[boost] Re: Build serialization13 outside source tree?

From: Larry Evans (cppljevans_at_[hidden])
Date: 2003-12-16 12:18:46

On 11/20/2003 11:30 AM, Robert Ramey wrote:
> Neal D. Becker wrote:
[snip]
>>Can I build serialization13 without first merging it into a complete boost 
>>source tree?
> 
> 
> There is no inherent reason this can't be done.  It just seems more
> convenient to me. I don't know what platform/compiler you want to 
> try it on so I don't know how much fussing around with include
> paths, compiler settings, etc will be necessary.

It looks like boost-sandbox/libs/socket/example/Jamfile did this, but
I haven't tried it myself.  However, I have tried emulating what was in
boost-1.30.2/libs/smart_ptr/test/Jamfile, but with just:

     dev_dir = ../../../.. ;
     B_ROOT = $(dev_dir)/../boost-release/boost-1.30.2 ;
     includes = <include>$(dev_dir) ;
     lnklibs =
       <lib>$(B_ROOT)/libs/test/build/boost_prog_exec_monitor
       ;
     test-suite "smart_ptr"
       : [ run smart_ptr_test.cpp $(lnklibs) : : : $(includes) ]
#      : [ compile get_policy_compile-pass.cpp : $(includes) ]
       ;

in the body of {...}.  I get:

cd /home/evansl/prog_dev/boost_dev/libs/managed_ptr/test/latest/
bjam
unknown dependent target 
<..!boost-release!boost-1.30.2!libs!test!build>libboost_prog_exec_monitor.a

A search on ouput of bjam -d+5, for the string <..! show a hit at:

/home/evansl/prog_dev/boost-release/boost-1.30.2/tools/build/allyourbase.jam:1390:>>>>|>>>>|>>>>|>>>>|>> 
set BOOST_ROOT += /home/evansl/prog_dev/boost-release/boost-1.30.2
/home/evansl/prog_dev/boost-release/boost-1.30.2/tools/build/boost-base.jam:1543:>>>>|>>>>|>>>>|>>> 
FGristFiles libboost_prog_exec_monitor.a
/home/evansl/prog_dev/boost-release/boost-1.30.2/tools/build/boost-base.jam:1543:>>>>|>>>>|>>>>|>>> 
local lib-target = 
<..!boost-release!boost-1.30.2!libs!test!build>libboost_prog_exec_monitor.a
/home/evansl/prog_dev/boost-release/boost-1.30.2/tools/build/boost-base.jam:1548:>>>>|>>>>|>>>>|>>> 
find-compatible-subvariant 
<..!boost-release!boost-1.30.2!libs!test!build>libboost_prog_exec_monitor.a 
: gcc debug : <architecture>native <debug-symbols>on <inlining>off 
<instruction-set>default <optimization>off <profiling>off <rtti>on 
<shared-linkable>false <threading>single <vtable-thunks>default 
<runtime-link>dynamic <target-type>RUN

The comments preceding rule relative-path may be relevant:

# try to make a potentially absolute path relative to the project
# root.  Only works for paths below the project root right now; others
# will remain absolute.

> 
> If fact, if your going down this path, you really don't even need to
> build the library.   You might get what you want by just including
> the *.cpp files in your project.

But this would mean duplicating the .o files under

   boost-1.30.2/tools/build/

But that's maybe a minor point.