Re: boost-build.jam documentation issues

From: Peter Foley (pjfoley_at_[hidden])
Date: 2005-08-12 04:28:55

Hi List,

Comments inline.

> David Abrahams wrote:
>> Andrey Melnikov <melnikov_at_[hidden]> writes:
>
>> I think it would be better to ship BB as a separate package 
>
> It is being shipped also as a separate package.

In my humble opinion I think this is not a true statement!!!

Note I am basing this on the fact that the boost.build download on
sourceforge is from October 29, 2004.

What I think Andrey is asking for is the ability to download a package
(installer) and that is all you need to use Bjam.

Currently to use bjam you need to either download a version of boost (1.32,
1.33 or CVS) and then compile a the version of bjam sources that you have.
Or download the already compiled version of bjam, _plus_ download a version
of the boost sources.

The reason you need the boost sources (in addition to the bjam.exe) is for
the %boost_root%/tools/build/[v1 || v2] directories. Without the additional
files in these directories you cannot use bjam. I am guessing that a number
of these files will have bugs that have been fixed more recently.

Also something that I would prefer to see would be something like the
installer that Rene posted late June. See
http://article.gmane.org/gmane.comp.lib.boost.devel/126668 another useful
link is http://sourceforge.net/project/shownotes.php?release_id=337287. 

Unfortunately this does not provide a complete bjam install instance, it
only installs the bjam.exe file in the bin directory. What is interesting
about Rene's installer is the fact that he has incorporated all the docbook
stuff so you could create docbooks without the boost source installed.

When I think of a package (or installer) it suggests to me that if I
download and install this package I have the capability to use the installed
software.

>
>> or at least not inside BOOST_ROOT.
>
> I don't see why that would be better. At any rate, it seems like a
> very unimportant change to make.

This really depends on what your (and the other developers) objective of
bjam is.

I know that technically bjam is the sharp end of the Boost.Build process,
but if you want other people to start using bjam as a MAKE (or insert other
build system) replacement I think it is important to make it easier to
install bjam without needing to install the latest boost source.

Please bare in mind I am only talking about an installer, the sources can
stay in the boost CVS and be managed as part of the boost project.

Peter.