The 2022-12 M1 build from Platform may have a regression that is causing
CDT build to fail more often due to deadlock in the indexer.
This commit uses 2022-09 R build of Platform to avoid the problem.
Note that this won't resolve the issue in Platform, but will allow
CDT to be built.
Fixes#81
This project is an example, it is not part of what is
released with CDT. To make this clearer I have renamed
the project to include "example" in the name.
This commit migrates all the N&N content from
https://wiki.eclipse.org/CDT/User/NewInCDT to GitHub.
For newer releases (>= CDT 10.0) the entire content has
been rewritten in GitHub flavour Markdown. For older
releases, the N&N page has simply been saved in a
rendered format.
Switch to CTabFolder/CTabItem for newui.
This changeset is a breaking change but on a review of existing
adopters/extenders of CDT no one is actually accessing these fields.
Change-Id: Ic1ef0f242c1d2932726f3a6d4c9df9558312764a
Signed-off-by: Torbjörn Svensson <torbjorn.svensson@st.com>
Also-by: Jonah Graham <jonah@kichwacoders.com>
The scripts assume that /bin/sh is bash, but it isn't on all installs,
in particular Ubuntu: https://wiki.ubuntu.com/DashAsBinSh
Change-Id: I8ea05b2ffd1fd41b3aa1e6b395e43fc15a15321f
The only time the stack service is unavailable is:
1. Stack service hasn't been started yet
2. Stack service has been shutdown
3. Stack service never gets created
All of these cases are configuration error, except (2). In (2) the
stack service isn't available to do source lookup, so instead
of an error, simply return no file (aka null)
Fixes#53
* Docker: Allow setting a mapping for docker paths
Bug 579944 introduced using Windows paths, to allow putting your project
into the WSL's file system.
While Docker for Windows (the commercial version) supports Windows
paths, this does not work with a OSS-docker installed in the WSL.
It is now possible to provide a path mapping to work around this.
Co-authored-by: Jeff Johnston <jjohnstn@redhat.com>
Adds constexpr evaluation for some additional compiler builtins. This is
probably the last lot few builtins that can reasonably be
constexpr-evaluated in CDT.
testAbstractBuiltinSpecsDetector_EnvChangesGlobal did not properly clean
up after itself, which caused
testAbstractBuiltinSpecsDetector_EnvChangesConfiguration_1,
testAbstractBuiltinSpecsDetector_EnvChangesConfiguration_2, and
testAbstractBuiltinSpecsDetector_EnvChangesGlobal to fail when run for
the second time in the same session.
Running tests twice is not useful, but happens in Eclipse with a launch
configuration set to run all tests in
org.eclipse.cdt.managedbuilder.core.tests/tests - once directly and once
through AllLanguageSettingsProvidersMBSTestSuite. I have not found any
way of running every test exactly once in the GUI.
gcc linker outputs "removing unused section" to stderr when the option "--print-gc-sections" is used. That is fine.
Eclipse CDT reports all these lines as errors however and the build seems to have failed, which is wrong.
The was a bug report Bug 539927: Do not mark "Removing unused section" lines as errors and a fix
To fix this bug a change was made 2020-12-02 05322656c6
-CDTGNULinkerErrorParser.regex.LdMode=(.*[/\\\\])?ld(\\.exe)?: (mode .*)
+CDTGNULinkerErrorParser.regex.ldInfo=(.*[/\\\\])?ld(\\.exe)?: ((mode|Removing unused section) .*)
That does however not solve problem entirely, as the output of gcc linker is "removing", not "Removing", i.e. the word "removing" starts with a lower-case "r"
To fix that problem both R and r should be accepted.
