On Sun, 3 Feb 2008, Robert P. J. Day wrote: > On Sun, 3 Feb 2008, Felix Fietkau wrote: > > > Robert P. J. Day wrote: > > > in all this discussion, i don't think we've addressed the original > > > subject -- why do "make clean" and "make dirclean" require a .config > > > file, such that they'll dump you into "make meuconfig" if you don't > > > have one? > > > > > > why do those two variations of cleaning seem to require a prior > > > configuration? > > > At the moment, clean and dirclean only clean the directories for > > the current target selection. I guess this could be changed in the > > future, so that if no .config exists, it deletes the appropriate > > directories for all targets. > > actually, i'd assumed as much and was guessing that you could build > several toolchains/images simultaneously under the same directory > structure so that, when you did a "clean", you'd just want to clean > that part of the tree corresponding to the current .config. but > when i looked more closely, i'm not convinced that that works very > well. > > maybe i'm misreading this but, when i configured and built for my > WL500gP and Broadcom WiFi, the resulting directories were called > things like "mipsel", "toolchain-mipsel_gcc4.1.2", and so on. > sure, that corresponds to my current config, but it's not a *unique* > correspondence. > > given more platforms, isn't it theoretically possible to configure > for another platform that just happens to use mipsel and be based on > gcc-4.1.2 as well? and if that were the case, wouldn't that second > build step all over the previous build? > > in short, unless you can guarantee complete separation between > different target platforms when you're configuring and building, i'm > not sure there's much value in trying to make a "clean" try to be > that selective.
whoops, i should have been a bit more specific in that there *are* some subdirs that are created specifically for that target, like build_dir/linux-brcm47xx, but i think you get my point. rday p.s. i haven't looked at all possible targets -- are there any that would actually clobber the results of a previous build by using an identical directory name, or do you deal with that in some way? i'm still working my way thru the build process. -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ======================================================================== _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
