Subject: [Boost-build] Issue in <include> relative path calculation when defined in <conditional>.
From: dimak (dvb.kharkov_at_[hidden])
Date: 2012-07-19 05:05:55
I am replicating here the issue definition I posted several days ago at
Boost track tickets, *Ticket #7144
*(https://svn.boost.org/trac/boost/ticket/7144). Please have a look at the
attach "hello2.tar.gz" if you take your time for bug review and its possible
*Description of the bug:*
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.
-- View this message in context: http://boost.2283326.n4.nabble.com/Issue-in-include-relative-path-calculation-when-defined-in-conditional-tp4633265.html Sent from the Boost - Build mailing list archive at Nabble.com.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk