error_parsers.txt 1.1 KB

1234567891011121314151617181920212223242526
  1. Eclipse error parsers
  2. =====================
  3. These are a godsend for extracting & quickly navigating to
  4. warnings & error messages from console output. Unforunately
  5. I don't know how to write an Eclipse plugin so you'll have
  6. to add them manually.
  7. To add a console parser to Eclipse, go to Window --> Preferences
  8. --> C/C++ --> Build --> Settings. Click on the 'Error Parsers'
  9. tab and then click the 'Add...' button. See the table below for
  10. the parser fields to add.
  11. Eclipse will only parse the console output during a build, so
  12. running your unit tests must be part of your build process.
  13. Either add this to your make/rakefile, or add it as a post-
  14. build step in your Eclipse project settings.
  15. Unity unit test error parsers
  16. -----------------------------
  17. Severity Pattern File Line Description
  18. -------------------------------------------------------------------------------
  19. Error (\.+)(.*?):(\d+):(.*?):FAIL: (.*) $2 $3 $5
  20. Warning (\.+)(.*?):(\d+):(.*?):IGNORE: (.*) $2 $3 $5
  21. Warning (\.+)(.*?):(\d+):(.*?):IGNORE\s*$ $2 $3 Ignored test