Bug 373401 - Tools options are not emitted to command-line if the option value cannot be resolved
Summary: Tools options are not emitted to command-line if the option value cannot be r...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build-managed (show other bugs)
Version: 8.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-06 12:21 EST by Alex Freidin CLA
Modified: 2020-09-04 15:17 EDT (History)
1 user (show)

See Also:

Attachments
Patch (2.38 KB, patch)
2012-03-06 12:30 EST, Alex Freidin CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Freidin CLA 2012-03-06 12:21:08 EST 
Build Identifier: 20110519-1049

The options in the Project Properties may have values that use built-in variables. For example, linker Libraries settings may include "${workspace_loc:/my_project_here}". In case, when the variable cannot be resolved, like in the case when the referred project is removed from the workspace, the command-line is generated without -L option. The resulting error message may be misleading or there could be no error message, depending which tool option is effected.
The MBS should not ignore unresolved values and should emit the relevant tool options to cmdline. Such that the user can immediately locate the problem.


Reproducible: Always
Comment 1 Alex Freidin CLA 2012-03-06 12:30:46 EST 
Created attachment 212150 [details]
Patch

A patch my colleague created to emit the tool flag without a value if the value cannot be resolved. This causes an error message from the tool during the build, pointing to the missing value.
Comment 2 Alex Freidin CLA 2012-03-06 12:31:58 EST 
The patch is against CDT 7.0.1.