Re: [Boost-build] How to link in boost libraries using boost-build?

From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2008-07-09 21:17:42

   Hi.

> So I thought I could do something like:
> 
>   lib program_options : : <link>shared <threading>multi <variant>debug 
> <toolset>msvc <name>boost_program_options-vc90-mt-gd-1_35
> 
> But
> 
> a) That just doesn't work.
> 
> b) boost-build doesn't seem to give me any way to distinguish between 
> vc90 and vc80.

   For our libraries we do something like this (example for one of the 
OpenSSL libraries):

lib eaylib_static_rtlStatic    : : <file>$(SSL_ROOT)/libcrypto.a 
        <toolset>gcc                               ;
lib eaylib_static_rtlStatic    : : 
<name>$(SSL_ROOT)/lib/VC/static/libeay32MTd <toolset>msvc <variant>debug 
               ;
lib eaylib_static_rtlStatic    : : 
<name>$(SSL_ROOT)/lib/VC/static/libeay32MT  <toolset>msvc 
<variant>release             ;
explicit eaylib_static_rtlStatic    ;

   And it works fine so I do not see what you mean by 'a) That just 
doesn't work'.

   You should be able to distinguish between different alternatives 
based on the toolset feature (e.g. <toolset>msvc-9.0) or the 
toolset:version subfeature (e.g. <toolset:version>9.0). Not sure if the 
toolset:version feature is spelled exactly like that, but that should be 
easy to check.

   I know that Boost Build has a bug though when you add properties 
conditioned on multiple other properties one of which is a versioned 
toolset. It then ignores all conditions other than that versioned 
toolset. But there is already a failing test case for this in the trunk.

   Hope this helps.

   Best regards.