Opened 18 years ago

Closed 16 years ago

#13 closed defect (fixed)

Dependency property inheritance

Reported by: ghost Owned by: somebody
Priority: major Milestone: M13
Component: component1 Version: 2.0
Keywords: Cc:

Description

Given top-level Jamfile with: 

lib a ;
project
  : requirements <library>a
  ;

it's not possible to build any child project, because they will have <library>a as inherited property, but won't have the 'a' target.

Change History (4)

comment:1 by ghost, 17 years ago

Milestone: → M13

comment:2 by jurko.gospodnetic@…, 16 years ago

Resolution: → fixed
Status: new → closed

Closed by a patch from Steven Watanabe committed as changeset ​http://svn.boost.org/trac/boost/changeset/47536

comment:3 by jurko.gospodnetic@…, 16 years ago

Resolution: fixed
Status: closed → reopened
Version: → 2.0

Reopened again as the original patch got reverted in changeset ​http://svn.boost.org/trac/boost/changeset/47571 due to not working correctly with dependency features using absolute paths to targets or those using targets from the current project.

Test case inherited_dependencies.py attached in the original patch will be left in the trunk.

comment:4 by jurko.gospodnetic@…, 16 years ago

Resolution: → fixed
Status: reopened → closed

Ticket closed by the following patch series:

  • Changeset link: ​http://svn.boost.org/trac/boost/changeset/48318 
    Updated Boost Build's project id handling so that if a project has an
id attribute, this id will be automatically registered and usable from
that same project just the same as if the id had been specified
directly using the 'id' project rule parameter.
  • Changeset link: ​http://svn.boost.org/trac/boost/changeset/48319 
    Added binding targets specified using an inherited dependency
property to their corresponding project so they refer to the correct
target independently of the project context in which they get used.
Note: See TracTickets for help on using tickets.