> > 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. > > or am i missing something?
You're right. Pls see attached patch. The BUILD_SUFFIX is used to separate different platforms. Currently the toolchain dir is not unique enough. You can't have the same gcc and different uclibc versions for the same arch. The applied patch does not fix the ./tmp dir . Unless the ./tmp is not unique it's not possible to run different builds in parallel (for instance in an compute farm). At least sequential build are is possible with this patch. You can easily change between different platforms without loosing the previous builds. br/R
rules.patch
Description: rules.patch
_______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
