[Boost-bugs] [Boost C++ Libraries] #7163: Issue in glob rule when defined in <conditional>.

Subject: [Boost-bugs] [Boost C++ Libraries] #7163: Issue in glob rule when defined in <conditional>.
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-07-23 20:41:25


#7163: Issue in glob rule when defined in <conditional>.
--------------------------------------------------------+-------------------
 Reporter: Dmitriy Kinoshenko <dvb.kharkov@…> | Owner: vladimir_prus
     Type: Bugs | Status: new
Milestone: To Be Determined | Component: build
  Version: Boost Development Trunk | Severity: Problem
 Keywords: bjam glob <conditional> |
--------------------------------------------------------+-------------------
 Hi,

 When we use glob rule inside conditional in dependency target, it makes
 "globbing" not inside directory of dependency project, but inside
 dependent one. To reproduce, take example/libraries from boost build
 repository, amend util/foo/jamfile to introduce <conditional>:

>>>
 rule print-my-sources ( properties * )
 {
     ECHO My sources: ;
     ECHO [ glob *.cpp ] ;
 }

 project
     : usage-requirements <include>include ;

 lib bar : bar.cpp : <conditional>@print-my-sources ;
 <<<

 Finally, build from jamroot.jam level and see the output:
 My sources:
 app.cpp
 My sources:
 app.cpp

 We expected to see "bar.cpp", while it seems that context was not switched
 from dependent "app" to dependency "util/foo", and thus we got "app.cpp".

 Attached reworked example/libraries.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/7163>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:10 UTC