Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
CDT/User/NewIn101
Contents
Release
This is the New & Noteworthy page for CDT 10.1 which is part of Eclipse 2020-12 Simultaneous Release
Update index and views with active configuration by default | The default preference controlling which configuration the index uses along with the affected views has been changed to use the active configuration instead of a fixed configuration. The new default should be less confusing for users as an initial setting but might not be suitable for all projects.
See the CDT User FAQ for instructions on how to change this preference. CDT extenders can also customize products using plugin_customization.ini, with org.eclipse.cdt.core/cprojectdescription.configRelations=1 (1 for "fixed", 2 for "active") See also Bug 329995 and cdt-dev. |
---|
Editor
Refactoring
Code Analysis
Parser
__has_include |
Parser support has been added for C++17 __has_include as well as the language extension __has_include_next. See Bug 566918. |
---|
Formatter
Build
Visual Studio 2017 and 2019 |
Support for detecting the Microsoft Visual C++ toolchain part of Visual Studio 2017 and 2019 has been added. Support for earlier versions has been removed. This support is still considered experimental since many basic features are missing for this CDT toolchain. See Bug 567169. |
---|
Debug
Launch Bar
Terminal
New activity for Terminal main toolbar contributions |
A new activity, org.eclipse.tm.terminal.view.ui.activity.maintoolbar, now can be used to disable main toolbar contributions of the Terminal plug-ins. Currently there is only one such contribution, a toolbar button to launch a terminal. See Bug 568923. Disabling of the TM terminal main toolbar button can now be done e.g. with a product customization file containing the line: org.eclipse.ui.workbench/UIActivities.org.eclipse.tm.terminal.view.ui.activity.maintoolbar=false The product customization file is specified to Eclipse arguments with: -pluginCustomization /some/path/plugin_customization.ini |
---|
API modifications
Bugs Fixed in this Release
See Bugzilla report Bugs Fixed in CDT 10.1