-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users- bounces@lists.boost.org] On Behalf Of liamv7 Sent: Friday, February 02, 2007 5:04 AM To: Boost-users@lists.boost.org Subject: [Boost-users] installing boost at work
Hi, I want to use boost at work. What's the best way to make this available to our developers? The options I see: 1. Put the include files and built libs/dlls in version control. I don't see much point to this and binaries take up a lot a space and it's annoying when upgrading. 2. Zip up the include files and dlls and have developers unzip in appropriate location. 3. Let developers access boost over network. To slow.
How do you guys manage this?
[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.