David and Phillip -
Thanks for the responses.
I obviously made a blunder and didn't use: bjam "-sTOOLS=darwin".
One thing I noticed was compiling the hello world for debug works using: bjam
That threw me off, when I did a: bjam release
Is there a requirement to have python installed when building boost proper? I noticed 6 targets failed related to the unit testing and wondered if they were related to python.
Best regards,
Aaron R>
On 4/19/07, Phillip Seaver <phil@apago.com> wrote:
David Abrahams wrote, on 4/19/2007 4:12 AM:
> on Thu Apr 19 2007, Phillip Seaver <phil-AT-apago.com> wrote:
>
>
>> Based on the output directory, it looks like you're doing "using gcc
>> ..." when you need to do "using darwin ...".
>>
>
> How many times do people need to make this mistake before we recognize
> that gcc should refer to the apple compiler by default, on MacOS X?
>
It looks like gcc.jam has enough other platform-specific code in it
these days to justify moving the OS X support into there. I'll try to
find some time to do it, unless someone more qualified wants to. :-)
I probably won't be able to get to it for the next week or so, but it
fits in with my long-term plans to make a toolset for OS X that handles
SDK's, universal binaries, target OS version, application bundles, etc.
Phillip
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build