--On Tuesday, March 24, 2009 11:56 AM -0600 Damien Hocking
Boost isn't rebuilt as part of the SCons build pass, we have shell scripts (Linux, OSX) or batch files (Windows) that devs can invoke if they want or need to.
Sounds like a good approach.
I've also worked with other organisations that have the Boost source and platform binaries on a network share, and not part of the version control system.
Alas, this wouldn't work for me as is as it would require mobile developers (those working on an embedded system at the customer site) to have a local copy. I guess they could periodically sync with the file server, but at that point I might as well check the whole thing into version control, using your first suggestion. One thing I'm considering is NOT putting the upstream release in my repo, but rather checking out from the official repo (eg. via externals) and then having local scripts build that. What kinds of downsides are there to that?