Opened 20 years ago
Last modified 19 years ago
#4 new enhancement
Features relevance — at Version 3
| Reported by: | ghost | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | M13 |
| Component: | component1 | Version: | |
| Keywords: | Cc: |
Description (last modified by )
At the moment, all properties are assumed to be relevant for target, and are encoded for path. For example, dvi files produced by tex might be placed in gcc/debug. Need to check which properties are really relevant for target. They include:
- properties that affect flags for the action
- properties that affect generators selection
- composite properties for which some part of expansion is relevant
The new functionality should be added to 'toolset' module and 'virtual-target.action' class, since the latter determines the path for targets.
Change History (3)
comment:1 by , 20 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 20 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 20 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | → M12 |
Note:
See TracTickets
for help on using tickets.
