[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-core-dev] Running a cppunit TestApplication in post-build step, and using the reports.
|
I've solved one of these problems myself today.
Kiwon Um wrote:
>
> 2. The testApp reports errors and some information for those that helps to
> track where it is, such as line number and file name, (e.g.
> main.cpp:21:Assertion...) using standard outputting into the console. But
> the eclipse's embedded problems view doesn't recognize it. Only compile
> errors and warnings are reported.
> Is there any good way to use that information to track the errors
> conveniently?
>
It could be resolved as follows:
outputter.setLocationFormat("%f:%l: "); // look carefully at the quotes,
the last space is there
The main point is that there must be (at least) one space between the line
number(:) and the description, e.g. main.cpp:21: Assertion... not
main.cpp:21:Assertion...
The eclipse's embedded problems view now recognizes the errors from the
console.
Kiwon Um wrote:
>
> 1. Post-build event is played only if there is at least one change of
> project.
> How can I set it to be executed always when I build my project?
>
However I really wonder how I could make the post-build step to be executed
always, it was the first question of me.
--
View this message in context: http://www.nabble.com/Running-a-cppunit-TestApplication-in-post-build-step%2C-and-using-the-reports.-tf4290269.html#a12230108
Sent from the Eclipse CDT - core mailing list archive at Nabble.com.
