- Jan 08, 2014
-
-
Robert Loehning authored
Change-Id: Ib5423fdd064e4546f848c0b640b0ed0514c26d3a Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@digia.com> Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- Aug 20, 2013
-
-
Tobias Hunger authored
Change-Id: Iebf4302bb5e3f893dc573e504efc214861d80848 Reviewed-by:
Daniel Teske <daniel.teske@digia.com>
-
- Aug 09, 2013
-
-
Tobias Hunger authored
Change-Id: I42c195004a9eca9f03cf34bd274f473ed87c580e Reviewed-by:
André Hartmann <aha_1980@gmx.de> Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com>
-
- Aug 08, 2013
-
-
Andre Hartmann authored
Allow setting the following items from outside: * capture regular expression, * file name, line number and message capture position and * whether to parse stdout, stderr or both The parser functions can be unit-tested by running (Debug build of Qt Creator needed): qtcreator -test ProjectExplorer,testCustomOutputParsers The data is passed to the custom parser in CustomToolChain::outputParser(). The parser information is stored in toolchains.xml together with the custom toolchain. A configuration widget is provided to set up and test the regular expression against a sample error message. Change-Id: I6191df3c44432943e0aeb16c48d8e79d35845d2e Reviewed-by:
Orgad Shaneh <orgads@gmail.com> Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com>
-