How to install boost linux

How to Install Boost on Ubuntu 16.04/18.04 Linux

This post will guide you how to install Boost libraries on Ubunt 16.04/18.04 Linux server. How do I install Boost C++ libraries 1.64 from a PPA in Ubuntu. How to install Boost from the default repositories on Ubuntu 16.04/18.04 Linux. How to install the latest version of Boost libraries from source package on Ubuntu Linux server.

What is Boost?

Boost is a set of libraries for the C++ programming language that provide support for tasks and structures such as linear algebra, pseudorandom number generation, multithreading, image processing, regular expressions, and unit testing. It contains over eighty individual libraries.

Install Boost C++ libraries via Default Repository

Boost is available on the default Ubuntu repositories, so you can install it with apt command directly, type the following commmand:

Verify the installed Boost Version

Once completed the installation process of Boost on your Ubuntu server, you can verify the installed boost version to check if the Boost is installed properly. Type one of the following commands to check version of boost:

Install Boost C++ libraries From PPA

You can also install Boost from a PPA on Ubuntu Linux, just type the following command:

This PPA can be added to your system manually by copying the lines below and adding them to your system’s software sources.

For Ubuntu 18.04:

For Ubuntu 18.10:

For Ubuntu 16.04:

Then you can try to install the Boost on your Ubuntu Linux, and the latest version of this PPA is 1.68, type the following command to install it:

Then the latest version 1.68 of boost would be installed on your Ubuntu Linux server.

Install Boost C++ libraries From Source Package

If you want to install the latest version of Boost( the current release version is 1.69) on your Ubuntu server, you have to install it from source package. And you need to download the latest archive package of boost from its official site firstly. . then execute the installation script. Just do the following steps:

#1 download source package of boost from this link with wget tool, type:

#2 extract all files from the archive file that you downloaded in the above step. type:

#3 Change the current directory to boost_1_69_0/, type:

#4 execute the script bootstrap.sh, type the following command:

#5 Builds and installs Boost with the following command:

Conclusion

You should know that how to install Boost C++ Libraries on your Ubuntu 16.04 or 18.04 Linux from this guide. And if you want to learn more about the Boost, you can go the below official web site to checking the getting started guide directly.

Источник

Programmer Think

Where programmers share thinking

How to Compile and Install Boost Libraries on Linux

Posted by ldb358 on Thu, 16 May 2019 20:02:36 +0200

Preface

When compiling a bitcoin wallet, you need to rely on the Boost library. Because it takes a long time to compile and wastes a lot of time in «give it a try», write down the successful process.

Download the Boost installation package

Anyway, I didn’t download it successfully

• Manually download installation packages
  Download to local location and upload to server at above address

decompression

Compile and Install

Enter the extracted directory first:

Then run the bootstrap.sh script and set the parameters:

—with-libraries specifies which boost libraries to compile. All is to compile all. Write the names of the libraries if you only want to compile some of them, separated by a sign. There are several libraries you can specify:

Library Name	Explain
atomic
chrono
context
coroutine
date_time
exception
filesystem
graph	Graph Components and Algorithms
graph_parallel
iostreams
locale
log
math
mpi	Metaprogramming Framework Implemented by Templates
program_options
python	Mapping C++ classes and functions into Python
random
regex	Regular Expression Library
serialization
signals
system
test
thread	Portable C++ Multithreaded Library
timer
wave

—with-toolset specifies which compiler to use at compilation time, GCC is sufficient on Linux. If you have multiple versions of GCC installed on your system, you can specify the version of GCC here, for example—with-toolset=gcc-4.4

When the command is executed, it is successful to see the following:

Start compiling boost by executing the following command:

The compilation takes about 10 minutes, wait patiently, and the following tips will follow at the end:

Finally, execute the following command to start installing boost:

—prefix=/usr is used to specify the boost installation directory. Without this parameter, the default header file is in the / usr/local/include/boost directory and the library file is in the / usr/local/lib/directory.If you specify the installation directory as—prefix=/usr, boost will be installed directly into the system header and library files directories, omitting the configuration environment variables.

The following tips will appear after installation:

Finally, note that if you want to compile with the boost library immediately after installation, you also need to execute this command:

Update the dynamic link library of the system.

Источник

Boost C++ Libraries

. one of the most highly regarded and expertly designed C++ library projects in the world. — Herb Sutter and Andrei Alexandrescu, C++ Coding Standards

Getting Started on Unix Variants

1 Get Boost

The most reliable way to get a copy of Boost is to download a distribution from SourceForge:

