Update Boost - Revision history

M at 09:32, 17 September 2007

2007-09-17T09:32:42Z

← Older revision		Revision as of 09:32, 17 September 2007
Line 67:		Line 67:
	Next, we'll open a command window and set up the environment by running vcvars32.bat.		Next, we'll open a command window and set up the environment by running vcvars32.bat.

	(older notes...) 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:		<font style="color:gray">(older notes...) 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		E:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars.bat
Line 73:		Line 73:
	If you check the "Getting Started" boost docs in CVS (the boost/index.htm file), you'll notice that they are VERY different from the boost.org version of "Getting Started". It looks like the "vc-8_0" toolset recommended for the stable build has been rolled into the more generic "msvc" toolset along with other versions of VC. The vcvars32.bat file then drives the whole process. Also, the way you specify the bjam toolset option has apparently changed.		If you check the "Getting Started" boost docs in CVS (the boost/index.htm file), you'll notice that they are VERY different from the boost.org version of "Getting Started". It looks like the "vc-8_0" toolset recommended for the stable build has been rolled into the more generic "msvc" toolset along with other versions of VC. The vcvars32.bat file then drives the whole process. Also, the way you specify the bjam toolset option has apparently changed.

	(newer notes...) There is a shortcut in the Microsoft Windows SDK folder that seems to correct the include and lib paths:		(newer notes...)</font> There is a shortcut in the Microsoft Windows SDK folder that seems to correct the include and lib paths:

	C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Windows SDK\Visual Studio Registration\Integrate Windows SDK with Visual Studio 2005		C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Windows SDK\Visual Studio Registration\Integrate Windows SDK with Visual Studio 2005
Line 87:		Line 87:
	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.

	You shouldn't even need to add the library files you'll be using to your project, as most libraries are included automatically when you include the boost header. HOWEVER, as of this writing, bjam (using the catch-all "--toolset=msvc") is creating Windows static library files named "...-vc-...", while the auto-linking code in the header files is forcing a link to "...-vc80-...". Silly boost. I have updated CVS with no luck, so for now I will just copy the libraries I need from the -vc- name to the -vc80- name, as a temporary workaround.		You shouldn't even need to add the library files you'll be using to your project, as most libraries are included automatically when you include the boost header.

			<font style="color:gray">(older notes) HOWEVER, as of this writing, bjam (using the catch-all "--toolset=msvc") is creating Windows static library files named "...-vc-...", while the auto-linking code in the header files is forcing a link to "...-vc80-...". Silly boost. I have updated CVS with no luck, so for now I will just copy the libraries I need from the -vc- name to the -vc80- name, as a temporary workaround. </font>

	You should now be good to go!		You should now be good to go!

M at 18:26, 16 September 2007

2007-09-16T18:26:41Z

← Older revision		Revision as of 18:26, 16 September 2007
Line 9:		Line 9:
	== Linux ==		== Linux ==

	Remove the old boost:		Remove the old boost (if any):

	cd ~m/development/boost_cvs		cd ~m/development/boost_cvs
Line 22:		Line 22:
	Grab a fresh copy from CVS:		Grab a fresh copy from CVS:

			cd ~m/development/boost_cvs
	cvs -d:pserver:anonymous@boost.cvs.sourceforge.net/cvsroot/boost login		cvs -d:pserver:anonymous@boost.cvs.sourceforge.net/cvsroot/boost login
	cvs -z3 -d:pserver:anonymous@boost.cvs.sourceforge.net/cvsroot/boost co -P boost		cvs -z3 -d:pserver:anonymous@boost.cvs.sourceforge.net/cvsroot/boost co -P boost

M at 03:04, 5 July 2007

2007-07-05T03:04:00Z

← Older revision		Revision as of 03:04, 5 July 2007
Line 64:		Line 64:
	Once you have the source, grab a new version of bjam, if needed, and put it in your path.		Once you have the source, 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:		Next, we'll open a command window and set up the environment by running vcvars32.bat.

			(older notes...) 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		E:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars.bat

	If you check the "Getting Started" boost docs in CVS (the boost/index.htm file), you'll notice that they are VERY different from the boost.org version of "Getting Started". It looks like the "vc-8_0" toolset recommended for the stable build has been rolled into the more generic "msvc" toolset along with other versions of VC. The vcvars32.bat file then drives the whole process. Also, the way you specify the bjam toolset option has apparently changed.		If you check the "Getting Started" boost docs in CVS (the boost/index.htm file), you'll notice that they are VERY different from the boost.org version of "Getting Started". It looks like the "vc-8_0" toolset recommended for the stable build has been rolled into the more generic "msvc" toolset along with other versions of VC. The vcvars32.bat file then drives the whole process. Also, the way you specify the bjam toolset option has apparently changed.

			(newer notes...) There is a shortcut in the Microsoft Windows SDK folder that seems to correct the include and lib paths:

			C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Windows SDK\Visual Studio Registration\Integrate Windows SDK with Visual Studio 2005

	So when you're ready, set up the command line development environment and build boost:		So when you're ready, set up the command line development environment and build boost:

