[boost] Re: Customer Friendlier Boost Installation

From: David Abrahams (dave_at_[hidden])
Date: 2005-05-26 21:41:11

"Arkadiy Vertleyb" <vertleyb_at_[hidden]> writes:

> "David Abrahams" <dave_at_[hidden]> wrote
>
>> > error: unable to construct
>> > ../libs/program_options/build/boost_program_options
>>                                 ^^^^^^^^^^^^^^^^^^^^^
>>
>> That's a C++ library.  I see a correlation here ;-)
>>
>> How about editing your user-config.jam file?  You can copy it from
>> tools/build/v2/user-config.jam into your $HOME directory.
>
> I guess I am missing the whole picture here...  What are the pieces I need?
>
> 1) bjam -- I got it with Rene's install, and it's in my path.  I assume
> nothing else need to be done about it...

I don't know enough about Rene's thing to tell you for sure, but if
Rene installed a pre-built binary and hasn't recently updated his
installer program and you are using Boost's CVS you probably need a
more up-to-date version of bjam than the one he supplied you with,
because the CVS version of Boost.Build is using some features that
were recently added to bjam.  So I'd rebuild it -- it's trivial; just
go to the tools/build/jam_src subdirectory of your boost distro and
type

   C:\boost_cvs\boost\tools\build\jam_src> build

The result is in bin.ntx86\bjam.

> 2) Boost.Build 2 -- a bunch of jam files, tool description files, etc.  Does
> it come as a part of Boost?  

Yes.  C:\boost_cvs\boost\tools\build\v2

This is all detailed at

  http://engineering.meta-comm.com/resources/cs-win32_metacomm/doc/html/bbv2/installation.html

> When I have boost-build.jam, I understand where it's taken from,
> but since I removed it...  

Not sure I understand, but probably doesn't matter.

> Is it comming as a part of the current Boost tree?

C:\boost_cvs\boost\boost-build.jam

> I have boost_1_32_0, Boost CVS, and Boost Sandbox CVS.
> Should I use different Boost.Build in each tree?  

I might use the latest CVS Boost.Build in each tree, although you can
use the BBv2 from 1.32.0 in the boost_1_32_0 tree if you like.  The
latter is easier, as you won't have to replace boost-build.jam there
or point BOOST_BUILD_PATH at c:\boost_cvs\boost\tools\build\v2.

The boost-build.jam at the root of the sandbox CVS works by default if
the sandbox image is right next to the boost image, but if not you can
always set BOOST=c:\boost_cvs\boost in your environment or put
-sBOOST=c:\boost_cvs\boost on your bjam command-line and it will set
up your include paths correctly in sandbox projects (at least mine; I
can't vouch for what other people did).

> And I don't think

??

> 3) What is my $HOME directory?  The boost-sandbox\libs\typeof\doc?

Sorry, that was a Unix-ism.  Just

       set HOME=%HOMEPATH%

and it will be in c:\Documents and Settings\<your-user-name>

We ought to change it so it uses %HOMEPATH% instead of %HOME% by
default, on Windows.

> Assumming that I am trying to build the documentation...  And if I
> build the tests, will my $HOME be different?  

No, $HOME == %HOME%  i.e. whatever directory you set the HOME variable
to.

> Besides I don't see Boost.Build in the Boost Sandbox CVS...

Not a problem.

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