Bugzilla – Full Text Bug Listing
| Summary: | Improved usage of list types of build variables | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Sebastian Bauer <mail> |
| Component: | cdt-core | Assignee: | Project Inbox <cdt-core-inbox> |
| Status: | NEW --- | QA Contact: | Jonah Graham <jonah> |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 332061 | ||
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