How to install boost on windows

4.1   Build From the Visual Studio IDE

• From Visual Studio’s File menu, select New > Project…

• In the left-hand pane of the resulting New Project dialog,
  select Visual C++ > Win32.

• In the right-hand pane, select Win32 Console Application
  (VS8.0) or Win32 Console Project (VS7.1).

• In the name field, enter “example”

• Right-click example in the Solution Explorer pane and
  select Properties from the resulting pop-up menu

• In Configuration Properties > C/C++ > General > Additional Include
  Directories, enter the path to the Boost root directory, for example

  C:Program Filesboostboost_1_82_0

• In Configuration Properties > C/C++ > Precompiled Headers, change
  Use Precompiled Header (/Yu) to Not Using Precompiled
  Headers.²

• Replace the contents of the example.cpp generated by the IDE
  with the example code above.

• From the Build menu, select Build Solution.

To test your application, hit the F5 key and type the following
into the resulting window, followed by the Return key:

1 2 3

Then hold down the control key and press «Z», followed by the
Return key.

skip to the next step

4.2   Or, Build From the Command Prompt

From your computer’s Start menu, if you are a Visual
Studio 2005 user, select

All Programs > Microsoft Visual Studio 2005
> Visual Studio Tools > Visual Studio 2005 Command Prompt

or, if you’re a Visual Studio .NET 2003 user, select

All Programs > Microsoft Visual Studio .NET 2003
> Visual Studio .NET Tools > Visual Studio .NET 2003 Command Prompt

to bring up a special command prompt window set up for the
Visual Studio compiler. In that window, set the current
directory to a suitable location for creating some temporary
files and type the following command followed by the Return key:

cl /EHsc /I pathtoboost_1_82_0 pathtoexample.cpp

To test the result, type:

echo 1 2 3 | example

4.3   Errors and Warnings

Don’t be alarmed if you see compiler warnings originating in Boost
headers. We try to eliminate them, but doing so isn’t always
practical.⁴ Errors are another matter. If you’re
seeing compilation errors at this point in the tutorial, check to
be sure you’ve copied the example program correctly and that you’ve
correctly identified the Boost root directory.

5.1   Simplified Build From Source

If you wish to build from source with Visual C++, you can use a
simple build procedure described in this section. Open the command prompt
and change your current directory to the Boost root directory. Then, type
the following commands:

bootstrap
.b2

The first command prepares the Boost.Build system for use. The second
command invokes Boost.Build to build the separately-compiled Boost
libraries. Please consult the Boost.Build documentation for a list
of allowed options.

5.2   Or, Build Binaries From Source

If you’re using an earlier version of Visual C++, or a compiler
from another vendor, you’ll need to use Boost.Build to create your
own binaries.

b2 --build-dir=build-directory toolset=toolset-name --build-type=complete stage

C:WINDOWS> cd C:Program Filesboostboost_1_82_0
C:Program Filesboostboost_1_82_0> b2 ^
More? --build-dir="C:Documents and Settingsdavebuild-boost" ^
More? --build-type=complete msvc stage

b2 --help

5.3   Expected Build Output

During the process of building Boost libraries, you can expect to
see some messages printed on the console. These may include

• Notices about Boost library configuration—for example, the Regex
  library outputs a message about ICU when built without Unicode
  support, and the Python library may be skipped without error (but
  with a notice) if you don’t have Python installed.

• Messages from the build tool that report the number of targets
  that were built or skipped. Don’t be surprised if those numbers
  don’t make any sense to you; there are many targets per library.

• Build action messages describing what the tool is doing, which
  look something like:

  toolset-name.c++ long/path/to/file/being/built
  

• Compiler warnings.

5.4   In Case of Build Errors

The only error messages you see when building Boost—if any—should
be related to the IOStreams library’s support of zip and bzip2
formats as described here. Install the relevant development
packages for libz and libbz2 if you need those features. Other
errors when building Boost libraries are cause for concern.

If it seems like the build system can’t find your compiler and/or
linker, consider setting up a user-config.jam file as described
here. If that isn’t your problem or the user-config.jam file
doesn’t work for you, please address questions about configuring Boost
for your compiler to the Boost Users’ mailing list.

Auto-Linking

Most Windows compilers and linkers have so-called “auto-linking
support,” which eliminates the second challenge. Special code in
Boost header files detects your compiler options and uses that
information to encode the name of the correct library into your
object files; the linker selects the library with that name from
the directories you’ve told it to search.

The GCC toolchains (Cygwin and MinGW) are notable exceptions;
GCC users should refer to the linking instructions for Unix
variant OSes for the appropriate command-line options to use.

6.1   Link From Within the Visual Studio IDE

Starting with the header-only example project we created
earlier:

1. Right-click example in the Solution Explorer pane and
   select Properties from the resulting pop-up menu
2. In Configuration Properties > Linker > Additional Library
   Directories, enter the path to the Boost binaries,
   e.g. C:Program Filesboostboost_1_82_0lib.
3. From the Build menu, select Build Solution.

skip to the next step

6.2   Or, Link From the Command Prompt

For example, we can compile and link the above program from the
Visual C++ command-line by simply adding the bold text below to
the command line we used earlier, assuming your Boost binaries are
in C:Program Filesboostboost_1_82_0lib:

cl /EHsc /I pathtoboost_1_82_0 example.cpp   ^
     /link /LIBPATH:C:Program Filesboostboost_1_82_0lib

6.3   Library Naming

