Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320550 - Improved usage of list types of build variables
Summary: Improved usage of list types of build variables
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 7.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 332061
  Show dependency tree
 
Reported: 2010-07-21 16:14 EDT by Sebastian Bauer CLA
Modified: 2020-09-04 15:22 EDT (History)
0 users

See Also:

Attachments
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 Sebastian Bauer CLA 2010-07-21 16:14:51 EDT 
Build Identifier: 

Currently, list types of build variables (e.g., string list, directory list, etc.) are replaced as they would be written as a single string. It would be nice, if one could use these variables in the "Path and Symbols" page of the project properties as placeholders for defines, include paths, and libs. For instance, if a build variable MYDEF contains "DEF1", "DEF2", and this variable is added in the symbols page, I would expect that symbols "DEF1" and "DEF2" are added and not that a single symbol "DEF1 DEF2" is added, which doesn't make sense.

Additionally, it would be nice if one could generally specify how the variables are expanded when they are used, e.g., by using an argument to the build variables, e.g., ${MYDEF:-D} would expand it to -D"DEF1" -D"DEF2".

Reproducible: Always