Re: [Boost-build] force linking with boost libs with same variant as own project build

From: Andrej van der Zee (mavdzee_at_[hidden])
Date: 2008-07-09 23:55:56

Hi,

> 
>    Simple add alternatives for your lib targets
> based on the variant 
> property. For example:
> 
> lib eaylib_static_rtlStatic    : : 
> <name>$(SSL_ROOT)/lib/VC/static/libeay32MTd
> <variant>debug               ;
> lib eaylib_static_rtlStatic    : : 
> <name>$(SSL_ROOT)/lib/VC/static/libeay32MT 
> <variant>release             ;
> explicit eaylib_static_rtlStatic    ;
> 

Yes that is simple enough indeed (maybe it should be
added to boost docs for site-config.jam?). Thanks
alot!

Is there a way that I can adjust my install rule based
on the variant too? Currently I am using the rules
like below, but it obviously copies both the release
and debug build. Any idea?

install dist-lib
    : [ glob $(boost-library-path)/*boost_system* ]
    [ glob $(boost-library-path)/*boost_thread* ]
    [ glob $(boost-library-path)/*boost_regex* ]
    [ glob $(boost-library-path)/*boost_data_time* ]
    [ glob $(boost-library-path)/*boost_filesystem* ]
    : <install-type>SHARED_LIB
    <os>CYGWIN:<location>$(install-path)/bin
    <os>LINUX:<location>$(install-path)/lib
    <os>AIX:<location>$(install-path)/lib
    ;

Cheers,
Andrej

      __________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html