In order to choose the right binary for your build configuration
you need to know how Boost binaries are named. Each library
filename is composed of a common sequence of elements that describe
how it was built. For example,
libboost_regex-vc71-mt-d-x86-1_34.lib can be broken down into the
following elements:

lib

Prefix: except on Microsoft Windows, every Boost library
name begins with this string. On Windows, only ordinary static
libraries use the lib prefix; import libraries and DLLs do
not.⁵

boost_regex

Library name: all boost library filenames begin with boost_.

-vc71

Toolset tag: identifies the toolset and version used to build
the binary.

-mt

Threading tag: indicates that the library was
built with multithreading support enabled. Libraries built
without multithreading support can be identified by the absence
of -mt.

-d

ABI tag: encodes details that affect the library’s
interoperability with other compiled code. For each such
feature, a single letter is added to the tag:

Key	Use this library when:	Boost.Build option
s	linking statically to the C++ standard library and compiler runtime support libraries.	runtime-link=static
g	using debug versions of the standard and runtime support libraries.	runtime-debugging=on
y	using a special debug build of Python.	python-debugging=on
d	building a debug version of your code.6	variant=debug
p	using the STLPort standard library rather than the default one supplied with your compiler.	stdlib=stlport

For example, if you build a debug version of your code for use
with debug versions of the static runtime library and the
STLPort standard library,
the tag would be: -sgdp. If none of the above apply, the
ABI tag is ommitted.

-x86

Architecture and address model tag: in the first letter, encodes the architecture as follows:

Key	Architecture	Boost.Build option
x	x86-32, x86-64	architecture=x86
a	ARM	architecture=arm
i	IA-64	architecture=ia64
s	Sparc	architecture=sparc
m	MIPS/SGI	architecture=mips*
p	RS/6000 & PowerPC	architecture=power

The two digits following the letter encode the address model as follows:

Key	Address model	Boost.Build option
32	32 bit	address-model=32
64	64 bit	address-model=64

-1_34

Version tag: the full Boost release number, with periods
replaced by underscores. For example, version 1.31.1 would be
tagged as «-1_31_1».

.lib

Extension: determined according to the operating system’s usual
convention. On most unix-style platforms the extensions are
.a and .so for static libraries (archives) and shared
libraries, respectively. On Windows, .dll indicates a shared
library and .lib indicates a
static or import library. Where supported by toolsets on unix
variants, a full version extension is added (e.g. «.so.1.34») and
a symbolic link to the library file, named without the trailing
version number, will also be created.

6.4   Test Your Program

To test our subject extraction, we’ll filter the following text
file. Copy it out of your browser and save it as jayne.txt:

To: George Shmidlap
From: Rita Marlowe
Subject: Will Success Spoil Rock Hunter?
---
See subject.

Now, in a command prompt window, type:

pathtocompiledexample < pathtojayne.txt

The program should respond with the email subject, “Will Success
Spoil Rock Hunter?”

Onward

Good luck, and have fun!

—the Boost Developers

#include <boost/array.hpp>

#include <iostream>

using namespace std;

int main()

{

    boost::array<int, 10> arr

        = { { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 } };

    for (int i = 0; i < 10; i++) {

        cout << "Geek Rank is :" << arr[i] << "*"

             << "n";

    }

    return 0;

}

results matching ««

These instruction assume that cygwin has been installed to c:cygwin.

Install these packages:

Now we need to configure Boost.Build to use these tools. This step
is different depending on whether you’re using Boost.Build built with
cygwin, or for native windows. For cygwin you need to add to your
user-config.jam file:

using xsltproc ;

using boostbook
    : /usr/share/docbook-xsl
    : /usr/share/xml/docbook/4.2
    ;

using quickbook ;

# If you installed doxygen:
using doxygen ;

When using a native (non-Cygwin) Boost.Build, you’ll need to specify
the windows paths to the various tools:

# Adjust this path to the location of your cygwin install.
CYGWIN_DIR = c:/cygwin ;

using xsltproc
    : $(CYGWIN_DIR)/bin/xsltproc.exe ;

using boostbook
    : $(CYGWIN_DIR)/usr/share/docbook-xsl
    : $(CYGWIN_DIR)/usr/share/xml/docbook/4.2
    ;

using quickbook ;

# If you installed doxygen:
using doxygen
    : $(CYGWIN_DIR)/bin/doxygen.exe
    ;

In order to install the tools under windows, we need to create a directory
structure somewhat similar to the unix filesystem. We’re going to place
this in c:boost-tools, if you want to put it elsewhere,
just follow the instructions, adjusting the paths accordingly. This
is also a good location to use as the prefix when installing Boost.Build.

Next you need to download several xml tools from Igor
Zlatkovic. You require: iconv, libxml2
and libxslt, zlib. Then unzip
these into the c:boost-tools directory. This should
place the xsltproc exectuable in c:boost-toolsbin.

Next make a directory for xml processing files at c:boost-toolsxml.

user-config.jam in the boost build search path,
for most people this will be C:Documents and Settingsusername.

BOOST_TOOLS_DIR = c:/boost-tools ;
using xsltproc
    : $(BOOST_TOOLS_DIR)/bin/xsltproc.exe"
    ;

using boostbook
    : $(BOOST_TOOLS_DIR)/xml/docbook-xsl
    : $(BOOST_TOOLS_DIR)/xml/docbook-xml
    ;

using quickbook ;

Also, if you wish to use doxygen to generate reference documentation
from C++ source headers, you’ll need to install it. You can download
it from the
doxygen website. The installer should add the executable to
your path, so you just need to add to your user-config.jam:

using doxygen ;