Subject: [Boost-bugs] [Boost C++ Libraries] #3616: Boost.Test Xcode formatter not working in Xcode 3.2
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-11-12 20:06:13
#3616: Boost.Test Xcode formatter not working in Xcode 3.2
------------------------------------------------------+---------------------
Reporter: Sean P. DeNigris <sean@â¦> | Owner: rogeeff
Type: Bugs | Status: new
Milestone: Boost 1.41.0 | Component: test
Version: Boost 1.40.0 | Severity: Problem
Keywords: |
------------------------------------------------------+---------------------
The build result format has changed to:
[file path]:[line]: {warning|error}: [whatever]
e.g. /path/to/source.cpp:42: error: something bad happened!
Right now, the formatter outputs [file path]:[line]: [whatever]
The "warning: " or "error: " is missing, so the issue is not properly
displayed in Xcode
Possible solution:
1. move Apple-specific code to log_entry_start e.g.:
void log_entry_start( std::ostream& output,
boost::unit_test::log_entry_data const& entry_data, log_entry_types let )
{
switch( let ) {
...
case BOOST_UTL_ET_WARNING:
#ifdef __APPLE_CC__
output << file << ':' << line << ":
warning: ";
#endif
print_prefix( output,
entry_data.m_file_name, entry_data.m_line_num );
output << "warning in \"" <<
boost::unit_test::framework::current_test_case().p_name << "\": ";
break;
case BOOST_UTL_ET_ERROR:
#ifdef __APPLE_CC__
output << file << ':' << line << ": error:
";
#endif
print_prefix( output,
entry_data.m_file_name, entry_data.m_line_num );
output << "error in \"" <<
boost::unit_test::framework::current_test_case().p_name << "\": ";
break;
...
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.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/3616> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:01 UTC