From: Brian Braatz (brianb_at_[hidden])
Date: 2005-05-27 08:41:41
> -----Original Message-----
> From: boost-bounces_at_[hidden]
> On Behalf Of Jeff Flinn
> Sent: Thursday, May 26, 2005 9:29 AM
> To: boost_at_[hidden]
> Subject: [boost] Re: Customer Friendlier Boost Installation
> "David Abrahams" <dave_at_[hidden]> wrote in message
> > "Jeff Flinn" <TriumphSprint2000_at_[hidden]> writes:
> >> Something like this as a start?
> >> For MSVC
> >> ========
> >> Organizing boost files
> >> ======================
> >> 1) Create a main boost directory which will contain the current and
> >> future
> >> boost library verstions. For example: C:\boost
> > Maybe not such a good choice considering that it's the default
> > location for Windows? Or should we change the default (and if so,
> > what?)
> Sorry, "location for Windows" has too many overloads for me to know
> your asking here. What exactly is the problem using C:\boost?
[Brian Braatz Writes:]
An idea to add to the mix.
I config manage boost internal to my company- How I do that is I put
boost into an internal CVS server
I then make dirs (in CVS) like so
Common\source\boost\v_1_32\ (boost distro goes here)
This has an interesting effect of forcing the MSVC IDE project files to
have "boost\v_1_32" embedded in a string in them.
This allows me to keep 2 versions of boost side by side, and quickly (by
changing the "Include directories path" setting in the IDE to test with
different versions of boost
I am going to be adding a
Common\source\boost\Live\ at somepoint to be able to test off of current
stuff - the difficult with that will be just scripting the CVS get from
source forge, removing the cvs files added, and then re-adding to our
internal cvs (and cvs does not support recursive add).
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk