relative paths differ depending on where bjam is invoked

From: Daniel Holth (dholth_at_[hidden])
Date: 2005-04-16 22:38:24

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello. I am a little frustrated with boost.build v1 that comes with
Boost 1.32.0. I wouldn't mind using v2 but I've found it more opaque.

I have a nice project with several subdirectories like so

.
./src
./util

::: a Jamfile in src:

subproject src ;

# Include definitions needed for Python modules
SEARCH on python.jam = $(BOOST_BUILD_PATH) ;
import python ;

lib uses_relative_paths
~ : # sources
~ a.cc
~ b.cc
~ c.cpp
~ : # requirements
~ <threading>multi
~ <include>../include

::: and a Jamfile in .

project-root ;
subinclude ./src ;

:::

When I build my project from ./src/ it works fine, and when I try to
build from . it doesn't work. I suspect the relative paths are
interpreted differently. How are relative paths like this used properly?

Thanks,

Daniel Holth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCYdowVh4W2pVfoMsRAmfQAJwNM8+w5KCdmYUw55YNZ/9Cg4VqhwCgo+hJ
qfvG7E1dOa7A8/dwqgjAcmo=
=vX49
-----END PGP SIGNATURE-----