[Top][All Lists]

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

Re: [Discuss-gnuradio] Boost recipe in pybombs

From: Tim
Subject: Re: [Discuss-gnuradio] Boost recipe in pybombs
Date: Thu, 01 Aug 2013 15:58:53 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7


This is set because of the unfortunate way some version of
FindBoost.cmake are written
the order it searches for libs can look something like

1. check for libboostfoo-mt.so in $BOOST_ROOT
2. check for libboostfoo-mt.so in /usr/lib/
3. check for libboostfoo.so in $BOOST_ROOT
4. check for libboostfoo.so in /usr/lib/

A result of this is that if you build without the -mt tag, and you are
on a distro that has an older version of boost installed into /usr/lib/
system paths - $BOOST_ROOT will be ignored because it checks all the
search directories for each library naming case in an unfortunate order.
So building with -mt every time to ensures FindBoost.cmake picks up the
right prefixed boost library (if built from source) every time when
building other recipes that use boost & cmake.


On 08/01/2013 02:16 PM, Alexandru Csete wrote:
> The boost recipe in pybombs builds using the --layout=tagged option
> which will  generate libraries with the -mt suffix. The 'mt' stands
> for multi threaded and is only available for historical reasons,I
> suppose.
> Is there any particular reason for using this optionin pybombs? There
> are some linux distributions that have abandoned the -mt suffix and
> gnuradio builds just fine on those. Ubuntu still uses the -mt suffix
> but also creates softlinks  without the suffix, so it is safe for an
> application to only link to libboost-xyz without the suffix.
> Alex
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

reply via email to

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