diff options
| author | Marcus Müller <marcus.mueller@ettus.com> | 2018-02-11 16:45:15 +0100 |
|---|---|---|
| committer | Martin Braun <martin.braun@ettus.com> | 2018-02-12 23:58:35 +0100 |
| commit | 98753b64483fc8bfc65cbf55f2f680ff16bdb9d7 (patch) | |
| tree | 55d997cb2cfecc7113aad2a9a824ed2951db8b94 /README.building-boost | |
| parent | 6ae02d1d6d04a5f529ab3fea496c589f8d14229d (diff) | |
Removing building-boost README: no longer necessary, out of place
With 3.8, we'll no longer support distros that ship a Boost too old for
GNU Radio. (And even on old distros, there's often an official way of
installing Boost 1.48 or later parallely without messing up the whole
system.)
Even if that changes in the future, I really don't think building
third-party dependencies is something that should be documented within
the GNU Radio source tree.
Diffstat (limited to 'README.building-boost')
| -rw-r--r-- | README.building-boost | 74 |
1 files changed, 0 insertions, 74 deletions
diff --git a/README.building-boost b/README.building-boost deleted file mode 100644 index e75ccda692..0000000000 --- a/README.building-boost +++ /dev/null @@ -1,74 +0,0 @@ -Most distributions have the required version of Boost (1.35) ready for -installation using their standard package installation tools (apt-get, -yum, etc.). - -If running a distribution that requires boost 1.35 (or later) be built -from scratch, these instructions explain how to do so, and in a way -that allows it to peacefully coexist with earlier versions of boost. - -Notice that this is **not** the usual case. If you're using a Linux distribution -shipping a boost version prior to 1.35, you should very strongly consider just -updating to a more recent version. Even CentOS / RedHat 6.9 ship sufficiently -recent versions. Distributions older than that are generally considered to be -end-of-life. - -There are two recommended methods (aside from the far more recommended method of -upgrading your system): Installing boost using the PyBOMBS utility, or building -it from a source tarball. - -1. Installing Boost using PyBOMBS ---------------------------------- - -You can -install a recent boost by downloading and executing the PyBOMBS utility: - -# go to a directory you have write access to -$ git clone git://github.com/pybombs/pybombs -$ cd pybombs -$ ./pybombs install boost - -The utility will take care of everything from thereon, install it from a -package source if a recent version is available for your system or build -it from source if necessary. - -2. Building Boost from a source tarball ---------------------------------------- - -Download the latest version of boost from boost.sourceforge.net. -(boost_1_49_0.tar.bz2 was the latest when this was written). Different -Boost versions often have different installations. If these -instructions don't work, check the website www.boost.org for more -help. - -unpack it somewhere -cd (change directory) into the resulting directory - -$ cd boost_1_49_0 - -# Pick a prefix to install it into. I used /opt/boost_1_49_0 - -$ BOOST_PREFIX=/opt/boost_1_49_0 - -$ ./bootstrap.sh -$ sudo ./b2 --prefix=$BOOST_PREFIX --with-thread --with-date_time --with-program_options --with-filesystem --with-system --layout=versioned threading=multi variant=release install - -# Done! That was easy! - -Note that you don't have to specify each library, which will then -build all Boost libraries and projects. By specifying only those -required will just save compilation time. - ----------------------------------------------------------------------- - -Installing GNU Radio with new Boost libraries. - -Tell Cmake to look for the Boost libraries and header files in the new location with the following command: - -$ cd <build directory> -$ cmake -DBOOST_ROOT=$BOOST_PREFIX -DBoost_INCLUDE_DIR=$BOOST_PREFIX/include/boost-1_49/ -DBoost_LIBRARY_DIRS=$BOOST_PREFIX/lib <path to gnuradio source tree> -$ make -$ make test -$ sudo make install - -See README for more installation details. - |