Update Boost: Difference between revisions
No edit summary |
No edit summary |
||
Line 72: | Line 72: | ||
Make sure you've added the boost library and include paths to Visual Studio Tools->Options->Projects and Solutions->VC++ directories. | Make sure you've added the boost library and include paths to Visual Studio Tools->Options->Projects and Solutions->VC++ directories. | ||
Now you can add the library files you'll be using to your project. See | Now you can add the library files you'll be using to your project. However, most libraries are included automatically when you include the boost header. See the [http://boost.org/more/getting_started.html#Results boost "Getting Started" notes] for details. | ||
You should now be good to go! | You should now be good to go! |
Revision as of 16:39, 2 January 2007
This can help you update an existing boost installation under Linux or Windows, or get boost set up for the first time.
A note about CVS
I use boost from the CVS repository - it's typically been stable for me, and contains improved functionality over the official stable release. If you have trouble with the code you grab from CVS, you can wait a day and try again, to see if things have settled down, or google for answers, they're usually available fairly quickly. Once things seem stable for you, you should sit tight for a little while - no need to have to do this every single week, unless there's something new you just have to have. :>
You should upgrade all development environments, including Linux and Windows, at about the same time - don't wait a week or two and expect CVS installations to be compatible.
Linux
Remove the old boost:
cd ~m/development/boost_cvs rm -rf boost su - cd /usr/local/lib rm -f libboost* cd /usr/local/include rm -rf boost* ctrl-D
Grab a fresh copy from CVS:
cvs -d:pserver:[email protected]/cvsroot/boost login cvs -z3 -d:pserver:[email protected]/cvsroot/boost co -P boost
Also grab a new version of bjam, if needed, and put it here:
~m/development/boost_cvs/bjam
Now kick off the install.
screen ../bjam/boost-jam-3.1.13-1-linuxx86/bjam "-sTOOLS=gcc" (go get lunch) ...updated 1341 targets... su - cd ~m/development/boost_cvs/boost ../bjam/boost-jam-3.1.13-1-linuxx86/bjam "-sTOOLS=gcc" install
Update your projects to use the new boost. I made the following changes to my automake project:
configure.in: CPPFLAGS=”${CPPFLAGS} -I/usr/local/include/boost-#version#” Makefile.am: yourproject_LDADD = (…) /usr/local/lib/libboost_serialization-gcc#gccversion#.a
I thought about doing this symlink instead, but I'd rather maintain my project than the symlink:
cd /usr/local/lib ln -s libboost_serialization-gcc33.a libboost_serialization-gcc.a
Windows
Wipe out the old directory, except the boost\CVS directory, which will allow an easy fresh grab:
c:\Michael's Data\Software Development\boost_cvs\boost
Right-click on it and do a CVS update with Tortoise CVS. Also grab a new version of bjam, if needed, and put it in your path.
Next, we'll open a command window and set up the environment by running vcvars32.bat. But first, two things to check. First, make sure you run the RIGHT vcvars32.bat - each version of Visual Studio has one, and you won't always get the right one first in your path. Second, the default vcvars32.bat file will NOT have the Platform SDK files first - why, Microsoft? I adjusted mine so that the INCLUDE and LIB variables always put the Platform SDK paths first. On my system the file to adjust was here:
E:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars.bat
So when you're ready, set up the command line development environment and build boost:
<path to vc8>\vcvars32.bat cd <boost dir> bjam "-sTOOLS=vc-8_0" stage
Make sure you've added the boost library and include paths to Visual Studio Tools->Options->Projects and Solutions->VC++ directories.
Now you can add the library files you'll be using to your project. However, most libraries are included automatically when you include the boost header. See the boost "Getting Started" notes for details.
You should now be good to go!