Re: boost_config

From: David Abrahams (dave_at_[hidden])
Date: 2005-06-07 08:03:21

Jody Hagins <jody-boost-011304_at_[hidden]> writes:

> On Mon, 06 Jun 2005 14:48:28 -0400
> David Abrahams <dave_at_[hidden]> wrote:
>
>> The best thing to do is make a project with Boost.Build that uses
>> cross-project references to boost libraries (see the contents of
>> libs/python/example) and use that to build your project. The 2nd best
>> thing to do is to make a project with Boost.Build that uses
>> cross-project references to boost libraries (see the contents of
>> libs/python/example), then
>> 
>> bjam -a -obuild.log ...
>> 
>> and then look at the contents of build.log to see what command lines
>> to use.
>
> Thanks. BTW< did I miss something, or were you making a joke about the
> 1st and 2nd best approaches being exactly the same thing?

Almost the same. The best approach is to use Boost.Build to build
your project. The 2nd best approach is to find out how it would build
your project and reproduce the command lines in your own build system.

>> > Currently, our build system (based on make) does this reasonably
>> > well, but only because it is enforced manually in the make system.
>> 
>> I don't understand what you mean by "enforced manually"
>
> It means that I build the boost libraries, build the ACE+TAO libraries,
> build all the other libraries, then try to figure out how to make them
> all build with compatible options, and force our project build options
> to be the same. They are "enforced manually" by getting mad at anyone
> who changes them and causes stuff to break ;->

:)

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com