fe74d8dfee
Summary: - Add some new API to make it easier for ISVs to provide defaults. - Fully connect UI elements to CMake build process - Add some missing UI elements (such as customizing generator) - CMake generator default within CDT changed to Ninja Details: Add API to set CMake generator default (eg Ninja) ISV can set their desired CMake generator by overriding `CMakeBuildConfiguration.getDefaultProperties`. ISVs can also further fine tune the build process by overriding `CMakeBuildConfiguration.getDefaultProperties` Remove API `IOsOverrides` and related code. `IOsOverrides` was a partial implementation to achieve builds in Docker containers, however the work was not complete and it the extra code was complicating some basic use cases of setting defaults Add support for all generators to CMake build settings UI page by using a Combo instead of radio buttons. The non-deprecated generators that are built-in to CDT populate the Combo, but additional generators can be manually entered in the Combo. Rename clean command to clean target to better reflect its use as the argument passed to cmake's --target command line. Add all target for the argument passed to cmake's --target command line when doing a normal build. Clarify usage of UI overrides and change the UI to be "use defaults" (i.e. invert the checkbox). This is a **breaking** change as it means user projects that were using UI overrides will revert to using defaults. This is done on purpose as so many little things have changed in CMake settings, that reverting to defaults on upgrade seems like a logical decision. In addition *use defaults* matches the other GUIs in Eclipse, for example the MBS build command settings. Populate all defaults in getDefaultProperties() so that all CMake build settings are displayed as used (greyed out) and can be used as a starting point when editing settings. Simplify some of the code in CMakeBuildTab. Fix parsing of extra args so that quoted strings work. Refactored manual tests document and brought it up to date. Correct command line option for CMake's --warn-unused-vars Correct command line option for CMake's --warn-uninitialized Overall this is an API breaking change and the CHANGELOG-API.md has been updated with all the API changes in and around ICMakeProperties, including fixing typos in WarnUninitialized methods. Fixes #1055 Fixes #818 Part of #1000 Co-authored-by: Jonah Graham <jonah@kichwacoders.com> |
||
|---|---|---|
| .github | ||
| .mvn | ||
| build | ||
| cmake | ||
| codan | ||
| core | ||
| cross | ||
| debug | ||
| doc | ||
| docker | ||
| dsf | ||
| dsf-gdb | ||
| FAQ | ||
| images | ||
| jenkins/pod-templates | ||
| jsoncdb | ||
| jtag | ||
| launch | ||
| launchbar | ||
| llvm | ||
| memory | ||
| native | ||
| NewAndNoteworthy | ||
| releng | ||
| remote | ||
| terminal | ||
| testsrunner | ||
| tools.templates | ||
| unittest | ||
| util | ||
| visualizer | ||
| windows | ||
| .backportrc.json | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| .project | ||
| BUILDING.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Downloads.md | ||
| GitHubMigration.md | ||
| Jenkinsfile | ||
| LICENSE | ||
| NOTICE.md | ||
| POLICY.md | ||
| pom.xml | ||
| README.md | ||
| StandaloneDebugger.md | ||
| TESTING.md | ||
Eclipse CDT™ C/C++ Development Tools
The Eclipse CDT™ Project provides a fully functional C and C++ Integrated Development Environment based on the Eclipse platform. Features include: support for project creation and managed build for various toolchains, standard make build, source navigation, various source knowledge tools, such as type hierarchy, call graph, include browser, macro definition browser, code editor with syntax highlighting, folding and hyperlink navigation, source code refactoring and code generation, visual debugging tools, including memory, registers, and disassembly viewers.
Highlights of recent releases and release notes are available in the New & Noteworthy.
See also https://projects.eclipse.org/projects/tools.cdt and https://eclipse.org/cdt
Download
The recommended way to obtain Eclipse CDT is to download it as part of the complete Eclipse IDE for C/C++ Developers or Eclipse IDE for Embedded C/C++ Developers from the main Eclipse IDE download site.
Alternatively Eclipse CDT can be installed into an existing Eclipse installation using this p2 URL: https://download.eclipse.org/tools/cdt/releases/latest/ (see how)
Download Development Builds
Milestone builds of the Eclipse IDE for C/C++ Developers or Eclipse IDE for Embedded C/C++ Developers can be found on the Eclipse Downloads page by clicking on the Eclipse Developer Builds tab (only present when there is a milestone build newer than the latest release).
Alternatively, milestone builds of Eclipse CDT can be installed into an existing Eclipse installation using one of the p2 URLs in: https://download.eclipse.org/tools/cdt/builds (see how). See cdt.aggrcon for which milestone is currently contributed to Eclipse SimRel.
Bleeding edge continuous (aka nightly) builds are available for the main branch from the p2 software repository: https://download.eclipse.org/tools/cdt/builds/cdt/main/
Download older versions
Downloads links for older versions are available in Downloads.
Help & Support
The Eclipse CDT (C/C++ Development Tools) User Guide can be found in the Eclipse Help - C/C++ Development User Guide.
The Eclipse forum for C/C++ IDE (CDT) is for users to ask questions on how to use Eclipse CDT. It is monitored by fellow users in the community for support. Stack Overflow also has an eclipse-cdt tag that can be added to questions or searched for prevous similar questions.
The Eclipse CDT Plug-in Developer Guide can also be found in the Eclipse Help - CDT Plug-in Developer Guide.
There is an FAQ covering many commonly asked questions for both user and developers and a Contribution Guide for guidance on editing Eclipse CDT's source and submitting changes.
Reporting issues
Please report issues in the GitHub issue tracker.
Vendor Supplied Eclipse CDT
Did you get your version of Eclipse CDT from a vendor (such as a chip maker)? If so, they generally support their customers. In that case issues and support questions should be directed at the vendor in the first instance.
We encourage all vendors who are extending and redistributing Eclipse CDT to engage with the project and contribute fixes and improvements back to the Eclipse CDT project.
CDT LSP (LSP based C/C++ Editor)
The Eclipse CDT project also provides an LSP based C/C++ Editor. Please see the CDT LSP repo for more details on that project and the future plans for language server protocol and clangd support in Eclipse CDT.
Contributing
Contributions are always welcome!
Please bear in mind that this project is almost entirely developed by volunteers. If you do not provide the implementation yourself (or pay someone to do it for you), the bug might never get fixed. If it is a serious bug, other people than you might care enough to provide a fix.
Add-ons for CDT
There are many third-party addons for CDT to make it more productive.
- CDT LSP: LSP based C/C++ Editor provided by the Eclipse CDT project
- cmake4eclipse: This Eclipse plug-in automatically generates build-scripts for the Eclipse CDT managed build system from CMake scripts.
- Sloeber: Eclipse Plugins based on Arduino toolchains or a enhanced Arduino IDE.
- SonarQube for Eclipse: Eclipse plug-in for static analysis for quality and security issues in your C/C++ code directly inside the IDE.
- CUTE: C++ unit testing plug-in
- Bracketeer: Auto-comments on closing brackets and highlight of matching/mismatching brackets
- And many more in the Eclipse Marketplace, for example, try the CDT tag
Have a tool that you want listed here? Please open a PR
Code of Conduct
This project follows the Eclipse Community Code of Conduct.
Migration from Gerrit, Bugzilla, Wiki, Eclipse Forums
In the summer of 2022 the Eclipse CDT project migrated from Gerrit, Bugzilla, Wiki, Eclipse Forums to GitHub based solutions. Please see GitHub Migration for more details.