Hello Paul, The reason for this is that we have the possibility someday to chroot in the bt_staging_dir. Once everything is build you have a fairly complete distro and by chrooting or adding a kernel to it should be possible to boot it and use it as a compile environment (after some tweaking).
This is not fully worked out, but if I'm not mistaken the idea was not only use it as a toolchain but also keep the option to use it as a complete build environment. Eric Spakman --------------------------------------------------------------------- I certainly understand why we copy the toolchain, libraries, and include files into bt_staging_dir, but it seems somewhat bogus that we're doing so for end-binaries (i.e. things that nothing else is ever going to depend upon)... Is there a reason for this? It seems that there was a change in the charter for bt_staging_dir at some point (the documentation discusses that it's just for the toolchain elements, but all the example buildtool.mk files I've seen copy binaries and configuration files in there that are not part of the toolchain). I realize I'm just talking about one line in a buildtool.mk file, but it just seems curious that we're polluting what would otherwise be a clean and hopefully idempotent toolchain directory. Thanks, Paul ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
