Domenico Andreoli wrote:

>  i missed all these posts on this report. i didn't understand there
>is all this interest in having bjam working.
>  
>

Domenico,

Here is a brief synopsis based on my rudamentary understanding:

bjam (short for Boost.Jam) is an interpreter, much like bash or perl. It
iterprets a langauge - in this case a super-set of the Jam language. The
changes are well-documented:
http://www.boost.org/tools/build/jam_src/index.html

Boost.Build (often abbrivate bbv1 for Boost.Build version 1 and bbv2 for
Boost.Build version 2) is a set of bjam files which provide the Boost
build environment for their libraries. Boost.Build depends on bjam, but
is a seperate, higher-level thing (it is basically a common API built on
top of bjam that you can use to make Jamfiles which function quite like
makefiles, albiet with a very different language). The documentation for
Boost.Build version 1 can be found here:
http://www.boost.org/tools/build/v1/build_system.htm

There is a very active mailing list which is mentioned on the above webpage.

The relevant .jam files are in BOOST_ROOT/tools/build/v1/ if you
download the boost source.

It should be possible to split the relevant portions out and put them in
debianized locations (it might take some work though).

It makes good sense to have a seperate bjam package, as bjam is useful
in its own rite as a seperate application, and does not need Boost.Build
to be useful. However, all the boost projects (and any project which
uses Boost.Build) need the Boost.Build files found in
BOOST_ROOT/tools/build (some projects will need v2, mine only use v1).

Good luck! I have found the jamboost mailing list I mentioned above
invaluable. Also, the online docs are a great place to start.

-Andy

-- 
C. Andy Martin
Senior Software Engineer
Lumenware, LLC
A161A ASTeCC Building
University of Kentucky
Lexington, KY 40506-0286
859/257-2300 x225
859/257-2489 (fax)
[EMAIL PROTECTED]
http://www.lumenware.com/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to