Jeff Garland wrote:
Stefan Seefeld wrote:
troy d. straszheim wrote:
In boost itself libraries live next to each other (in terms of file system layout). Thus, a sandbox project could be looked at as a single library stored 'out-of-place'. The build system should support referring to an existing boost tree for the 'official boost' dependencies, such that the sandbox project only needs to provide new or updated files, but not a whole copy of boost-mainline.
This is a huge problem with the current sandbox organization. After spending a couple hours the other day trying to get boost.build to work in the sandbox tree I gave up in frustration and had to copy sandbox directories into my boost tree to use bjam. This is very annoying to say the least.
Is this a boost.build limitation ? What's the proper way to fix that ? Regards, Stefan -- ...ich hab' noch einen Koffer in Berlin...