boost-build

Cannot build Boost with MinGW, it looks for Visual C++

橙三吉。 提交于 2019-12-10 18:43:50
问题 At first I tried to build Boost having both MinGW and Microsoft Visual C++ installed, with these commands: bootstrap.bat mingw .\b2 During the build process, I got plenty of log lines indicating that the build was being done for Visual C++ (msvc). So I stopped it, I completely uninstalled Visual C++ (using the Windows utility), I removed the Boost directory, I recreated it from the bz2 file, I checked that g++.exe was in the PATH, and I re-entered the previous two commands to reinstall Boost

How to build Boost 1.55 with Visual Studio 2013?

岁酱吖の 提交于 2019-12-09 10:43:59
问题 I'm trying to build Boost 1.55 with Visual Studio 2013. 1) I tried to use boost-binaries (boost-binaries), but Visual Studio wrote about the error, when I tried to compile: error LNK1104: cannot open file 'libboost_serialization-vc120-mt-gd-1_55.lib'. I used boost_1_55_0-msvc-12.0-32.exe or 1.55.0-build2 (boost-binaries). I didn't find that .lib file in the boost_1_55_0\lib32-msvc-12.0 directory. 2) I also tried to use this program BlueGo 0.1.7 (BlueGo). It works very smooth, and create all

Change boost.build jamfile for C++11 support?

拜拜、爱过 提交于 2019-12-08 17:30:36
问题 I have been using boost.build or b2 for building a project. I am trying to add C++11 contructs like auto and begin but the standard invokation b2 release in the directory with the Jamfile does not recognize these. 回答1: Added the following in Jamroot <toolset>gcc:<cxxflags>-std=gnu++0x <toolset>clang:<cxxflags>-std=c++11 Seems to be working 回答2: You need to tell the compiler to enable c++11 support For example, for gcc you can use b2 toolset=gcc cxxflags="-std=c++11" (or the same command with

Building Boost for 32-bit and 64-bit on Windows into the same folder

时光总嘲笑我的痴心妄想 提交于 2019-12-07 15:00:42
问题 I'm looking a simple setup for the config.jam which will build Boost (1.60 or later) for both x86 and x64 on Windows using MSVC. Ideally using a single call to b2 -- I know that it's supposed to support generating multiple outputs from a single call. Having two separate calls for x86 and x64 is ok but not preferred. The other thing I would like is to have it output both sets of libraries into the same folder. Obviously then they need to have different names, so I would like it to put -x64

OSX Snow Leopard: Build boost 1.47.0 for 32 and 64 bit

女生的网名这么多〃 提交于 2019-12-06 02:51:06
问题 I am going crazy...I am currently trying to upgrade boost for my project from 1.44.0 to 1.47.0 on osx snow leopard.- I want to build it with the following command: ./b2 macosx-version=10.6 link=static address-model=32_64 threading=multi stage where i'd expect that it gives me a static fat build that supports i386 aswell as x86_64 . Anyways, it obviously does not, since if i query lipo -info of the resulting libs, they are all x86_64.- What can I do to solve this? Could it be that the build

Building Boost for 32-bit and 64-bit on Windows into the same folder

心已入冬 提交于 2019-12-05 18:48:28
I'm looking a simple setup for the config.jam which will build Boost (1.60 or later) for both x86 and x64 on Windows using MSVC. Ideally using a single call to b2 -- I know that it's supposed to support generating multiple outputs from a single call. Having two separate calls for x86 and x64 is ok but not preferred. The other thing I would like is to have it output both sets of libraries into the same folder. Obviously then they need to have different names, so I would like it to put -x64 somewhere in the names of the x64 binaries. And it still needs to auto-link, so I can't just rename them

How to build boost 1.45 universal binaries?

匆匆过客 提交于 2019-12-04 23:39:52
问题 How to build boost 1.45 universal binaries? on leopard/ snow leopard ? 回答1: To build 4-way universal boost static binaries on OSX 10.6 I do the following: Download boost from the boost website. Extract the archive and cd into the boost_x_xx_x folder (where x_xx_x is the version of boost you are using). Run: ./bootstrap.sh and then # The name of the Boost.Jam program changed from "bjam" to "b2" in Boost 1.47.0 # Replace "b2" with "bjam" if you are compiling a version <= 1.46.1 ./b2 macosx

OSX Snow Leopard: Build boost 1.47.0 for 32 and 64 bit

一世执手 提交于 2019-12-04 08:36:49
I am going crazy...I am currently trying to upgrade boost for my project from 1.44.0 to 1.47.0 on osx snow leopard.- I want to build it with the following command: ./b2 macosx-version=10.6 link=static address-model=32_64 threading=multi stage where i'd expect that it gives me a static fat build that supports i386 aswell as x86_64 . Anyways, it obviously does not, since if i query lipo -info of the resulting libs, they are all x86_64.- What can I do to solve this? Could it be that the build script is broken? I got it to work by using this build: ./b2 link=static threading=multi toolset=darwin

How to build Boost 1.55 with Visual Studio 2013?

╄→гoц情女王★ 提交于 2019-12-03 12:42:28
I'm trying to build Boost 1.55 with Visual Studio 2013. 1) I tried to use boost-binaries ( boost-binaries ), but Visual Studio wrote about the error, when I tried to compile: error LNK1104: cannot open file 'libboost_serialization-vc120-mt-gd-1_55.lib'. I used boost_1_55_0-msvc-12.0-32.exe or 1.55.0-build2 (boost-binaries). I didn't find that .lib file in the boost_1_55_0\lib32-msvc-12.0 directory. 2) I also tried to use this program BlueGo 0.1.7 ( BlueGo ). It works very smooth, and create all libraries, which I am needed. The problem in that it creates .lib files like this: libboost

Compile boost-python tutorial with VS-2015 CTP 5 and Python 3.5a on Windows 10 TP

纵然是瞬间 提交于 2019-12-01 08:03:45
I'm trying to get the boost-python extension module tutorial working on a modern C++14 compiler in Windows 10. I've downloaded the latest versions of boost 1.57 and python 3.5a source using vc-14 (VS 2015 CTP 5). I compiled python from source using VS 2015 CTP 5 and these instructions: 1.1.3.3. Windows . I've run the command .\bootstrap.bat && .\b2 stage toolset=msvc --with-python from the boost project folder c:\boost This is the user-config.jam file in my home directory: using msvc : 14.0 : C:\\Program\ Files\ (x86)\\Microsoft\ Visual\ Studio\ 14.0\\VC\\bin\\cl.exe ; using python : 3.5 #