Compile the static Boost Libraries in Windows - Revision history

Stgatilov: Boost is no longer relevant.

2019-04-11T03:23:30Z

Boost is no longer relevant.

← Older revision		Revision as of 03:23, 11 April 2019
Line 1:		Line 1:
			{{infobox\|bg=#ffa0a0\|This article is no longer relevant: boost has been removed from TDM game in version 2.06, and removed from tdm_update in version 2.08.}}

	There are several methods to obtain Boost binaries for Windows build environments.		There are several methods to obtain Boost binaries for Windows build environments.

Greebo: /* Compile the libraries from Boost sources */

2018-06-11T16:07:12Z

Compile the libraries from Boost sources

← Older revision		Revision as of 16:07, 11 June 2018
Line 25:		Line 25:
	..\..\bjam toolset=msvc link=static threading=multi runtime-link=static debug stage		..\..\bjam toolset=msvc link=static threading=multi runtime-link=static debug stage

	After these commands are done, the '''libboost_filesystem_vc*.lib''' files (both debug and release variants) can be found in the '''stage/''' directory below ~~your boost~~ folder. You'll need to repeat the above steps and replace '''filesystem''' with the names of the other libraries, e.g. '''regex''', '''thread''' or '''system'''.		After these commands are done, the '''libboost_filesystem_vc*.lib''' files (both debug and release variants) can be found in the '''stage/''' directory below the build folder (the one you launched the bjam command in). You'll need to repeat the above steps and replace '''filesystem''' with the names of the other libraries, e.g. '''regex''', '''thread''' or '''system'''.

	* Note for x64 users: Add the <tt>address-model=64</tt> option to bjam (after the threading argument) in order to build static libs with the 64-bit compiler.		* Note for x64 users: Add the <tt>address-model=64</tt> option to bjam (after the threading argument) in order to build static libs with the 64-bit compiler.
	* Note for users with multiple versions of Visual Studio: you can specify exactly which toolset you want to use by setting <tt>toolset=msvc-9.0</tt> (for VC++ 2008) and <tt>toolset=msvc-10.0</tt> (for VC++ 2010).		* Note for users with multiple versions of Visual Studio: you can specify exactly which toolset you want to use by setting <tt>toolset=msvc-9.0</tt> (for VC++ 2008) and <tt>toolset=msvc-10.0</tt> (for VC++ 2010). This argument is usually not necessary if you're using the correct VS command prompt.

	Now take the *.lib files from the stage/ folder and copy them into your project's library folder and the linking should succeed.		Now take the *.lib files from the stage/ folder and copy them into your project's library folder and the linking should succeed.

Greebo: /* Compile the libraries from Boost sources */

2018-06-11T16:03:51Z

Compile the libraries from Boost sources

← Older revision		Revision as of 16:03, 11 June 2018
Line 11:		Line 11:
	Download the boost release package from their website, e.g. Boost 1.45, and extract it to a folder. For this guide, I'll assume your boost package has been saved to <tt>c:\tools\boost_1_45_0</tt>).		Download the boost release package from their website, e.g. Boost 1.45, and extract it to a folder. For this guide, I'll assume your boost package has been saved to <tt>c:\tools\boost_1_45_0</tt>).

	To build the static libraries Boost you need the the boost jam tool (bjam.exe), which can be built by using the boostrap.bat script found in the root boost folder. Open a Visual Studio Developer Command prompt (choose the version you want to build the libraries for, e.g. 2017), then run the boostrap script which will place the bjam.exe in the same folder as the bootstrap script.		To build the static libraries Boost you need the the boost jam tool (bjam.exe), which can be built by using the boostrap.bat script found in the root boost folder. Open a Visual Studio Developer Command prompt (choose the version you want to build the libraries for, e.g. "Developer Command Prompt for VS 2017"), then run the boostrap script which will place the bjam.exe in the same folder as the bootstrap script.

	Let's start compiling by using the boost.filesystem library as example. Keep using the Visual Studio Developer Command prompt:		Let's start compiling by using the boost.filesystem library as example. Keep using the Visual Studio Developer Command prompt:

Greebo: /* Compile the libraries from Boost sources */

2018-06-11T16:02:42Z

Compile the libraries from Boost sources

← Older revision		Revision as of 16:02, 11 June 2018
Line 11:		Line 11:
	Download the boost release package from their website, e.g. Boost 1.45, and extract it to a folder. For this guide, I'll assume your boost package has been saved to <tt>c:\tools\boost_1_45_0</tt>).		Download the boost release package from their website, e.g. Boost 1.45, and extract it to a folder. For this guide, I'll assume your boost package has been saved to <tt>c:\tools\boost_1_45_0</tt>).

	To build the static libraries Boost you need the the boost jam tool (bjam.exe). At the ~~time of this writing there is a precompiled bjam.exe availabe on [http://sourceforge.net/projects/~~boost~~/files/boost-jam/ Sourceforge]~~. ~~Save~~ the ~~bjam.exe into some place~~ you ~~remember (~~e.g. ~~<tt>c:\tools\bjam.exe</tt>~~)~~. In case~~ the bjam.exe ~~can not be found, you can also build it from sources (this is not within~~ the ~~scope of this article)~~.		To build the static libraries Boost you need the the boost jam tool (bjam.exe), which can be built by using the boostrap.bat script found in the root boost folder. Open a Visual Studio Developer Command prompt (choose the version you want to build the libraries for, e.g. 2017), then run the boostrap script which will place the bjam.exe in the same folder as the bootstrap script.

	Let's start compiling by using the boost.filesystem library as example. ~~Open a command console (Win-R ==> "cmd" => Enter).~~		Let's start compiling by using the boost.filesystem library as example. Keep using the Visual Studio Developer Command prompt:

	cd c:\tools\boost_1_45_0		cd c:\tools\boost_1_45_0
	cd libs\filesystem\build		cd libs\filesystem\build
	c:\~~tools~~\bjam toolset=msvc link=static threading=multi release stage		..\..\..\bjam toolset=msvc link=static threading=multi release stage
	c:\~~tools~~\bjam toolset=msvc link=static threading=multi debug stage		..\..\..\bjam toolset=msvc link=static threading=multi debug stage

	Note that TDM ~~itself needs~~ an additional switch runtime-link=static ~~in addition~~ to ~~the above~~:		Note that TDM links statically to boost, so give an additional switch runtime-link=static to bjam:

	c:\~~tools~~\bjam toolset=msvc link=static threading=multi runtime-link=static release stage		..\..\bjam toolset=msvc link=static threading=multi runtime-link=static release stage
	c:\~~tools~~\bjam toolset=msvc link=static threading=multi runtime-link=static debug stage		..\..\bjam toolset=msvc link=static threading=multi runtime-link=static debug stage

	After these commands are done, the '''libboost_filesystem_vc*.lib''' files (both debug and release variants) can be found in the '''stage/''' directory below your boost folder. You'll need to repeat the above steps and replace '''filesystem''' with the names of the other libraries, e.g. '''regex''', '''thread''' or '''system'''.		After these commands are done, the '''libboost_filesystem_vc*.lib''' files (both debug and release variants) can be found in the '''stage/''' directory below your boost folder. You'll need to repeat the above steps and replace '''filesystem''' with the names of the other libraries, e.g. '''regex''', '''thread''' or '''system'''.

Greebo: /* Boost.Python */

2017-08-18T17:18:46Z

Boost.Python

@@ Line 32: / Line 32: @@
 Now take the *.lib files from the stage/ folder and copy them into your project's library folder and the linking should succeed.
-=== Boost.Python ===
+== Building boost.python ==
-To compile the Boost.Python static lib, you'll need to have a Python distribution installed in your system, otherwise bjam will complain that no Python installation can be found. Download a package from the [http://www.python.org Python website] and install it.
+I found it's possible to have both the x86 and x64 variants of Python around on your system to compile the boost.python library for both 32 and 64 bit platforms. Get the x86 and x64 installer from the Python website and install them into separate target folders. I tried this with Python 3.6, so your mileage might vary.
-Note: the boost python static library (e.g. '''libboost_python-vc100-mt-gd-1_42.lib''') will contain a reference to a specific version of the python static library. If you downloaded Python 2.7.1, your boost static lib will contain a reference to '''python27.lib'''. This file can be found in the libs/ in the directory you installed Python to, you should add that file to your project's library directory as well.
+Create a <tt>user-config.jam</tt> file and put it into your user folder, that might be <tt>C:\Users\greebo</tt>, for instance. To compile the 32-bit boost.python libs, I used the user-config.jam below, with my Python 3.6 x86 installation sitting in D:\temp\Python36-32 (for the records, I did not let the Python installer add anything to the PATH environment variable):
-Another note: when linking against that python27.lib your application will require the python27.dll at runtime. This file can be somewhat tricky to locate. For 32 bit systems this is usually C:\Windows\system32, for x64 systems the 32 bit Python DLL can be found in your C:\Windows\SysWoW64\ folder. On x64 systems, the 64 bit Python DLL is right in C:\Windows\System32.
+ using python
-See also the article in the DarkRadiant section which addresses boost.python compilation: [[DarkRadiant - Compiling in Windows#Prepare_for_building_boost.python|DarkRadiant - Compiling in Windows (boost.python secion)]]
+The I opened the Visual Studio Developer Command Prompt, changed folder to where I extracted the boost package (e.g. <tt>d:\temp\boost1_64</tt>) and started building using this command:
 == Boost.CMake ==

Greebo: /* Boost.Python */

2017-07-12T15:32:36Z

Boost.Python

← Older revision		Revision as of 15:32, 12 July 2017
Line 38:		Line 38:

	Another note: when linking against that python27.lib your application will require the python27.dll at runtime. This file can be somewhat tricky to locate. For 32 bit systems this is usually C:\Windows\system32, for x64 systems the 32 bit Python DLL can be found in your C:\Windows\SysWoW64\ folder. On x64 systems, the 64 bit Python DLL is right in C:\Windows\System32.		Another note: when linking against that python27.lib your application will require the python27.dll at runtime. This file can be somewhat tricky to locate. For 32 bit systems this is usually C:\Windows\system32, for x64 systems the 32 bit Python DLL can be found in your C:\Windows\SysWoW64\ folder. On x64 systems, the 64 bit Python DLL is right in C:\Windows\System32.

			See also the article in the DarkRadiant section which addresses boost.python compilation: [[DarkRadiant - Compiling in Windows#Prepare_for_building_boost.python\|DarkRadiant - Compiling in Windows (boost.python secion)]]

	== Boost.CMake ==		== Boost.CMake ==

Serpentinee at 22:27, 7 April 2012

2012-04-07T22:27:40Z

← Older revision		Revision as of 22:27, 7 April 2012
Line 1:		Line 1:
	There are several methods to obtain Boost binaries for Windows build environments.		There are several methods to obtain Boost binaries for Windows build environments.

	The boost static libraries follow a naming convention as explained in the ~~boost online docs:~~ http://www.boost.org/doc/libs/1_45_0/more/getting_started/windows.html#library-naming When including boost headers in your MSVC++ projects, the headers (like <boost/regex.hpp>) make use of VC's ''auto linking'' feature, so you don't need to worry about the actual file names, the linker is automatically instructed to require the correct libraries. All you have to do is make sure the linker can find these files in your project's libs directory.		The boost static libraries follow a naming convention as explained in the [http://www.boost.org/doc/libs/1_45_0/more/getting_started/windows.html#library-naming Boost - Library Naming] . When including boost headers in your MSVC++ projects, the headers (like <boost/regex.hpp>) make use of VC's ''auto linking'' feature, so you don't need to worry about the actual file names, the linker is automatically instructed to require the correct libraries. All you have to do is make sure the linker can find these files in your project's libs directory.

	== Download them from ~~sourceforge~~ ==		== Download them from Sourceforge ==
	You can try to find the static binaries needed on ~~boost's sourceforge page:~~ http://sourceforge.net/projects/boost/files/boost-binaries/		You can try to find the static binaries needed on [http://sourceforge.net/projects/boost/files/boost-binaries/ Boost's Sourceforge page].

	Often for very "fresh" releases there are no binaries available yet, so you'll need to fall back compiling the binaries yourself.		Often for very "fresh" releases there are no binaries available yet, so you'll need to fall back compiling the binaries yourself.
Line 11:		Line 11:
	Download the boost release package from their website, e.g. Boost 1.45, and extract it to a folder. For this guide, I'll assume your boost package has been saved to <tt>c:\tools\boost_1_45_0</tt>).		Download the boost release package from their website, e.g. Boost 1.45, and extract it to a folder. For this guide, I'll assume your boost package has been saved to <tt>c:\tools\boost_1_45_0</tt>).

	To build the static libraries Boost you need the the boost jam tool (bjam.exe). At the time of this writing there is a precompiled bjam.exe availabe on [http://sourceforge.net/projects/boost/files/boost-jam/~~3.1.18/boost-jam-3.1.18-1-ntx86.zip/download sourceforge~~]. Save the bjam.exe into some place you remember (e.g. <tt>c:\tools\bjam.exe</tt>). In case the bjam.exe can not be found, you can also build it from sources (this is not within the scope of this article).		To build the static libraries Boost you need the the boost jam tool (bjam.exe). At the time of this writing there is a precompiled bjam.exe availabe on [http://sourceforge.net/projects/boost/files/boost-jam/ Sourceforge]. Save the bjam.exe into some place you remember (e.g. <tt>c:\tools\bjam.exe</tt>). In case the bjam.exe can not be found, you can also build it from sources (this is not within the scope of this article).

	Let's start compiling by using the boost.filesystem library as example. Open a command console (Win-R ==> "cmd" => Enter).		Let's start compiling by using the boost.filesystem library as example. Open a command console (Win-R ==> "cmd" => Enter).

	cd c:\tools\boost_1_45_0		cd c:\tools\boost_1_45_0
	cd libs		cd libs\filesystem\build
	cd filesystem
	cd build
	c:\tools\bjam toolset=msvc link=static threading=multi release stage		c:\tools\bjam toolset=msvc link=static threading=multi release stage
	c:\tools\bjam toolset=msvc link=static threading=multi debug stage		c:\tools\bjam toolset=msvc link=static threading=multi debug stage
Line 58:		Line 56:
	# Unpack the tarball somewhere.		# Unpack the tarball somewhere.

	'''~~Configuring~~ and Generating:'''		'''Configuration and Generating:'''
	# Run the CMake GUI tool.		# Run the CMake GUI tool.
	# Set the source path to the location where you unpacked the tarball.		# Set the source path to the location where you unpacked the tarball.
	# Set an (empty) build directory - ''Note:'' while it says that this is where the binaries will be placed, this is actually going to be where all of the temporary build files are located, it will also contain the libs if we use default paths - don't freak out if there's loads of other stuff.		# Set an (empty) build directory - ''Note:'' while it says that this is where the binaries will be placed, this is actually going to be where all of the temporary build files are located, it will also contain the libs if we use default paths - don't freak out if there's loads of other stuff.
	# Click 'Configure' and set set which toolset/compiler you will be using. ''Note:'' If you are using icc, you will want to use Visual Studio as the generator but specify the compilers manually (icl.exe).		# Click 'Configure' and set set which toolset/compiler you will be using. ''Note:'' If you are using icc, you will want to use Visual Studio as the generator but specify the compilers manually (icl.exe).
	# There should now be a grid of default build options, many in red. Adjust them if needed, make sure that ENABLE_STATIC, ENABLE_MULTI_THREADED and ENABLE_RELEASE are ticked.		# There should now be a grid of default build options, many in red. Adjust them if needed, make sure that <tt>ENABLE_STATIC, ENABLE_MULTI_THREADED</tt> and <tt>ENABLE_RELEASE</tt> are ticked.
	# Once the configure process is complete, click 'Generate' - This will now place the solution file into the build directory.		# Once the configure process is complete, click 'Generate' - This will now place the solution file into the build directory.

Line 69:		Line 67:
	# Go to the build directory, as specified above.		# Go to the build directory, as specified above.
	# Open the solution file.		# Open the solution file.
	# '''Note''': By default the libraries are built as multithreaded-dll's (/MD flag) this needs to be changed to normal multithreaded for use with TDM. If you are having trouble with TDM linking looking in some strange libs/dlls, this is why.		# '''Note''': By default the libraries are built as multithreaded-dll's (<tt>/MD</tt> flag) this needs to be changed to normal multithreaded for use with TDM. If you are having trouble with TDM linking looking in some strange libs/dlls, this is why.
	## Select all of the projects that you wish to build, then right click on them in the solution browser and go to 'Properties'.		## Select all of the projects that you wish to build, then right click on them in the solution browser and go to 'Properties'.
	## Expand the C++ tab => Code Generation => Runtime Library, change this to 'Multi-threaded (/MT).		## Expand the C++ tab => Code Generation => Runtime Library, change this to 'Multi-threaded (<tt>/MT</tt>).
	## Apply.		## Apply.
	# While they are still selected, right click on them and then build them.		# While they are still selected, right click on them and then build them.

	You should now have the .libs in a /lib folder within your working directory. The libs might need renaming to fit with the naming scheme that is expected, e.g, : boost-regex-intel-mt-1_45.lib => libboost-regex-iw-mt-s-1_45.lib. This could likely be fixed in the CMakeLists file if you wanted, as well as the /MD -> /MT switch.		You should now have the .libs in a /lib folder within your working directory. The libs might need renaming to fit with the naming scheme that is expected, e.g, : <tt>boost-regex-intel-mt-1_45.lib</tt> => <tt>libboost-regex-iw-mt-s-1_45.lib</tt>. This could likely be fixed in the CMakeLists file if you wanted, as well as the <tt>/MD -> /MT</tt> switch.

	{{coding}}		{{coding}}

Serpentinee: Added an alternative CMake build method

2012-04-07T22:11:09Z

Added an alternative CMake build method

← Older revision		Revision as of 22:11, 7 April 2012
Line 40:		Line 40:

	Another note: when linking against that python27.lib your application will require the python27.dll at runtime. This file can be somewhat tricky to locate. For 32 bit systems this is usually C:\Windows\system32, for x64 systems the 32 bit Python DLL can be found in your C:\Windows\SysWoW64\ folder. On x64 systems, the 64 bit Python DLL is right in C:\Windows\System32.		Another note: when linking against that python27.lib your application will require the python27.dll at runtime. This file can be somewhat tricky to locate. For 32 bit systems this is usually C:\Windows\system32, for x64 systems the 32 bit Python DLL can be found in your C:\Windows\SysWoW64\ folder. On x64 systems, the 64 bit Python DLL is right in C:\Windows\System32.

			== Boost.CMake ==
			Some people find bjam to be extremely problematic under Windows. If you are having trouble, I would suggest trying the CMake build system branch of Boost. This is also very helpful with compiling the libs for use with Intel's compilers which tend to be badly supported by the bjam build system. Another advantage is that CMake generates Visual Studio solution files, meaning that you can adjust build settings or rebuild components with a familiar interface.

			CMake in Windows has a nice GUI which makes configuring the build very easy, as well as providing a way to easily adjust them at a later stage.

			[https://svn.boost.org/trac/boost/wiki/CMake Boost.Cmake - Boost Wiki] - [http://gitorious.org/boost Boost.Cmake - Gitorious]

			=== Steps ===
			'''CMake:'''
			# Download the latest binary release of CMake for your platform [http://www.cmake.org/cmake/resources/software.html CMake and related downloads]
			# Install it. Make sure that the CMake GUI gets installed.

			'''Boost.CMake Source:'''
			# Figure out which release of Boost that you need — in this case we will assume 1.45.
			# Download the relevant release tarball from the Gitorious branch (or use git/hg-git). The tarball can be found in the branch overview i.e, : [http://gitorious.org/boost/cmake/commits/cmake-1.45.0 Boost.CMake 1.45 branch]
			# Unpack the tarball somewhere.

			'''Configuring and Generating:'''
			# Run the CMake GUI tool.
			# Set the source path to the location where you unpacked the tarball.
			# Set an (empty) build directory - ''Note:'' while it says that this is where the binaries will be placed, this is actually going to be where all of the temporary build files are located, it will also contain the libs if we use default paths - don't freak out if there's loads of other stuff.
			# Click 'Configure' and set set which toolset/compiler you will be using. ''Note:'' If you are using icc, you will want to use Visual Studio as the generator but specify the compilers manually (icl.exe).
			# There should now be a grid of default build options, many in red. Adjust them if needed, make sure that ENABLE_STATIC, ENABLE_MULTI_THREADED and ENABLE_RELEASE are ticked.
			# Once the configure process is complete, click 'Generate' - This will now place the solution file into the build directory.

			'''Building:'''
			# Go to the build directory, as specified above.
			# Open the solution file.
			# '''Note''': By default the libraries are built as multithreaded-dll's (/MD flag) this needs to be changed to normal multithreaded for use with TDM. If you are having trouble with TDM linking looking in some strange libs/dlls, this is why.
			## Select all of the projects that you wish to build, then right click on them in the solution browser and go to 'Properties'.
			## Expand the C++ tab => Code Generation => Runtime Library, change this to 'Multi-threaded (/MT).
			## Apply.
			# While they are still selected, right click on them and then build them.

			You should now have the .libs in a /lib folder within your working directory. The libs might need renaming to fit with the naming scheme that is expected, e.g, : boost-regex-intel-mt-1_45.lib => libboost-regex-iw-mt-s-1_45.lib. This could likely be fixed in the CMakeLists file if you wanted, as well as the /MD -> /MT switch.

	{{coding}}		{{coding}}

Greebo: /* Compile the libraries from Boost sources */

2011-02-08T15:06:26Z

Compile the libraries from Boost sources

← Older revision		Revision as of 15:06, 8 February 2011
Line 21:		Line 21:
	c:\tools\bjam toolset=msvc link=static threading=multi release stage		c:\tools\bjam toolset=msvc link=static threading=multi release stage
	c:\tools\bjam toolset=msvc link=static threading=multi debug stage		c:\tools\bjam toolset=msvc link=static threading=multi debug stage

			Note that TDM itself needs an additional switch runtime-link=static in addition to the above:

			c:\tools\bjam toolset=msvc link=static threading=multi runtime-link=static release stage
			c:\tools\bjam toolset=msvc link=static threading=multi runtime-link=static debug stage

	After these commands are done, the '''libboost_filesystem_vc*.lib''' files (both debug and release variants) can be found in the '''stage/''' directory below your boost folder. You'll need to repeat the above steps and replace '''filesystem''' with the names of the other libraries, e.g. '''regex''', '''thread''' or '''system'''.		After these commands are done, the '''libboost_filesystem_vc*.lib''' files (both debug and release variants) can be found in the '''stage/''' directory below your boost folder. You'll need to repeat the above steps and replace '''filesystem''' with the names of the other libraries, e.g. '''regex''', '''thread''' or '''system'''.

Greebo: /* Compile the libraries from Boost sources */

2010-12-05T08:33:20Z

Compile the libraries from Boost sources

← Older revision		Revision as of 08:33, 5 December 2010
Line 24:		Line 24:
	After these commands are done, the '''libboost_filesystem_vc*.lib''' files (both debug and release variants) can be found in the '''stage/''' directory below your boost folder. You'll need to repeat the above steps and replace '''filesystem''' with the names of the other libraries, e.g. '''regex''', '''thread''' or '''system'''.		After these commands are done, the '''libboost_filesystem_vc*.lib''' files (both debug and release variants) can be found in the '''stage/''' directory below your boost folder. You'll need to repeat the above steps and replace '''filesystem''' with the names of the other libraries, e.g. '''regex''', '''thread''' or '''system'''.

	Note for x64 users: Add the <tt>address-model=64</tt> option to bjam (after the threading argument) in order to build static libs with the 64-bit compiler.		* Note for x64 users: Add the <tt>address-model=64</tt> option to bjam (after the threading argument) in order to build static libs with the 64-bit compiler.
	Note for users with multiple versions of Visual Studio: you can specify exactly which toolset you want to use by setting <tt>toolset=msvc-9.0</tt> (for VC++ 2008) and <tt>toolset=msvc-10.0</tt> (for VC++ 2010).		* Note for users with multiple versions of Visual Studio: you can specify exactly which toolset you want to use by setting <tt>toolset=msvc-9.0</tt> (for VC++ 2008) and <tt>toolset=msvc-10.0</tt> (for VC++ 2010).

	Now take the *.lib files from the stage/ folder and copy them into your project's library folder and the linking should succeed.		Now take the *.lib files from the stage/ folder and copy them into your project's library folder and the linking should succeed.