discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Installation issues with gnuradio on Ubuntu 12.04


From: Ron Economos
Subject: Re: [Discuss-gnuradio] Installation issues with gnuradio on Ubuntu 12.04
Date: Fri, 23 May 2014 23:15:05 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20

On 5/23/2014 10:54 PM, Activecat wrote:

On Fri, May 23, 2014 at 11:28 PM, Ron Economos <address@hidden> wrote:
Chose an install directory that makes sense
for you. /opt works well since it has the correct
permissions.

cd gnuradio
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/opt/gnuradio ..
make
sudo make install

This will build GnuRadio and install it in /opt/gnuradio


Will this later cause problem with OOT created with earlier version of gr_modtool?
It seems that the "/usr/local" has been "hard-coded" into some files of the OOT, as shown below.
Hence the OOT installation may fail to put all necessary files correctly into "/opt/gnuradio".

    address@hidden: ~/gnuradio/gr-mymodule1 $ grep -R /usr/local
    cmake/Modules/FindGnuradioRuntime.cmake:    PATHS /usr/local/include
    cmake/Modules/FindGnuradioRuntime.cmake:    PATHS /usr/local/lib
    cmake/Modules/FindGnuradioRuntime.cmake:          /usr/local/lib64
    cmake/Modules/FindCppUnit.cmake:    /usr/local/include
    cmake/Modules/FindCppUnit.cmake:    /usr/local/lib
    cmake/Modules/FindFFTW3.cmake:    PATHS /usr/local/include
    cmake/Modules/FindFFTW3.cmake:    PATHS /usr/local/lib
    cmake/Modules/FindFFTW3.cmake:    PATHS /usr/local/lib
    cmake/Modules/activecatConfig.cmake:          /usr/local/include
    cmake/Modules/activecatConfig.cmake:          /usr/local/lib
    cmake/Modules/activecatConfig.cmake:          /usr/local/lib64


Custom install locations do require some additional environment
setup. Sylvain gave me a nice shell script for that.

BASE=/opt/gnuradio
export PATH=${PATH}:${BASE}/bin
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${BASE}/lib64
export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:${BASE}/lib64/pkgconfig
export PYTHONPATH=${PYTHONPATH}:${BASE}/lib64/python2.7/site-packages/

Just change the first line to the directory of  your custom install.
Setting PKG_CONFIG_PATH will resolve finding packages
in OOT builds. Remember to use the same custom install prefix
in the cmake of your OOT builds.

Ron



reply via email to

[Prev in Thread] Current Thread [Next in Thread]