Opened 10 years ago
Closed 10 years ago
#7144 closed Bugs (fixed)
Issue in <include> relative path calculation when defined in <conditional>.
| Reported by: | Owned by: | Vladimir Prus | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | build |
| Version: | Boost Development Trunk | Severity: | Problem |
| Keywords: | bjam <include> <conditional> | Cc: |
Description
For <include> feature, "path" attribute is not relative to Jamfile when defined inside <conditional> of requirements. If <include> is defined directly in requirements, everything works proper of course.
The issue is revealed when building project not from the directory where Jamfile with <conditional> is located, but from other directory (so that relative path should be calculated).
Attached reworked "hello" example from repository with "child_dir" subpart which tries to include "folder_to_include" directory.
Attachments (1)
Change History (2)
by , 10 years ago
| Attachment: | hello2.tar.gz added |
|---|
comment:1 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.

Fixed on the trunk in revision [79665].