- fix GCCToolChain and ContainerGCCToolChain to not blindly
take the first token in the command string when processing
scannerinfo; if it is "ccache", take the second token instead
Change-Id: I4b2b7dfaccae6f3ec968bbe4217c57994ad71963
- fix ContainerTargetTypeProvider changeEvent() to start a Job and
return immediately so it will not cause a DockerConnection
to be held in multi-threading
- move the DockerConnectionManager addConnectionListener call
to end of init() method so the fetching of images won't cause
a notification event to occur
- at end of init(), call CBuildConfigurationManager.recheckConfigs()
to make sure any disabled configuration due to a missing
IDockerConnection is now put in the configs master list and
removed from the noconfigs list
- make similar changes to ContainerGCCToolChainProvider
Change-Id: Idc120d613b99ec365522f5e7bf5da82d1b362425
To build and run only lsp4e-cpp tests do:
mvn verify -P skip-tests-except-lsp4e-cpp
Also-by: Jonah Graham <jonah@kichwacoders.com>
Change-Id: Id6f3cd8ae291283c0cad7f1e63fbcdce683f4d2d
Otherwise we can get clashes if two anonymous types happen to be
at the same offset in files with the same name but different paths.
Change-Id: Ia269a7c6fa1dc7e37d23d9333b245143d7c33e5d
This package is marked for removal in Java 10 and in fact, is not found at
run time. Instead, use the javax.xml.bind plugin from Orbit.
javax.xml.stream is also needed by javax.xml.bind.
Change-Id: Ida10746267c814a8a11f2db7181dcb9e8ceaad44
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
We weren't dealting with relative include paths returned from
the call to gcc -E properly. Resolves them against the build
directory before checking if their a directory. Results in them
added.
Tested with ESP-IDF's feature/cmake branch.
Change-Id: I1e2583e03cce6380ee4382146b177978c9c81806
(cherry picked from commit 3b44424539)
Fixed with the patch for 533552, only the CodeFormatter needed fixing.
Change-Id: I258617d01b091764ad9776921e773e208002c989
Signed-off-by: Hansruedi Patzen <hansruedi.patzen@hsr.ch>
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Fix and test.
Also fixes formatting errors with DefaultStatements.
Change-Id: Idac4a7105d7ae86db40755bd27cef60e197de664
Signed-off-by: Hansruedi Patzen <hansruedi.patzen@hsr.ch>
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Fix and tests.
Also fixes bug 535265, since the Codan Quickfix tests fail otherwise.
Change-Id: Id31e40907b7ebdeee4a67c014c3a1b1cd37579ad
Signed-off-by: Hansruedi Patzen <hansruedi.patzen@hsr.ch>
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Ensure that the remote connection has been opened before showing
RemoteResourceBrowser dialog so that the dialog's layout would not
depend on the state of the connection.
Change-Id: Iec70c243b75723de418e55a1f07cd8e9804400b6
Signed-off-by: Chin Huat Ang <chin.huat.ang@intel.com>
All sorts of views, variables, memory, etc can do a DSF operation
that causes an error. But for some reason only the disassembly
view generally displays this error to the user in a pop-up.
This change converts the pop-up (which says things like "Target not
available" or "Failed to execute MI command:
-var-create - * symbol_that_user_typed_that_doesnt_exist
Error message from debugger back end:
-var-create: unable to create variable object") to just log the
error instead.
Errors are dealt with in the UI already (example, bad location in
text box in toolbar gets an exclamation next to it). However, I don't
know if there are some errors that really do need to be displayed
to the user with a pop-up.
Change-Id: I27b398c34e558db98d34cef773a2689fa9222149
AttributeWriter.writeGCCAttributeSpecifier()
* Added test to reproduce initial issue.
Change-Id: I72e60fb2244b7d40492bfcdeaa58a8707c39e277
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Includes reverting 851295e821:
[releng] work around Tycho issues of obtaining *.jre.javase [10.0.0]
Change-Id: I1d49b519ba111e48545ef37c991859dfa68960cd
The original implementation used plain-text string manipulation of the
IDocument. This changeset changes the implementation to make use of the
ASTRewrite infrastructure, which automatically honors the const
placement setting.
Change-Id: Ib5ae9381b93ca8ab4d1ad3e16b1c3c8b1ec62d78
Signed-off-by: Felix Morgner <fmorgner@hsr.ch>
Fix and test
Change-Id: I14088e69aed829940fb1e9f5197dedf18d9bb7a5
Signed-off-by: Hansruedi Patzen <hansruedi.patzen@hsr.ch>
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
- Launch bar is usually expecting a LaunchConfigurationTargeted
Delegate which calculates the binary but Container build
uses the ContainerLaunchConfigurationDelegate which expects
the program name, working dir, connection, and image id
set up as ILaunchConfiguration attributes
- modify ContainerLaunchConfigurationDelegate to add
finalLaunchCheck method which can verify if the launch
config attributes are set up and if not, set them from
the build config (since this is post-build)
- fix getImageName() in CoreBuildContainerLaunchConfigProvider
to use toolchain attributes
Change-Id: Iad6cc26928c33e964650b99844e065df8653858f
Fix and test
Change-Id: I785ecfd0715f1fa8ff86b87bd01d16ac6d5d5da2
Signed-off-by: Hansruedi Patzen <hansruedi.patzen@hsr.ch>
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