M at 23:41, 4 July 2007

2007-07-04T23:41:37Z

← Older revision		Revision as of 23:41, 4 July 2007
Line 33:		Line 33:
	cd boost		cd boost
	screen		screen
	../bjam/boost-jam-3.1.14-1-linuxx86/bjam "-~~sTOOLS~~=gcc"		../bjam/boost-jam-3.1.14-1-linuxx86/bjam --toolset=gcc
	(go get lunch)		(go get lunch)
	...updated 1341 targets...		...updated 1341 targets...
	su -		su -
	cd ~m/development/boost_cvs/boost		cd ~m/development/boost_cvs/boost
	../bjam/boost-jam-3.1.14-1-linuxx86/bjam "-~~sTOOLS~~=gcc" install		../bjam/boost-jam-3.1.14-1-linuxx86/bjam --toolset=gcc install

	Update your projects to use the new boost.		Update your projects to use the new boost.

M at 14:58, 4 July 2007

2007-07-04T14:58:45Z

← Older revision		Revision as of 14:58, 4 July 2007
Line 31:		Line 31:
	Now kick off the install.		Now kick off the install.

			cd boost
	screen		screen
	../bjam/boost-jam-3.1.13-1-linuxx86/bjam "-sTOOLS=gcc"		../bjam/boost-jam-3.1.14-1-linuxx86/bjam "-sTOOLS=gcc"
	(go get lunch)		(go get lunch)
	...updated 1341 targets...		...updated 1341 targets...
	su -		su -
	cd ~m/development/boost_cvs/boost		cd ~m/development/boost_cvs/boost
	../bjam/boost-jam-3.1.13-1-linuxx86/bjam "-sTOOLS=gcc" install		../bjam/boost-jam-3.1.14-1-linuxx86/bjam "-sTOOLS=gcc" install

	Update your projects to use the new boost.		Update your projects to use the new boost.

M: /* Windows */

2007-01-08T18:22:35Z

Windows

← Older revision		Revision as of 18:22, 8 January 2007
Line 75:		Line 75:
	cd <boost dir>		cd <boost dir>
	bjam "--toolset=msvc" stage		bjam "--toolset=msvc" stage
			(go get lunch)

	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.

M at 22:39, 3 January 2007

2007-01-03T22:39:06Z

← Older revision		Revision as of 22:39, 3 January 2007
Line 5:		Line 5:
	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. :>		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.		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. I wrote this in early January 2007, and things seem fairly stable.

	== Linux ==		== Linux ==

M at 22:35, 3 January 2007

2007-01-03T22:35:12Z

