custom build-steps.
Tools for custom build steps normally don't belong to a tool chain. We
assume now that the inputs don't need to be rebuilt rather than
provoking a NPE.
The actual fix is similiar to the patch added to the mentioned bug
originally been created by Piotr Aniola. It has been extended with a
test case demonstrating the problem (and the fix).
Change-Id: I5f17248cbe8e84779144bb5f1873c5b9456baa16
Signed-off-by: Sebastian Bauer <mail@sebastianbauer.info>
Reviewed-on: https://git.eclipse.org/r/38206
Tested-by: Hudson CI
Reviewed-by: Elena Laskavaia <elaskavaia.cdt@gmail.com>
values to default values instead of removing the options.
Change-Id: I748206ab90aa07d161a437af0b6fc4e3d3a7161b
Signed-off-by: mazab <mohamed_azab@mentor.com>
Reviewed-on: https://git.eclipse.org/r/27519
Tested-by: Hudson CI
Reviewed-by: Elena Laskavaia <elaskavaia.cdt@gmail.com>
This change introduces three new ProcessRunners that can be used in the
New Project wizard's template.xml files. These will be used by two new
Qt project wizards that I will introduce in a second patch.
The three new rules are:
1) "AddMakeTarget" which creates new Make Targets (in the Make Targets
view) for the new projects.
2) "SetEnvironmentVariable" which sets an environment variable in all of
the new project's build configurations.
3) "ExtraLanguageSettingsProvider" which modifies the new project's
build configurations to include a new ILanguageSettingsProvider.
The first two are straightforward, the third is a bit different.
Instead of creating a new Toolchain or Configuration it modifies the
Configurations that were created for the new project. In this case the
only modification is to add the extra ILanguageSettingsProvider, but it
might be useful to extend this to other customizations as well.
Change-Id: I30710400e9b0dffcbe6e8965ce7ce2078c1c99ca
Signed-off-by: Andrew Eidsness <eclipse@jfront.com>
Reviewed-on: https://git.eclipse.org/r/16817
Reviewed-by: Andrew Gvozdev <angvoz.dev@gmail.com>
IP-Clean: Andrew Gvozdev <angvoz.dev@gmail.com>
Tested-by: Andrew Gvozdev <angvoz.dev@gmail.com>
An implementation of IEnvironmentVariable is returning null for its key
or value. The javadoc on this interface doesn't mention null, which I
guess makes it a valid value.
This patch checks the result before trying to put it into an instance of
java.util.Properties.
Change-Id: Ic04ddd72dfb558ca403b549b64847c3437971407
Signed-off-by: Andrew Eidsness <andrewe@jfront.com>
Reviewed-on: https://git.eclipse.org/r/15820
Reviewed-by: Andrew Gvozdev <angvoz.dev@gmail.com>
IP-Clean: Andrew Gvozdev <angvoz.dev@gmail.com>
Tested-by: Andrew Gvozdev <angvoz.dev@gmail.com>
-isystem
https://bugs.eclipse.org/bugs/show_bug.cgi?id=394959
Simple patch to treat -isystem as -I, so that at least the paths show
up in the configuration:
- added two include parse options (copied/adapted from -I)
- added junit test case (copied/adapted from -I)
Change-Id: Ib3f3764ad75def49f6ec180bfecc0d6f42eabb1d
Signed-off-by: Fabrizio Iannetti <fabrizio.iannetti@intel.com>
Reviewed-on: https://git.eclipse.org/r/15584
Reviewed-by: Andrew Gvozdev <angvoz.dev@gmail.com>
IP-Clean: Andrew Gvozdev <angvoz.dev@gmail.com>
Tested-by: Andrew Gvozdev <angvoz.dev@gmail.com>
