Thanks this help out with the problems and no warnings I dont thing. Thanks again maybe someone should add this to the docs! Michael On 24 Mar 2004, at 17:56, James Mastro wrote:

On Mar 24, 2004, at 8:45 AM, Michael Short wrote:

...

First I done find the bjam tool?

Second when I build the bjam tool myself I get the following error. Jamfile:71: in module scope rule unless unknown in module.

Here's how I built bjam:

Download the 1.31.0 sources from SourceForge from the link in my other mail. This will give you a folder called "boost_1_31_0" which I will call BOOST_ROOT.

To build bjam:

cd {BOOST_ROOT}/tools/build/jam_src sh ./build.sh

This builds bjam and jam in "{BOOST_ROOT}/tools/build/jam_src/bin.macosxppc". When you build boost, bjam needs to be in your path somewhere. I made a folder ~/bin which is in my path. I copied bjam and jam into ~/bin. Don't forget to add the folder to your $PATH variable if it isn't already.

Then to build the boost libs:

cd {BOOST_ROOT} bjam "-sTOOLS=darwin" install

I'm pretty sure that's all I did to get them to build and install. IIRC, almost all libs built without a problem. Also, it is possible you do not even need to build the boost libraries depending on what parts of boost you are using if you still have problems. I used the smart_ptr's only for a long time without ever building anything, since they are just template headers.

Most of this is just from http://www.boost.org/tools/build/jam_src/index.html#building_bjam

-jim

Michael Short writes:

Thanks this help out with the problems and no warnings I dont thing.

Thanks again maybe someone should add this to the docs!

As the original poster said, these instructions were lifted directly from "the docs". Please help us understand what to change so that others don't have trouble. -- Dave Abrahams Boost Consulting www.boost-consulting.com

Michael Short writes:

Hello

well I always have problem following unix like instructions but the main problem I had with these instruction was that there was a lot of if you have this system do that if you have that config do this, etc. Which ends up getting a little confusing

I don't see anything like that between the download step and the final section labelled "Additional Steps". Please be specific about where you got confused.

and it would seamed that the instructions just got complicated. It would be better to see a common/general step by step for system a,b and c, like Mac os x, pc, unix etc. leaving the more complete documents for those who have a custom config.

I don't understand what you're asking for. Every platform I know of is supported by a few different compilers. Do you think we should produce a separate document for each of M platforms x N compilers?

This is just my opinion but I think in the long run when one for each system is avalable then there will be no more problem like this which as boost gets more populare is going to happen. when more people start leaving windows and moving to linux or unix or macos then there are going to be a number of unformilare people lost in a unix back ground.

If you would like like any more input please ask.

Specific suggested changes to the docs (in the form of new text) would be a big help. -- Dave Abrahams Boost Consulting www.boost-consulting.com