https://svn.boost.org/trac10/ticket/2079 <p> [I'm writing this out of anger.] </p> <p> I'm trying out (again) the Boost.Build system on my Mac OS X 10.4.11 PowerPC system. I'm using a subversion working copy as my Boost base. The directions for the general GCC generally crash and burn. The documentation occasionally mentions the darwin keyword for Apple's special GCC, but there's isn't enough information to know how to use it. I'm currently struggling with support over one of our mailing lists. </p> <p> I think that nearly no one uses a generic GCC on the Mac (for cross-compiles or bleeding edge); they'll almost always use Apple's special GCC (to create Mac programs). So why the heck isn't full-blown Mac OS X support baked in the example configuration files (and documentation) out of the box? </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2079 Trac 1.4.3 Marshall Clow Sat, 26 Jul 2008 04:02:26 GMT https://svn.boost.org/trac10/ticket/2079#comment:1 https://svn.boost.org/trac10/ticket/2079#comment:1 <ul> <li><strong>owner</strong> set to <span class="trac-author">Marshall Clow</span> </li> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">assigned</span> </li> </ul> <p> I build on my Mac OS X box frequently; until quite recently (last month), I used a PPC box running 10.4.11. My user-config.jam contains a single line: </p> <blockquote> <p> import toolset : using ; using darwin ; </p> </blockquote> <p> and it seems to work just fine. </p> <p> What problems, exactly, are you having? </p> <p> P.S. The jam files for darwin have been significantly changed for 1.36.0 (thanks to Mat Marcus from Adobe and others) to build universal binaries, etc. </p> Ticket Marshall Clow Mon, 29 Sep 2008 22:19:03 GMT https://svn.boost.org/trac10/ticket/2079#comment:2 https://svn.boost.org/trac10/ticket/2079#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">assigned</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> I'm closing this bug because I think it was fixed in 1.36. </p> Ticket