https://svn.boost.org/trac10/ticket/2059 <p> If there's a formatter to print errors like Xcode uses, then a script could call a unit test with this formatter during the build stage and any problems can be traced to the problematic line in the Xcode IDE. This idea came from Richard Dingwall's blog entry "<a class="ext-link" href="http://richarddingwall.name/2008/06/01/using-the-boost-unit-test-framework-with-xcode-3/"><span class="icon">​</span>Using the Boost Unit Test Framework with Xcode 3</a>." </p> <p> Maybe it could be a default for Xcode systems, although that would break backwards compatibility. I think <code>__APPLE_CC__</code> is defined in the preprocessor when Xcode (or at least Apple's custom GCC) is used. </p> <p> I <a class="changeset" href="https://svn.boost.org/trac10/changeset/46924" title="Added support for an Xcode-compatible logging format during unit tests">recently made an example</a> to see if it worked and for my own testing. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2059 Trac 1.4.3 Daryle Walker Sun, 24 Aug 2008 02:02:13 GMT https://svn.boost.org/trac10/ticket/2059 https://svn.boost.org/trac10/ticket/2059 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">new_formatter.diff</span> </li> </ul> <p> Example diff of the changes required </p> Ticket Gennadiy Rozental Sun, 14 Sep 2008 19:05:33 GMT https://svn.boost.org/trac10/ticket/2059#comment:1 https://svn.boost.org/trac10/ticket/2059#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> applied in 48775 </p> Ticket