Bug 391476 - [Scanner Discovery] @ parameter should be used
Summary: [Scanner Discovery] @ parameter should be used
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: 8.1.0   Edit
Hardware: PC Windows XP
: P3 enhancement with 4 votes (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-09 15:41 EDT by Gerald Lutter CLA
Modified: 2020-09-04 15:18 EDT (History)
1 user (show)

See Also:


Attachments
minimum example describing the enhancement request (535 bytes, application/x-gzip)
2012-10-09 15:41 EDT, Gerald Lutter CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerald Lutter CLA 2012-10-09 15:41:26 EDT
Created attachment 222082 [details]
minimum example describing the enhancement request

Our build environment makes heavy use of the @ parameter (see gcc manual). The main aspect of this parameter is to shorten the parameter list while calling the compiler (some shells or the command interpreter do not like very long parameter lists). The @ parameter is followed by a file which holds all the necessary build parameters. Would it be possible to include support for this parameter, so that the scanner uses not only the compiler call but also the contents of the file?

For more information take a look at the given minimum example. You have to create a new Project, set the builderpath to the source directory and only include the source directory into the project (via folder link). The scanner discovery now does not discover the options from options.txt. If you change the call inside the Makefile and add the options -I and -D from the options.txt to the build command, all works as expected.