
-----Original Message----- From: boost-users-bounces@lists.boost.org on behalf of Nat Goodspeed [Nat] Probably not what you want to hear, but we checked the Boost sources & includes into a subtree in our version-control system. For the few Boost libraries we use that require building, we created platform-specific project files and build them along with our own source code. Naturally they don't require rebuilding as often as our stuff, but it makes it more uniform for a new developer to get started. This also allows us to use the VCS (Subversion in our case) to manage the problem of merging local patches with new Boost releases. ------------- Hi, I do the same thing but I'm curious why you wouldn't just use bjam to build boost? One thing I do is also check in the binaries per platform/compiler/variant and the build scripts are smart enough to know where to look. The logic behind this was that there is no point rebuilding as 90% of the developers would use the same platform and that the builds would just build our code. Sohail