Re: [Boost-build] Telling the location of library files when using a different partition to modular-boost

Subject: Re: [Boost-build] Telling the location of library files when using a different partition to modular-boost
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-03-22 13:32:18

AMDG

On 03/22/2016 11:07 AM, Paul A. Bristow wrote:
> 
> in my jamfile I have
> 
> using  use-project /boost : i:/modular-boost ;
> requirement
> 
>     <library>/boost/system//boost_system
> 
> and 
> 
> run hello_boost_system.cpp ;
> 
> I get
> 
> LINK : fatal error LNK1104: cannot open file 'libboost_system-vc140-mt-sgd-1_60.lib'
> 
> but this file *does exist*:
> 
>                               I:\modular-boost\stage\lib\libboost_system-vc140-mt-sgd-1_60.lib
> 
> If I change to this run line (and remove the <library> )
> 
> run hello_boost_system.cpp /boost/system//boost_system ;
> 
> I get the same link error.
> 

This should be exactly equivalent to <library>.

> (Wondering if an absolute path was not allowed, if I try to create a relative path then I get this
> 

  It's impossible to create a relative path
to a different drive.

> <snip>
> 
> But if I add
> 
>    <library>/boost/thread//boost_thread
> 
> as well as
> 
>     <library>/boost/system//boost_system
> 
> then it all builds  and passes, as does
> 
> run hello_boost_system.cpp /boost/system//boost_system /boost/thread//boost_thread ;.
> 
> So I there is something I don't understand about library requirements for Boost.System and Boost.Chrono,
> 

  Now that is weird.  Does the compile command
for hello_boost_system change when adding
boost_thread?  In particular -DBOOST_ALL_NO_LIB
or some such might be added?

> but was misled by the failure to link (and that I still don't understand why).
> 

I'd need to see the linker commands to guess why.

In Christ,
Steven Watanabe