Opened 20 years ago
Closed 19 years ago
#72 closed defect (fixed)
<conditional> in target's usage requirements is not handled correctly
| Reported by: | Owned by: | somebody | |
|---|---|---|---|
| Priority: | major | Milestone: | M12 |
| Component: | component1 | Version: | |
| Keywords: | Cc: |
Description
It seems that the <conditional> feature is handled differently when placed to target's requirements and target's usage requirements.
lib a : a.cpp : : : <conditional>@platform-include-dir ;
exe b : b.cpp a ;
When the target 'b' is being built the usage requirements of target 'a' are not applied. Actually it looks like that the platform-include-dir rule is not invoked at all.
Change History (2)
comment:1 by , 19 years ago
| Milestone: | → M12 |
|---|
comment:2 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
