project.jam question

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-02 13:30:36

Further trying to track down our bugs, I am looking at project.jam. In
v. 1.4, before I started mucking with it, I see the following in
project.find-jamfile:

# Normalize the paths of each file found.
#
local jamfile-found = ;
for local jamfile in $(jamfile-glob)
{
local normalized = $(jamfile) ;
if ! [ os.path.is_rooted $(jamfile) ]
{
local root-path =
[ os.path.parent [ os.path.make [ modules.binding [
CALLER_MODULE ] ] ] ] ;
normalized =
[ os.path.native [ os.path.root_relative_path $(jamfile)
$(root-path) ] ] ;
}

Can somebody please explain the logic behind this? It looks completely
flawed to me. What it seems to do is to try to find any Jamfiles
specified with relative paths in a directory which is relative to >>>the
directory containing the module which called find-jamfile<<< !! Usually,
that's just $(BOOST_ROOT)/tools/build/new, since it gets called from
load-jamfile, etc. This looks like another instance of checking in
untested behavior, though I can't be sure.

I'm planning to simply remove this bit of nastiness for the time
being...

-Dave

+---------------------------------------------------------------+
David Abrahams
C++ Booster (http://www.boost.org) O__ ==
Pythonista (http://www.python.org) c/ /'_ ==
resume: http://users.rcn.com/abrahams/resume.html (*) \(*) ==
email: david.abrahams_at_[hidden]
+---------------------------------------------------------------+