Re: [Boost-build] clarification of install, prefix and stage when building boost

Subject: Re: [Boost-build] clarification of install, prefix and stage when building boost
From: Bioxydyn Dev (bioxydyn.dev_at_[hidden])
Date: 2013-08-22 13:28:06

Hi Steven,

Thanks for your reply. I have some follow up questions below.

On 22 August 2013 16:54, Steven Watanabe <watanabesj_at_[hidden]> wrote:

> AMDG
>
> On 08/22/2013 06:53 AM, Bioxydyn Dev wrote:
> > Hi,
> >
> > I have successfully built boost with the following options:
> >
> > ./b2 install --prefix=~/development/cots/boost stage <various other
> options>
> >
> > I notice that a directory ~/development/cots/boost is created in
> > $BOOST_ROOT which
> > contains lib and include sub directories. The contents of the include
> > directory appears to be the same as what is in $BOOST_ROOT/boost and the
> > lib contains the build output.
> >
> > A directory $BOOST_ROOT/stage/lib is also created which contains the
> build
> > output.
> >
> > I expected the latter but not the former.
> >
>
> The former is created by install, the latter by stage.
> Pick which one you want.
>

OK. So both are not usually required?

>
> > What is the --prefix option for?
>
> --prefix is used for install.
>
> > Should it be used when the stage option is
> > used?
>
> No.  Use --stage-dir
>
> > And why does it appear to result in the include files being
> > duplicated in another directory?
> >
>
> stage is intended for those working out of the source tree.
> install is intended to create a separate installation,
> that doesn't depend on the source.
>

I'm not sure I understand what the difference is.

What do you mean by 'working out of the source tree'?

As a developer, if you use a boost library that is header only how would
you not be dependent on the source?

regards

Joe