| Detecting include paths and preprocessor symbols [message #1224987] |
Sat, 28 December 2013 10:26 |
 Shaun Pinney
Messages: 1
Registered: December 2013 |
Junior Member |
|
|
I've read the Eclipse help and found that the CDT determines include paths and preprocessor symbols using two techniques:
1. Querying the compiler itself for built-in include paths and predefined macros
2. Parsing the build output for include paths and macros added via command line arguments
http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Fconcepts%2Fcdt_c_scanner_discovery.htm
For 2, the help page indicates it relies on the verbose build output of the build system. So, if a build system redirects compiler output to a logfile instead of stdout, then these command line options would not be seen during the parsing step.
Are there Language Setting Providers that can capture command line parameters when the build system redirects the compiler command line parameters away from stdout? I can envision a ptrace-based method on Linux to capture all child process parameters, but have not found any mention of an CDT provider that does this.
Thanks,
Shaun
|
|
|
Powered by
FUDForum. Page generated in 0.03256 seconds
] 
Search
Help
Register
Login
Home
