1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-04-21 21:52:10 +02:00
cdt/NewAndNoteworthy
Jonah Graham b8bd15844b Bug 571722: Add ALL_FLAGS for scanner discovery
This change adds the ALL_FLAGS that does not limit tool options to
those declared as IOption::isForScannerDiscovery when launching the
compiler to discover compiler built-ins.

This is needed as many other flags, either entered manually in "Other
flags" or some of the existing flags with checkboxes such as "-ansi",
"-fPIC", and "-fstack-protector-all" which all affect scanner discovery
as they can all change what macros are built-in to the compiler.

The current solution has as a drawback that some settings, like -I and -D
then appear twice. For example in the "Includes" node in the "Project
Explorer"

My only reservation about this change is if there is an option
that can be specified successfully at build time, but when used
at scanner discovery time causes the compiler to fail, or return
incorrect results. Therefore I have added a new field,
excludeFromScannerDiscovery to tool options (buildDefinitions
extension point) that allows tool integrators to always exclude
a command line option from ALL_FLAGS. I have also added
a new "Other flags (excluded from discovery)" to the
"Miscellaneous" tab to allow compiler options to be entered
by the user.
2022-11-21 10:46:49 -05:00
..
images Bug 571722: Add ALL_FLAGS for scanner discovery 2022-11-21 10:46:49 -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 Bug 571722: Add ALL_FLAGS for scanner discovery 2022-11-21 10:46:49 -05:00
CHANGELOG-API.md Bug 580015: add support for multiple bin parsers #75 2022-11-18 10:55:40 -05:00
README.md Fix CHANGELOG-API anchor (#168) 2022-11-15 21:35:27 +00:00

CDT Release Notes and New & Noteworthy

What's new and noteworthy in:

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.