5481522e1f
Don't install org.eclipse.pde.api.tools.ee.feature.feature.group because it's no longer in the latest update site, and that causes problems like this one as noticed by a user: https://www.eclipse.org/forums/index.php?t=msg&th=1111320&goto=1854139&#msg_1854139 Move all the tasks up to the project level. Include a * requirement on the CDT targlet so that all projects are imported by the targlet task with no need for a separate import task. Probably many of the explicitly listed requirements are no longer needed because all requirements of all projects in the clone are resolved now automatically. Also ensure that all platforms are resolved so that all of CDT fragments are imported. Move the Git clone task before the modular targlet task so that the clone is available during the first resolution. Add an EclipseIni task so that the CDT.setup is redirected into the local clone's version such that you can modify that setup and test it locally via Help -> Perform Setup tasks (and so that Navigate -> Open Setup -> CDT opens the editable workspace version). https://bugs.eclipse.org/bugs/show_bug.cgi?id=580505 |
||
|---|---|---|
| .mvn | ||
| build | ||
| cmake | ||
| codan | ||
| core | ||
| cross | ||
| debug | ||
| doc | ||
| dsf | ||
| dsf-gdb | ||
| FAQ | ||
| images | ||
| jenkins/pod-templates | ||
| jsoncdb | ||
| jtag | ||
| launch | ||
| launchbar | ||
| llvm | ||
| lsp | ||
| memory | ||
| native | ||
| qt | ||
| releng | ||
| remote | ||
| terminal | ||
| testsrunner | ||
| tools.templates | ||
| unittest | ||
| util | ||
| visualizer | ||
| windows | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| .project | ||
| BUILDING.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Downloads.md | ||
| GitHubMigration.md | ||
| Jenkinsfile | ||
| LICENSE | ||
| POLICY.md | ||
| pom.xml | ||
| README.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.
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 or Eclipse IDE for Scientific Computing 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)
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.
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.
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.