Re: [Boost-build] library output without comiler name

From: Vladimir Prus (vladimir_at_[hidden])
Date: 2008-07-10 10:30:20

Christoph Mayer wrote:

>>> I am writing a small script that automates the compilation of the boost
>>> libraries. The library will be used by people without root access and
>>> therefore can not be installed using e.g apt-get or system wide.
>>>
>>> The script currently looks as follows:
>>>
>>> cd boost_1_35_0
>>> mkdir build
>>> ./configure --prefix=$PWD/build --with-libraries=thread
>>> make
>>> make install
>>> cp ./libboost_thread-gcc*-mt.so ./libboost_thread.so
>>>
>>> The last copy line is very annoying and does not work in case gcc is not
>>> used. There is an option for bjam that directly outputs libraries in the
>>> form libboost_thread.so. Is it possible to use this by calling
>>> ./configure with additional parameters instead of using bjam directly?
> 
> 
>> I don't think so. I recommend using bjam directly for all cases.
> 
> Thanks for your answer. If I use bjam directly in my script I think I
> would call at first ./configure alone to trigger the building of the
> bjam executable. How can I then know where the executable resides? The
> directory seems to be dependent on the architecture (e.g x86).

You can use the same approach as configure script does:

arch=`cd $my_dir/tools/jam/src && ./bootstrap/jam0 -d0 -f
build.jam --toolset=$TOOLSET --toolset-root= --show-locate-target && cd ..`
  BJAM="$my_dir/tools/jam/src/$arch/bjam"

- Volodya