Re: [SPAM] [jamboost] Re: Getting started with Boost Build and Linking to Boost libraries

From: Jason Stewart (jstewart_at_[hidden])
Date: 2005-09-23 17:02:43

At 05:21 PM 9/23/2005, you wrote:
>Caleb Epstein <caleb.epstein_at_[hidden]> writes:
>
> > On 9/22/05, David Abrahams <dave_at_[hidden]> wrote:
> >>
> >> > I should mention that c:\boost is an installed copy of boost, not a
> >> > full source tree. That is, I downloaded the source and ran 'bjam
> >> > install'. So it has an include directory and a lib directory but no
> >> > sources other than the headers in include.
> >>
> >> Oh, well, that's dumb. We should fix that.
> >

I was able to get my simple test working by putting the following 
Jamroot file into the c:\boost directory:

project boost
: usage-requirements <include>./include/boost-1_33
;

lib filesystem : : 
<file>./lib/libboost_filesystem-vc71-mt-gd-1_33.lib <variant>debug ;
lib filesystem : : 
<file>./lib/libboost_filesystem-vc71-mt-1_33.lib <variant>release ;

lib test : : 
<file>./lib/libboost_unit_test_framework-vc71-mt-gd-1_33.lib <variant>debug ;
lib test : : 
<file>./lib/libboost_unit_test_framework-vc71-mt-1_33.lib <variant>release ;

Obviously, this just defines two libraries and only two variants of 
those but it did compile correctly. I was able to link against the 
test framework by including "/boost//test" in the list of sources for 
my test harness. I don't know if there is a more automated way of 
generating this list of libraries supplied by boost along with all of 
the variants (different compilers, different threading options, etc.) 
but I guess it just needs to be done once per boost installation.

Another thing I noticed, This library depends on another library that 
I build (as demonstrated in the example that I sent yesterday). When 
I built the second (dependent library) the first one was built 
correctly but the unit tests for the first was not built. Is there a 
way to make it depend on the unit tests building and working?

Thanks for the help.

Jason Stewart