Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to set Error Parsers in Core Build projects' project properties. #753

Closed
ewaterlander opened this issue Apr 5, 2024 · 2 comments
Closed

Comments

@ewaterlander
Copy link
Contributor

Hi,

Core Build projects, CMake and Makefile, have no option in the project properties to change the used error parsers for the project. The only option is to change it in the global Workspace settings.

Managed Build projects do have this option in the project properties.
C/C++ Build >> Settings >> Error Parsers

I would like to have this option too for Core Build projects.

best regards,

Erwin Waterlander

@ewaterlander
Copy link
Contributor Author

The idea of Core Build projects is to "keep it simple" and settings follow as much as possible just from the selected toolchain in the launch configuration. See also Doug Schaefer's proposal for the Core Build flow and the initial discussions about the new flow Bug 321443 - Build Model Enhancements.

An LLVM error parser can be automatically selected based on the toolchain. A problem at the moment is that CDT does not have an LLVM error parser. See #752

@ewaterlander
Copy link
Contributor Author

What triggered this issue was that I was looking for an LLVM error parser, because of #752.
Issue #752 was fixed in #803. An LLVM parser is not needed at the moment, because the GCC parser can be used. It has now a tiny extension to also support LLVM remarks. Secondly the error parser can be automatically selected based on the toolchain. There is no extra option needed for this in the project properties.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant