Boost C++ Libraries: Ticket #3616: Boost.Test Xcode formatter not working in Xcode 3.2 https://svn.boost.org/trac10/ticket/3616 <p> The build result format has changed to: [file path]:[line]: {warning|error}: [whatever] e.g. /path/to/source.cpp:42: error: something bad happened! </p> <p> Right now, the formatter outputs [file path]:[line]: [whatever] </p> <p> The "warning: " or "error: " is missing, so the issue is not properly displayed in Xcode </p> <p> Possible solution: </p> <ol><li>move Apple-specific code to log_entry_start e.g.: </li></ol><p> void log_entry_start( std::ostream&amp; output, boost::unit_test::log_entry_data const&amp; entry_data, log_entry_types let ) { </p> <blockquote> <p> switch( let ) { </p> </blockquote> <p> ... </p> <blockquote> <p> case BOOST_UTL_ET_WARNING: </p> </blockquote> <p> #ifdef <span class="underline">APPLE_CC</span> </p> <blockquote> <p> output &lt;&lt; file &lt;&lt; ':' &lt;&lt; line &lt;&lt; ": warning: "; </p> </blockquote> <p> #endif </p> <blockquote> <p> print_prefix( output, entry_data.m_file_name, entry_data.m_line_num ); output &lt;&lt; "warning in \"" &lt;&lt; boost::unit_test::framework::current_test_case().p_name &lt;&lt; "\": "; break; </p> </blockquote> <blockquote> <p> case BOOST_UTL_ET_ERROR: </p> </blockquote> <p> #ifdef <span class="underline">APPLE_CC</span> </p> <blockquote> <p> output &lt;&lt; file &lt;&lt; ':' &lt;&lt; line &lt;&lt; ": error: "; </p> </blockquote> <p> #endif </p> <blockquote> <p> print_prefix( output, entry_data.m_file_name, entry_data.m_line_num ); output &lt;&lt; "error in \"" &lt;&lt; boost::unit_test::framework::current_test_case().p_name &lt;&lt; "\": "; break; </p> </blockquote> <p> ... </p> <p> I don't know what to do about "info" and "fatal error," because I don't know if there are corresponding levels in Xcode, but I'm posting the question to the Xcode users list. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/3616 Trac 1.4.3 Sean P. DeNigris <sean@…> Thu, 12 Nov 2009 20:30:19 GMT <link>https://svn.boost.org/trac10/ticket/3616#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3616#comment:1</guid> <description> <p> sorry... above lines: output &lt;&lt; file &lt;&lt; ':' &lt;&lt; line &lt;&lt;... should be: output &lt;&lt; entry_data.m_file_name &lt;&lt; ':' &lt;&lt; entry_data.m_line_num &lt;&lt;... </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Gennadiy Rozental</dc:creator> <pubDate>Mon, 23 Nov 2009 03:59:54 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/3616#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3616#comment:2</guid> <description> <p> Am I correct to understand that the only issue is absence of ':' in between error|warning and 'in' in messages. For example: file:line: error: in &lt;test_case&gt; ... would have worked? </p> </description> <category>Ticket</category> </item> <item> <author>Sean P. DeNigris <sean@…></author> <pubDate>Sat, 28 Nov 2009 23:51:00 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/3616#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3616#comment:3</guid> <description> <p> Yes, I think we actually want to insert "error: " and have "error" twice, as Xcode will eat the first one and keep the message intact - "file:line: error: error in &lt;test_case&gt;" <br /><br /> The only other issue is how to map info and fatal error. It seems fair to map info to warning and fatal error to error, so they would be:<br /> file:line: warning: info from &lt;test_case&gt;<br /> file:line: error: fatal error in &lt;test_case&gt; </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Raffi Enficiaud</dc:creator> <pubDate>Sat, 18 Mar 2017 13:33:25 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/3616#comment:4 https://svn.boost.org/trac10/ticket/3616#comment:4 <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">invalid</span> </li> </ul> <p> New versions of Xcode do not have this feature anymore </p> Ticket