>From what you are telling me it appears that I need to grab all which is in tools/build/v2 in order to build.  That's fine, I'm willing to bite that dep.  However it would be very useful if there was a step by step process somewhere which outlines how-to setup a project. 

It would also be nice if there were some open source projects which use bjam which I could reference.  After looking at (N) bjam files I can usually gleen the forest through the trees.

So if you know of any other projects which I can look @ that would be *useful*

-Tim

On 7/24/07, Roland Schwarz <roland.schwarz@chello.at> wrote:


Tim St. Clair wrote:
>     I'm looking for a nice mid-level example of a bjam project outside
> of boost, which uses boost.  All of the examples listed in the
> documentation are very simple and CANNED.  I want to know exactly what
> pieces I need in order for me to build, w/o dragging in the entire
> tools/build/v2 directory.

What do you mean by CANNED ? Do you mean everything below boost root?
If so, try to take the tools/build/v2/example/libraries as a starting
point.
1) Move it outside the tree.
2) Make sure either you have BOOST_BUILD_PATH pointing to
    .../tools/build/v2, have a boost-build.jam pointing there,
    or have the boost-build package (if you are on debian) installed.
3) Using boost libraries: If you want to be platform independent
    you currently have only one option: installing the source tree.
    Then in your Jamroot: "use-project boost : insert_path_to_boost"
4) Linking to boost libraries from bjam in a platform independent
    way is being worked on.

>     From reading the documentation, and looking at the bjam files
> created within boost, there is a fair amount of inconsistency on what
> one might consider to be "best-practices"...

Unfortunately true. This for the most part stems from the draft nature
of the Boost.Build manual I guess.

Roland

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build



--
Regards,
Timothy St. Clair
[timothysc@gmail.com]