In the directory where you want to put the Boost installation, execute

RedHat, Debian, and other distribution packagers supply Boost library packages, however you may need to adapt these instructions if you use third-party packages, because their creators usually choose to break Boost up into several packages, reorganize the directory structure of the Boost distribution, and/or rename the library binaries. 1 If you have any trouble, we suggest using an official Boost distribution from SourceForge.

2 The Boost Distribution

This is a sketch of the resulting directory structure:

The organization of Boost library headers isn’t entirely uniform, but most libraries follow a few patterns:

Some older libraries and most very small libraries place all public headers directly into boost /.

Most libraries’ public headers live in a subdirectory of boost /, named after the library. For example, you’ll find the Python library’s def.hpp header in

Some libraries have an “aggregate header” in boost / that #includes all of the library’s other headers. For example, Boost.Python’s aggregate header is

Most libraries place private headers in a subdirectory called detail /, or aux_ /. Don’t expect to find anything you can use in these directories.

It’s important to note the following:

The path to the boost root directory (often /usr/local/ boost_1_66_0) is sometimes referred to as $BOOST_ROOT in documentation and mailing lists .

To compile anything in Boost, you need a directory containing the boost / subdirectory in your #include path.

Since all of Boost’s header files have the .hpp extension, and live in the boost / subdirectory of the boost root, your Boost #include directives will look like:

depending on your preference regarding the use of angle bracket includes.

Don’t be distracted by the doc / subdirectory; it only contains a subset of the Boost documentation. Start with libs / index.html if you’re looking for the whole enchilada.

3 Header-Only Libraries

The first thing many people want to know is, “how do I build Boost?” The good news is that often, there’s nothing to build.

Nothing to Build?

Most Boost libraries are header-only: they consist entirely of header files containing templates and inline functions, and require no separately-compiled library binaries or special treatment when linking.

The only Boost libraries that must be built separately are:

A few libraries have optional separately-compiled binaries:

• Boost.DateTime has a binary component that is only needed if you’re using its to_string/ from_string or serialization features, or if you’re targeting Visual C++ 6.x or Borland.
• Boost.Graph also has a binary component that is only needed if you intend to parse GraphViz files.
• Boost.Math has binary components for the TR1 and C99 cmath functions.
• Boost.Random has a binary component which is only needed if you’re using random_device.
• Boost.Test can be used in “header-only” or “separately compiled” mode, although separate compilation is recommended for serious use.
• Boost.Exception provides non-intrusive implementation of exception_ptr for 32-bit _MSC_VER==1310 and _MSC_VER==1400 which requires a separately-compiled binary. This is enabled by #define BOOST_ENABLE_NON_INTRUSIVE_EXCEPTION_PTR.

4 Build a Simple Program Using Boost

To keep things simple, let’s start by using a header-only library. The following program reads a sequence of integers from standard input, uses Boost.Lambda to multiply each number by three, and writes them to standard output:

Copy the text of this program into a file called example.cpp.

Now, in the directory where you saved example.cpp, issue the following command:

To test the result, type:

4.1 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. 3 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 Prepare to Use a Boost Library Binary

If you want to use any of the separately-compiled Boost libraries, you’ll need to acquire library binaries.

5.1 Easy Build and Install

Issue the following commands in the shell (don’t type $; that represents the shell’s prompt):

Select your configuration options and invoke ./bootstrap.sh again without the —help option. Unless you have write permission in your system’s /usr/local/ directory, you’ll probably want to at least use

to install somewhere else. Also, consider using the —show-libraries and —with-libraries= library-name-list options to limit the long wait you’ll experience if you build everything. Finally,

will leave Boost binaries in the lib/ subdirectory of your installation prefix. You will also find a copy of the Boost headers in the include/ subdirectory of the installation prefix, so you can henceforth use that directory as an #include path in place of the Boost root directory.

5.2 Or, Build Custom Binaries

If you’re using a compiler other than your system’s default, you’ll need to use Boost.Build to create binaries.

You’ll also use this method if you need a nonstandard build variant (see the Boost.Build documentation for more details).

5.2.1 Install Boost.Build

Boost.Build is a text-based system for developing, testing, and installing software. First, you’ll need to build and install it. To do this:

1. Go to the directory tools / build /.
2. Run bootstrap.sh
3. Run b2 install —prefix=PREFIX where PREFIX is the directory where you want Boost.Build to be installed
4. Add PREFIX / bin to your PATH environment variable.

5.2.2 Identify Your Toolset

