|
| Re: Custom CDT build parser for auto discovery [message #1733102 is a reply to message #1732542] |
Tue, 24 May 2016 08:10   |
Eclipse User |
|
|
|
Do you mean that you have that string exactly as you wrote in the Compiler command pattern, including all the quotation marks? If you only use the armcc.exe, then why you need the gcc/g++ parts?
An example, probably not what you want but maybe adds a little help:
In Linux, I have a make output with compiler /path/to/my_little-compiler++, and I use the (my_little-compiler\+\+) setting. It works, though the discovered settings are added to the individual CPP source files rather than to the project toplevel settings. In the project explorer, little wrench "sub-icons" denote the CPP files that have discovered settings after a successful build (looks like the header files are not handled by this feature).
I don't have quotation marks in my make output, so I can't help you in that, but probably you could try out the following settings:
(armcc\.exe)
(armcc\.exe)"
(armcc\.exe")
I don't know if the parentheses are necessary (in a regular expression they usually mean a capture group, and the matched string may be used by CDT for something internally, so I kept them).
|
|
|
|
| Re: Custom CDT build parser for auto discovery [message #1752058 is a reply to message #1733184] |
Wed, 18 January 2017 06:58 |
| Eclipse User |
|
|
|
David Choen wrote on Wed, 25 May 2016 04:06
The CDT parsed the compiler output, it simply placed the result in each file individually, and not in the whole project.
I found today that this behaviour can be changed (at least in Neon).
Go to Preferences - C/C++ - Build - Settings - Discovery tab.
Then select the "CDT CGC Build Output Parser", then below select "Project" in the "Container to keep discovered entries".
regards,
|
|
|
Powered by
FUDForum. Page generated in 0.05016 seconds
Home