← Older revision		Revision as of 22:35, 3 January 2007
Line 53:		Line 53:
	== Windows ==		== Windows ==

	~~Wipe~~ out the old directory, '''except the boost\CVS directory''', which will allow an easy fresh grab (it will also clear out potentially TONS of old stuff that won't otherwise be cleaned up - particularly the bin directory, replaced with bin.v2):		This is for Visual Studio 2005 with SP1 installed.

			If you do not have boost yet, [http://news.thedigitalmachine.com/2006/09/05/getting-to-sourceforge-from-windows-through-a-proxy-redux/ check here] for instructions on grabbing a CVS snapshot. Otherwise, wipe out the old directory, '''except the boost\CVS directory''', which will allow an easy fresh grab (it will also clear out potentially TONS of old stuff that won't otherwise be cleaned up - particularly the bin directory, replaced with bin.v2):

	c:\Michael's Data\Software Development\boost_cvs\boost		c:\Michael's Data\Software Development\boost_cvs\boost

	Right-click on it and do a CVS update with Tortoise CVS.		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.
			Once you have the source, 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:		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:

M at 21:16, 3 January 2007

2007-01-03T21:16:32Z

← Older revision		Revision as of 21:16, 3 January 2007
Line 1:		Line 1:
	This can help you update an existing boost installation under Linux or Windows~~, or get boost set up for the first time~~.		This can help you get boost set up for the first time, or update an existing boost installation, under Linux or Windows.

	== A note about CVS ==		== A note about CVS ==
Line 53:		Line 53:
	== Windows ==		== Windows ==

	Wipe out the old directory, '''except the boost\CVS directory''', which will allow an easy fresh grab:		Wipe out the old directory, '''except the boost\CVS directory''', which will allow an easy fresh grab (it will also clear out potentially TONS of old stuff that won't otherwise be cleaned up - particularly the bin directory, replaced with bin.v2):

	c:\Michael's Data\Software Development\boost_cvs\boost		c:\Michael's Data\Software Development\boost_cvs\boost
Line 64:		Line 64:
	E:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars.bat		E:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars.bat

	If you check the "Getting Started" boost docs in CVS (the boost/index.htm file), you'll notice that they are VERY different from the boost.org version of "Getting Started". It looks like the "vc-8_0" toolset recommended for the stable build has been rolled into the more generic "msvc" toolset along with other versions of VC. The vcvars32.bat file then drives the whole process.		If you check the "Getting Started" boost docs in CVS (the boost/index.htm file), you'll notice that they are VERY different from the boost.org version of "Getting Started". It looks like the "vc-8_0" toolset recommended for the stable build has been rolled into the more generic "msvc" toolset along with other versions of VC. The vcvars32.bat file then drives the whole process. Also, the way you specify the bjam toolset option has apparently changed.

	So when you're ready, set up the command line development environment and build boost:		So when you're ready, set up the command line development environment and build boost:

	<path to vc8>\vcvars32.bat		<path to vc8>\vcvars32.bat
			(or use Program Files->Microsoft Visual Studio 2005->Visual Studio Tools->Visual Studio 2005 Command Prompt)
	cd <boost dir>		cd <boost dir>
	bjam "-~~sTOOLS~~=msvc" stage		bjam "--toolset=msvc" stage

	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.

	You shouldn't even need to add the library files you'll be using to your project, as most libraries are included automatically when you include the boost header. HOWEVER, as of this writing, bjam (using the ~~generic~~ "-~~sTOOLS~~=msvc" ~~toolset~~) is creating Windows static library files named "...-vc-...", while the auto-linking code in the header files is forcing a link to "...-vc80-...". Silly boost. I have updated CVS with no luck, so for now I will just copy the libraries I need from the -vc- name to the -vc80- name, as a temporary workaround.		You shouldn't even need to add the library files you'll be using to your project, as most libraries are included automatically when you include the boost header. HOWEVER, as of this writing, bjam (using the catch-all "--toolset=msvc") is creating Windows static library files named "...-vc-...", while the auto-linking code in the header files is forcing a link to "...-vc80-...". Silly boost. I have updated CVS with no luck, so for now I will just copy the libraries I need from the -vc- name to the -vc80- name, as a temporary workaround.


	You should now be good to go!		You should now be good to go!

M at 21:06, 3 January 2007

2007-01-03T21:06:36Z

← Older revision		Revision as of 21:06, 3 January 2007
Line 63:		Line 63:

	E:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars.bat		E:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars.bat

			If you check the "Getting Started" boost docs in CVS (the boost/index.htm file), you'll notice that they are VERY different from the boost.org version of "Getting Started". It looks like the "vc-8_0" toolset recommended for the stable build has been rolled into the more generic "msvc" toolset along with other versions of VC. The vcvars32.bat file then drives the whole process.

	So when you're ready, set up the command line development environment and build boost:		So when you're ready, set up the command line development environment and build boost:
Line 68:		Line 70:
	<path to vc8>\vcvars32.bat		<path to vc8>\vcvars32.bat
	cd <boost dir>		cd <boost dir>
	bjam "-sTOOLS=~~vc-8_0~~" stage		bjam "-sTOOLS=msvc" stage

	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.

	You shouldn't even need to add the library files you'll be using to your project, as most libraries are included automatically when you include the boost header. HOWEVER, as of this writing, bjam (using the "-sTOOLS=~~vc-8_0~~" toolset) is creating Windows static library files named "...-vc-...", while the auto-linking code is forcing a link to "...-vc80-...". Silly boost. I have updated CVS with no luck, so for now I will just copy the libraries I need from the -vc- name to the -vc80- name, as a temporary workaround. ~~See the [http://boost.org/more/getting_started.html#Results boost "Getting Started" notes] for library-naming details.~~		You shouldn't even need to add the library files you'll be using to your project, as most libraries are included automatically when you include the boost header. HOWEVER, as of this writing, bjam (using the generic "-sTOOLS=msvc" toolset) is creating Windows static library files named "...-vc-...", while the auto-linking code in the header files is forcing a link to "...-vc80-...". Silly boost. I have updated CVS with no luck, so for now I will just copy the libraries I need from the -vc- name to the -vc80- name, as a temporary workaround.


	You should now be good to go!		You should now be good to go!