Add existing type-traits that were implemented for GCC that are relevant to
MSVC. Some are missing but even with those parsing is improved with minimal
effort. For the LLVM codebase, I see it go from 0.46% unresolved names (16,668)
to 0.19% (6,950).
This is combined with another patch that adds temporary macro hacks.
Change-Id: I441dcfa4a986edef78b75c0d6db04b78fdbc97b3
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
While a literal expression itself will never be negative (the negative
sign is parsed as a unary operator), we also use FloatingPointValue to
represent results during value computations which can be negative.
Change-Id: I16227b2d19256066b094ae60476e124b4bcea14d
Add missing ; to test case.
Change-Id: If0224c4fc3580cbe527efe0d3a5739896a000d7e
Signed-off-by: Felix Morgner <fmorgner@hsr.ch>
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Recognize MinGW installations by checking the path of gcc.exe for
substring "ming".
Change-Id: Ibc6d4b03ef715036176e3aea6382dd986e4caae8
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
This new Language Settings Provider allows parsing MSVC (cl.exe) compilation
commands, It is done similarly to the GCC Build Output Parser.
It is not enabled by default but can be enabled when in the context of
building with an external builder.
In general, MSVC support still needs some work but this output parser greatly
facilitates setup for certain types of projects.
Change-Id: I3fb110ecdfbac1cabbc16239ad6667a5e628d443
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
Problem:
========
Common builder invokes the build on all the referenced projects. For the
markers creation, the project on which build is invoked by user is used,
that is incorrect. Once all the referenced projects are built, the
actual project starts building and removes all the markers associated
with it, hence the markers created previously for referenced projects
are removed and now clicking on error/warning in build console of
referenced projects will not open source file because of missing
markers.
Fix:
====
Always set the correct project being built for markers creation using
setCurrentProject(..) API.
Change-Id: Ief051ac664ea964816fdcbe7f2f54bcf43caa212
Signed-off-by: Umair Sair <umair_sair@hotmail.com>
Problem:
========
filterConfigsToBuild(..) always filters the configs that are once added
to set irrespective if it has been built or not. Consider scenario where
there are three project a, b, c and a depends on b & c and b depends on
c. When a is built, filterConfigsToBuild(..) returns configs of b and c.
Then b starts building and filterConfigsToBuild(..) doesn't return
config of c because its already in set. This is wrong and it should
return config of c because it is not yet built and b depends on it.
Fix:
====
If a referenced config by any project/config is not yet built,
filterConfigsToBuild(..) shouldn't filter it.
Change-Id: I5fbe77789f14ce3114200998070a7461069c98ab
Signed-off-by: Umair Sair <umair_sair@hotmail.com>
The version of the plug-in had been correctly bumped already, but
the tags were missing causing API errors
Change-Id: Ief9f7250d3940c1ddd4d44ee19d53dc99f1af8b5
The configuration for baseline replacement needs to be split.
This may be a bug in Tycho, but I cannot tell. It seems to me the
configuration about ignoredPatterns should be read from the
configuration block in the execution block, but it isn't.
Change-Id: I35e3f4007b0afc21d8bd81d5b07f76581879bc76
Also fix version numbers in all bundles who's binary contents have
changed despite no change in the source of the bundle.
Change-Id: Ic67b79aafa801c7ce96c5e52843ad5c881827d84
We had linux-g++-64. But with Ubuntu 18.04, when you install Qt5
you end up with linux-g++. This simply add that and doesn't specify
the architecture so should work for both 32 and 64 bit.
Change-Id: Ia458e212ff53638496a7108f58b212ef96296afd
This script had been copied to the cdt-infra repo a while ago, this
update removes the copy left behind and redirects users to cdt-infra.
Change-Id: Ia4b2d90a9336947e0aad53a0fce6a569416ac379
Adds support for this attribute in the ILaunchTarget attributes and
then convert it to the boolean attribute on the launch config.
Change-Id: Ieefa6892641517ff0fa6a0a04f63a6a8dbc35bf4
Adds ILaunchTargets for GDB Remote for TCP and Serial Port.
Adds a launch config provider that maps default launch configurations
for the gdb remote launch config types.
Alters the launch attributes by merging in the target attributes
over the launch configuration attributes. This is a no-op of the
target is the Null Target (which has no attributes).
Some string externalization that was missed from previous commits.
Carrying on tradition of ramdonly using Gdb or GDB in our class names :)
Change-Id: Ie8483110f594db593e704adda420ce6b14812dea
Without setting dependent plug-ins to minimum version to match the
target platform we are aiming for we can imply (and therefore let install)
CDT into older versions of Eclipse where CDT does not actually work.
This can be exposed in very odd ways, such as IllegalAccessError, when
platform has allowed API changes.
However, rather than update every single bundle in CDT, only the
o.e.cdt.core/ui bundles are being updated as this should achieve the
desired result without every other bundle needing to be touched.
See Bug 536448
Change-Id: I1c8f102a9a750e40970197da3e6cd56d139492bc
I haven't been able to get the automatic publishing working in time
and as Doug has been doing active work in that area I have temporarily
made this change.
Change-Id: I1d4b6776b77a116063b93f5f280dbf45719b7a6e
