This avoids expontential complexity when type template arguments inside
an ambiguous name specifier themselves contain ambiguous name specifiers.
The patch also enhances TemplateIdStrategy to allow marking and backing
up to a branch point, and uses this ability in templateArgument().
Change-Id: Ia03e9cd0bc026b02b85edc05ed327cce883d6a59
- fix provided by Christian Walther
- fix createTreeForEntries() method to use addTreeListener() instead
of addPaintListener() to handle resizing
- in TreeListener, define treeExpanded method which uses pack method
for entries column
Change-Id: I28db2059d3e0561ce9e5e52f569409de9aff9a6d
- add new optional build property to run all Autotool
commands in Container
- for Autotool nature projects only, add a checkbox to the
ContainerPropertyTab to turn this new option on/off
- change the AbstractAutotoolsHandler class to look at the
optional build properties for the project to determine if
the fallback CommandLauncher used to run commands should come from
the CommandLauncherManager to run in Container or to a
local CommandLauncher
- change AutotoolsNewMakeGenerator the same way
- add new messages as needed (add a tooltip to warn user that
choosing new option may cause inconsistencies for files shared
among configurations)
Change-Id: Id828ec3015f32f320d2247bd0577944164c71df8
Not sure what changed but the launcher for these projects is now
returning null for an environment. Added a null check.
Change-Id: I05c94bb77f951f417577d0c2a3e3b4b6b996214b
(cherry picked from commit be9c1b8338)
The setting build.proj.ref.configs.enabled=true ensures CDT projects are
not rebuilt if non-related projects are changed. This setting cannot be
changed with product or command line customization, hindering products
which require this behavior.
The reason for this is that ACBuilder, which is asked for the value of
the preference, communicates with the instance scope of preferences.
Product and command line customization, however, are on default scope
level.
With this change, ACBuilder will also ask the default scope when
retrieving the value of the preference.
Change-Id: I09e895ea2a05b677e36fac9eb28f24f1f3bc2877
Signed-off-by: Simeon Andreev <simeon.danailov.andreev@gmail.com>
- modify ContainerTab to reset the error message when Docker
Connections/Image changes cause a listener notification and
then look to see if no connections or no images errors exist
- modify ContainerTab to reset the error message if the Docker
Connection selected gets changed
- bump org.eclipse.cdt.docker.launcher version to 1.1.1
Change-Id: Iad5051750a5dd53a0eb458d73570fffd9e3867c4
- bump up org.eclipse.cdt.remote.core so that autotools.core
can refer to the latest version in its dependencies
Change-Id: I4ec198d7c5d367a4a479a1dd39839f3c2d8c4a96
The special binding type CPPLambdaExpressionParameter is removed.
Instead, a lambda expression parameters's are represented as
regular CPPParameters owned by the closure type's generated
function call operator.
Change-Id: I4afeac90c2595a1f84dfa59f057d0494b64d079c
The pseudo-destructor is represented as a CPPImplicitFunction, computed
lazily and stored by CPPBasicType.
This commit also adds support for alias templates to
CPPTemplates.getTemplateName().
Change-Id: I6774556b2493cb68d32c3007d6ce48c7805595f4
The implementation strategy is as follows:
- Implement an option to find potential matches during an AST
definition search.
- Store names that resolve to ProblemBindings in the index,
as references for the candidate bindings, annotated as being
potential matches.
- Add an option to Index.findNames() to include potential matches.
- Use the added options for the index and AST searches in
OpenDeclarationsJob, prioritizing them accordingly (e.g. exact index
matches take precedence over potential AST matches, but if there
are no exact matches, potential matches from the AST and the index
are combined).
Change-Id: I19f5c58820eb3ec79a31652d69fd5b86acaba115
Previously, we would only try the first base class whose primary
template matched that of the parameter type.
Change-Id: I0511e6a1ba1c7197887ff23bc37b70a2a820eb87
In the new toolchain wizard, the select button wasn't hooked up.
So I turned it off. Also, we had no build settings tab on the serial
launch.
Change-Id: I811f579334889085f49d298878589109c5e4a228
Move Toolchains directly under C/C++ and rename to Core
Build Toolchains. Add a label describing what the toolchains
are for in hope of avoiding confusion with managed build.
Also move Qt into C/C++.
Change-Id: Ia1d76087c65b26562d1001243ea355c7ac32365e
When projects were deleted, sometimes the descriptors
would not. We were creating our own core build launch
descs which didn't have an equals method causing duplicate
entries to be created. Arduino uses launch bar's project
launch descs. This change does the same for core build.
Change-Id: I2a6f60e92aaa20892d6c1d8331ded903b226984f
- Add volatile variant for __atomic_clear and __atomic_test_and_set
- Add missing parameters for __builtin_fmax and related
Change-Id: Ib31d1a410b8749f5672d70d7d02ca1dff962c38b
Signed-off-by: Martin Oberhuber <mober.at+eclipse@gmail.com>
The evaluated type of 'decltype(auto)' in combination with const and/or
volatile will be a ProblemType since this is not valid code. The patch
also contains a checker to give the user a visual feedback.
Note: A proposed quick-fix has been removed after a short discussion.
Change-Id: I8760ed0ac28e28529ab30516accac9c0413c87d9
Signed-off-by: Hansruedi Patzen <hansruedi.patzen@hsr.ch>
We weren't passing in the base settings to the compiler for
discovery. Also had a bug in the defines regex that mishandled
values with spaces in them.
Change-Id: I48183bfc3f61056324da009e58327cdcfed8754a
When deleting projects then creating them with the same name
the scanner info didn't get cleared up and was reused. We
were deleting these files from the wrong path.
Change-Id: Ieda174b7cfc9690ab51be65e674bda321cb3bc10
We were missing the dialog to ask if you wanted to continue
after build errors in a project. We were missing the method
that provided the list of projects to do that check.
Also while testing that noticed the handling of the build
and clean command UI was broken with make projects.
Change-Id: I698e151672a114bb22c815f49d362b6413b9c315
If we're building for non-local targets we need a toolchain
file. Print out an error message when it's missing at build
time. Recover when one is added.
Also a rider that makes sure the Makefile projects are
marked experimental.
Change-Id: I0c295dc5b3d71a04c60c3385ce790553f172859d
The call to CDTBuildAction's super updateSelection method
clears out some state. Make sure we call it even though we
want to always build CDT projects.
Change-Id: Ie5dc1f583bbcc04d85b7254a4b7c18ee50f02997
If you select a non-CDT project then select a CDT one, the
Build Project menu item wouldn't enable. If you select the
CDT project again, it does. Big question is why isn't it enabled
when selected.
This fix just enables it all the time. Much easier for users
to understand.
Change-Id: I674740f2c6998686cade1f910a269a4e9d935d39
Makefile projects depend on build output parsing to pick up
compiler options to use while indexing. Sometimes, that just
doesn't work. As a back up we've always allowed users to manually
add them to the project. Long ago when we had pure make projects
we had UI for this. This change hooks that old UI up. It was a
time before build configs so they get applied to them all but it
serves it's role as a backup when users run into problems.
Unmarked everything I use here from deprecated until we decide
how to replace these with Core build config aware settings.
Change-Id: I6fc4d48e5315df3c60c7591b026ae0a53a1f505e
Removed the empty debug.core.tests project. Also removed the
utils-feature and remote-feature projects since these shouldn't
be features.
Change-Id: Ib5d297c626de5328e3421a1fc9346330d9907750
Also set BUILD_MODE to the launch mode so the makefile can do
different things based on the mode. Change template to add -g
option for debug.
Also fix a deadlock I detected due to side affect build folder
creation.
Change-Id: Ic7b13ba3238e6ef201cccb1b2bfc8dcc6956ea3a