First, find the toolset corresponding to your compiler in the following table (an up-to-date list is always available in the Boost.Build documentation).

If you previously chose a toolset for the purposes of building b2, you should assume it won’t work and instead choose newly from the table below.

Toolset Name	Vendor	Notes
acc	Hewlett Packard	Only very recent versions are known to work well with Boost
borland	Borland
como	Comeau Computing	Using this toolset may require configuring another toolset to act as its backend.
darwin	Apple Computer	Apple’s version of the GCC toolchain with support for Darwin and MacOS X features such as frameworks.
gcc	The Gnu Project	Includes support for Cygwin and MinGW compilers.
hp_cxx	Hewlett Packard	Targeted at the Tru64 operating system.
intel	Intel
msvc	Microsoft
sun	Oracle	Only very recent versions are known to work well with Boost. Note that the Oracle/Sun compiler has a large number of options which effect binary compatibility: it is vital that the libraries are built with the same options that your appliction will use. In particular be aware that the default standard library may not work well with Boost, unless you are building for C++11. The particular compiler options you need can be injected with the b2 command line options cxxflags=«and «linkflags=. For example to build with the Apache standard library in C++03 mode use b2 cxxflags=-library=stdcxx4 linkflags=-library=stdcxx4 .
vacpp	IBM	The VisualAge C++ compiler.

If you have multiple versions of a particular compiler installed, you can append the version number to the toolset name, preceded by a hyphen, e.g. intel-9.0 or borland-5.4.3 .

5.2.3 Select a Build Directory

Boost.Build will place all intermediate files it generates while building into the build directory. If your Boost root directory is writable, this step isn’t strictly necessary: by default Boost.Build will create a bin.v2/ subdirectory for that purpose in your current working directory.

5.2.4 Invoke b2

Change your current directory to the Boost root directory and invoke b2 as follows:

For a complete description of these and other invocation options, please see the Boost.Build documentation.

For example, your session might look like this:

That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “ —build-type=complete ”.

Building the special stage target places Boost library binaries in the stage / lib / subdirectory of the Boost tree. To use a different directory pass the —stagedir= directory option to b2.

b2 is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.

For a description of other options you can pass when invoking b2, type:

In particular, to limit the amount of time spent building, you may be interested in:

• reviewing the list of library names with —show-libraries
• limiting which libraries get built with the —with-library-name or —without-library-name options
• choosing a specific build variant by adding release or debug to the command line.

Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure everything is went well, you might redirect the output into a file by appending “ >build.log 2>&1 ” to your command line.

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:

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.Build mailing list.

6 Link Your Program to a Boost Library

To demonstrate linking with a Boost binary library, we’ll use the following simple program that extracts the subject lines from emails. It uses the Boost.Regex library, which has a separately-compiled binary component.

There are two main challenges associated with linking:

1. Tool configuration, e.g. choosing command-line options or IDE build settings.
2. Identifying the library binary, among all the build variants, whose compile configuration is compatible with the rest of your project.

There are two main ways to link to libraries:

You can specify the full path to each library:

You can separately specify a directory to search (with -L directory) and a library name to search for (with -l library, 2 dropping the filename’s leading lib and trailing suffix ( .a in this case):

As you can see, this method is just as terse as method A for one library; it really pays off when you’re using multiple libraries from the same directory. Note, however, that if you use this method with a library that has both static ( .a) and dynamic ( .so) builds, the system may choose one automatically for you unless you pass a special option such as -static on the command line.

In both cases above, the bold text is what you’d add to the command lines we explored earlier.

6.1 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. 4 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. 5	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.

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

6.2 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:

If you linked to a shared library, you may need to prepare some platform-specific settings so that the system will be able to find and load it when your program is run. Most platforms have an environment variable to which you can add the directory containing the library. On many platforms (Linux, FreeBSD) that variable is LD_LIBRARY_PATH, but on MacOS it’s DYLD_LIBRARY_PATH, and on Cygwin it’s simply PATH. In most shells other than csh and tcsh, you can adjust the variable as follows (again, don’t type the $—that represents the shell prompt):

On csh and tcsh, it’s

Once the necessary variable (if any) is set, you can run your program as follows:

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

7 Conclusion and Further Resources

This concludes your introduction to Boost and to integrating it with your programs. As you start using Boost in earnest, there are surely a few additional points you’ll wish we had covered. One day we may have a “Book 2 in the Getting Started series” that addresses them. Until then, we suggest you pursue the following resources. If you can’t find what you need, or there’s anything we can do to make this document clearer, please post it to the Boost Users’ mailing list.

Источник