Re: [Boost-build] naive usage of bootstrap.sh

Subject: Re: [Boost-build] naive usage of bootstrap.sh
From: Robert Ramey (ramey_at_[hidden])
Date: 2016-10-24 10:27:38

On 10/23/16 3:15 PM, Vladimir Prus wrote:
> Robert,
>
> I think it behaves as documented. The prefix option specified where to
> install, not where to build, so the build happens in the root folder.
> You can pass --build-dir to b2 to change that.

Hmmm - read that as where to install b2.  I was surprised when b2 showed 
up in boost directory rather than the directory pointed to by the 
-prefix=<dest directory>.  I see now that prefix refers to the 
destination of the boost install rather than the destination of the b2 
executable.

I read --build-dir as the directory to be used to for temporary files to 
be used in the build not the destination of the b2 executable.

I really, really admire the developers of boost build and the effort 
they have put in trying to make this work.  But I think there is really 
something missing here.  It seems that there is interest in making the 
"next" version.  I would like to see:

a) small prototype
b) with it's own manual
c) subjected to test by naive but not dumb volunteers
d) who try to use the product by following the instructions in the manual.
e) and record their experience as they go
f) so the developers can make something that is easy to use.
h) as a means to keep product design on the right track.

Of course I think many, many programmers efforts could benefit from this 
type of prototyping.  But I realize that many development teams feel 
that they don't have enough time to do this.  Of course I think they're 
wrong - but that's only my opinion.

FWIW - I did allude to this in the first part of my presentation at 
CPPCon 2016.

Robert Ramey