CODEWITHSUNDEEP
c++boostvisual-studio-2015
SvinSimpe
SvinSimpe

Reputation: 870

Failing to build Boost 1.60.0 on Windows 10


I've used the Getting Started Guide that is provided from Boost.

Many of the existing problems with somewhat related nature seem to occur within Visual Studio and be due to faulty project settings and linking in particular.

My problems lies in actually getting Boost to build using the
Developer Command Prompt for VS2015 and running it as admin.

First I just extracted the folder and ran the VS2015 command prompt from the root folder with

bootstrap.bat

which gave me the following output

C:\Program Files (x86)\boost\boost_1_60_0>bootstrap.bat
Building Boost.Build engine

Failed to build Boost.Build engine.
Please consult bootstrap.log for further diagnostics.

You can try to obtain a prebuilt binary from

http://sf.net/project/showfiles.php?group_id=7586&package_id=72941

Also, you can file an issue at http://svn.boost.org
Please attach bootstrap.log in that case.

According to the bootstrap.log a lot of required header files were not found. According to the Visual C++ Team Blog the headers, sources and librares is now distributed on a different location on the user machines. This happend to me! I had to move a ton of headers and lib files from for it to find them.

However..... I can't figure out how to go on from this point.

Upvotes: 4

Views: 11549

Answers (1)

default
default

Reputation: 11635

Looking at your output at the end there are 4 suspicious warnings:

..\kernel32.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
..\advapi32.lib: warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
..\user32.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'
..\uuid.lib : warning LNK4272: library machine type 'x64' conflicts with target machine type 'X86'

Note the machine type, i.e. it probably related to which platform this is running for. Visual Studio Command Prompts come in different forms, make sure that you are running the correct one - In your case the correct one seems to be the VS2015 x64 Native Tools Command Prompt

Upvotes: 5

Related Questions