Re: [boost] big problem with dependency changes

Or is it only running b2 headers that is the problem?

Maybe I have missed it in the previous conversations, but why have ./b2 headers make the /boost folder at all? When using boost-build, the headers target can add all the include paths for the various projects. If working on a project not using boost-build, generally I would install boost (at the very least into a folder). I ask, how are people depending on the generated /boost directory? Is it only to build the boost libraries? Regards, Thomas