mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-04-21 21:52:10 +02:00
Code Issues Wiki Activity
cdt/NewAndNoteworthy
History
betamax cf359d59ad
Stops CMake build output folders being named "default" (#1084) 
The default IBuildConfiguration is no longer used by projects that use
ICBuildConfigurationProvider.

For CMake, Makefile and other Core Build projects the build output
folder is sometimes named "default" rather than the pattern
toolName.launchMode.toolchain OS.toolchain Arch.launchTarget Id (eg:
cmake.debug.win32.x86_64.Local). PR #1076 exposes new API
(ICBuildConfigurationProvider.getCBuildConfigName) to encourage this
naming pattern.

The "sometimes" is variable and often happens when a project is first
created when the active launch target is Local and the launch mode is
"run", but not always. This gives a random, inconsistent impression to
CDT.

The Platform project always contains a IBuildConfiguration with the name
IBuildConfiguration.DEFAULT_CONFIG_NAME. It seems the original Core
Build system design went to some length to fit in with this and always
make use of this IBuildConfiguration when pairing it with a new
ICBuildConfiguration.

With this PR, this no longer happens, allowing CDT code to be simplified
and the build folder naming made consistent, always adhering to
ICBuildConfigurationProvider.getCBuildConfigName.

Addresses Issue: CDT CMake Improvements #1000, IDE-82683-REQ-024 Default
CMake build folder
2025-02-19 20:55:50 -05:00
..
images Provide an example of extending CMake project type in Core Build (#1052) 2025-01-23 09:20:39 -05:00
OlderReleases Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-10.0.md Update wiki.eclipse links to their new locations 2022-11-09 10:56:55 -05:00
CDT-10.1.md Update wiki.eclipse links to their new locations 2022-11-09 10:56:55 -05:00
CDT-10.2.md Move https://wiki.eclipse.org/CDT/StandaloneDebugger to GitHub 2022-11-09 10:56:55 -05:00
CDT-10.3.md Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-10.4.md Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-10.5.md Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-10.6.md Update wiki.eclipse links to their new locations 2022-11-09 10:56:55 -05:00
CDT-10.7.md Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
CDT-11.0.md Add lack Dwarf5 support to release notes 2022-12-07 19:54:49 -05:00
CDT-11.1.md CDT 11.1.1 Release Notes updates 2023-03-20 09:27:32 -04:00
CDT-11.2.md Add Cross GCC toolchain uses GNU Elf Parser to N&N 2023-04-24 15:25:02 +01:00
CDT-11.3.md Add CDT LSP information to CDT's READMEs and N&N (#566) 2023-09-20 06:38:22 -04:00
CDT-11.4.md Convert \b to 0x7f to properly handle backspace in the terminal (#619) 2023-11-14 17:53:17 -05:00
CDT-11.5.md Bug579242: allow user to override CMake Settings (#683) 2024-02-07 13:52:58 -05:00
CDT-11.6.md Updates for CDT 11.6.1 (#858) 2024-07-02 21:11:07 -04:00
CDT-12.0.md Add bugs fixed in 12.0.0 milestone builds to N&N 2025-02-08 13:38:51 +00:00
CHANGELOG-API.md Stops CMake build output folders being named "default" (#1084) 2025-02-19 20:55:50 -05:00
README.md Update SimRel version for CDT 12.0 2025-02-08 17:12:40 +00:00

README.md

CDT Release Notes and New & Noteworthy

What's new and noteworthy in:

CDT LSP

The CDT LSP (LSP based C/C++ Editor) provides its own changelog highlighting its release notes and new and noteworthy entries.

Older Versions

Older Versions

Older Versions

Older versions of CDT's New & Noteworthy page have not been converted from Wikitext to GitHub markdown, instead these older pages have simply been saved from the browser to preseve them. This may lead to some minor rendering issues that hopefully do not detract too much from the overall information provided.

API Changes

The Eclipse CDT project announces and tracks breaking API changes in CHANGELOG-API.

How to write a New & Noteworthy entry

How to write a New & Noteworthy entry

Use the model of any of the previous New & Noteworthy entry pages as a starting point. CDT 10.3/2021-06 is a fairly extensive entry and is a useful page to copy examples from.

Using Images

Upload images to the images/ subfolder and prefix the file with the version number, e.g. CDT-10.5-. The images should be embedded using the <img> tag with (gernally) a width of 50% like this:

<p align="center"><img src="images/CDT-10.0-CTAD.jpg" width="50%"></p>

Referecing Code

Especially when writing New & Noteworthy entries about API it is useful to link to the file. This should be done using a relative path, such as:

The [SerialPort](../native/org.eclipse.cdt.native.serial/src/org/eclipse/cdt/serial/SerialPort.java) supports arbitrary baud rates.

which renders like this:

The SerialPort supports arbitrary baud rates.

API Changes and Improvements

Improvements and changes to API should be announced in the New and Noteworthy for the release so they get visibility. Linking directly to the code or Javadoc for the new API is encouraged.

API Breakages and Removals

Anything that breaks or removes API should be listed in the CHANGELOG-API. If the API change is very significant (such as a new version of Java) listing it in the New and Noteworthy for the release is also advisable.