Recent

This Page

User

Make error not cleared from Problem View

The Problem View

When building a project where errors or warnings are generated during the build, the Problems View will contain details of the errors/warnings, allowing you to quickly jump to the appropriate parts of your sources for fixing the issues.

Normally, when rebuilding your project after fixing the issues, the information in the Problems View will be cleared.

Issue in Code Red IDE v5

However when building a project with Code Red IDE v5 created with Code Red IDE v5.0.12 or earlier (including v4), if the project contains errors that cause a build failure, fixing the cause of the build failure may leave a make error in the Problems View, even though the build has now succeeded.

Resolving in Code Red IDE v5.0.14 or later

Right click over the make error in the Problems View and select "Delete" from the context sensitive menu.

Right click on the project in the Project Explorer View and select the context sensitive menu entry:

Tools -> Fixup Error Parsers

Now when you rebuild the project in future, any "fixed" errors from previous builds should automatically get removed from the Problems View.

Note that you will need to repeat this process for each project where you see the issue. However if you select multiple projects before right clicking in step 2, you can fix them all up at once.

Resolving in Code Red IDE v5.0.12 or earlier

Right click over the make error in the Problems View and select "Delete" from the context sensitive menu.

Select the Project in the Project Explorer View, then select from the main menu bar:

Project -> Properties -> C/C++ Build -> Settings -> Error Parsers

Then untick "CDT GNU Make Error Parser 6.0 (Deprecated)

Move "CDT GNU Make Error Parser 7.0" to the top of the list.

You will need to repeat these steps for both the Debug and Release build configurations of your project. Then when you rebuild the project in future, any "fixed" errors from previous builds should automatically get removed from the Problems View.

Note that you will need to repeat this process for each project where you see the issue.