Since resolved bindings are cached, we can get stuck with a bad binding
resolved during an incorrecy branch of ambiguity resolution.
Change-Id: I59bcb9f6f2b756892a56b135e8d6a1f026180728
Unify launching for projects that use the new Core Build system.
Starts with CMake projects. We'll do Qt projects next.
Change-Id: I14af8e99decd54cc6548095b3ad3e054c550aea2
DisplayHelper is used to run the event loop until a condition is met
or until a maximum timeout is reached. This timeout varies between
hundreds of milliseconds to a few seconds. When the tests are running
on a machine that is known to be quite under load (Hudson), the
timeouts in the milliseconds are too optimistics as there can be a
lot of other things running at the same time on the machine.
This change adds a multipler (default 1) that can be controlled from
the maven command line, for example:
-Dorg.eclipse.cdt.ui.testplugin.DisplayHelper.TIMEOUT_MULTIPLIER=5
Change-Id: I9c1517ac2641768e8ae0f4508bf9a008931ef805
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
For ESP8266, I want to auto discover the toolchains and friends
installed into Eclipse. I also want to handle toolchain files
manually added by the user. Adding providers and listeners.
Adds prefix to gcc commands. Makes CMake config provider for Local
only. ESP8266 has it's own launch config. Add build output to the
build config model. And fix up output folders.
Change-Id: I682c3d08898e5ca275d07f8bb63c6ec1c7605a81
Right now launch configuration delegates need to know too much about
the specific build system for a project (cmake versus qt, for example)
Start decoupling this and test out the theory with CMake.
Change-Id: I8a362f16cddca77b37a5ab5920ee19318035d478
Use launch target os and cpu arch properties to pick toolchains and
toolchain files. UI to add toolchain files. And build support.
Also some clean up of Qt as I found bugs.
Change-Id: Icd1da43460b5954eea15e95ed8ec27850fc4e54e
Reads the compile_commands.json file and feeds the commands into
the processLine method of the build config which creates the scanner
info. The scanner info is cached in memory and stored in the
metadata directory.
Change-Id: I8b04e661dfe767904d1c10119c07167fee8cd7e4
* Adapted the parser to cope with decltype(auto)
* Extended IASTSimpleDeclSpecifier to have a kind for decltype(auto)
* Added tests (syntactic recognition and type deduction for variables)
* Modified DeclSpecWriter to cope with the decltype(auto) kind simple
decl specifier
Change-Id: Ib1ded823027d124cef35e9d6355c0f48f57709a0
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Use the same as JDT to be more consistent and also to not conflict
with Mission Control.
Change-Id: Ibe1ed3c43e5c7de2ab5bb0a508bf93e22bbdb7ca
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Running maven with mvn clean install -Dindexer.timeout=123 doesn't
have any effect since tests to not inherit the VM args from Maven.
But we can pass those VM args manually in the pom.xml
Change-Id: I17b4aecdc422e3035e583b6d057c8487e7e41650
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
