Robert Bielik wrote:
Hi all,
I'm sitting here developing a build script to automate my build which first of all involves checking out sources, one of which is boost. However, 99.9% of the checkout time is boost tests/documentation/examples and what have you.
If it were me, I'd think a little more about this. When I include boost in a (real) commercial project. I include/link to a public directory which contains the release of boost I want to depend on. I don't check it out of some depostitory and re-build. I do this for a few reasons. a) It saves a lot of time. b) It prevents me from getting surprised by changes that I'm not expecting. c) It lets me change one thing at a time (corallory to b). When I've got nothing else to do or my app needs some new library/feature I can replace the boost version and re-run any testing. If there's any problem I can just redirect to the original spot until my complaints are addressed. Boost files are "read-only" in this context so they are not great candidates for "checking out the latest version" Robert Ramey