|
|
Boost-Build : |
From: Caleb Epstein (caleb.epstein_at_[hidden])
Date: 2005-09-22 17:23:02
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.
This is one of the major mind-bogglers I have encountered when trying to use
Boost Build. You can't use it with an installed Boost directory, only with
the unpacked source distribution. That doesn't seem like the best idea to
me, especially since the layout of the bin[.v2] directory doesn't take into
account architecture-specifics (e.g. I have
$BOOST_ROOT/bin.v2/libs/test/build/gcc; are those from gcc-on-Linux or
gcc-on-Solaris?)
What I would expect would be that "bjam install" would install all of the
Boost headers, compiled libraries, the Boost Build plumbing, and any
Jamfiles[.v2] necessary to link with those compiled libraries. These
Jamfiles might necessarily be different than the ones used to build the
library in the first place. They should only provide information about the
required compiler flags for building code that links with the library, and
the necessary library names to link. There should be no information about
how to build the library itself, since the sources aren't available.
-- Caleb Epstein caleb dot epstein at gmail dot com ------=_Part_7594_24879782.1127427782054 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 9/22/05, <b class="gmail_sendername">David Abrahams</b> <<a href="mailto:dave_at_[hidden]">dave_at_[hidden]</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > I should mention that c:\boost is an installed copy of boost, not a<br>> full source tree. That is, I downloaded the source and ran 'bjam<br>> install'. So it has an include directory and a lib directory but no <br>> sources other than the headers in include.<br><br>Oh, well, that'sdumb. We should fix that.</blockquote><div><br> This is one of the major mind-bogglers I have encountered when trying to use Boost Build. You can't use it with an installed Boost directory, only with the unpacked source distribution. That doesn't seem like the best idea to me, especially since the layout of the bin[.v2] directory doesn't take into account architecture-specifics (e.g. I have $BOOST_ROOT/bin.v2/libs/test/build/gcc; are those from gcc-on-Linux or gcc-on-Solaris?)<br> <br> What I would expect would be that "bjam install" would install all of the Boost headers, compiled libraries, the Boost Build plumbing, and any Jamfiles[.v2] necessary to link with those compiled libraries. These Jamfiles might necessarily be different than the ones used to build the library in the first place. They should only provide information about the required compiler flags for building code that links with the library, and the necessary library names to link. There should be no information about how to build the library itself, since the sources aren't available.<br> </div></div><br>-- <br>Caleb Epstein<br>caleb dot epstein at gmail dot com ------=_Part_7594_24879782.1127427782054--
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk