From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-10-24 02:19:39
Johan Nilsson wrote:
> I originally posted to the Jamming mailinglist, but got no response. I
> figured the behaviour of bjam might still be the same with respect to
> OpenVMS paths.
This might be true, but as far as I know, there's nobody who uses bjam
on VMS, so we're in no beter position to fix things there than you.
> it seems to be impossible to get both jam (2.4) and the DEC C++ 6.5 compiler
> (cxx) to locate the header files correctly when using relative includes
> under OpenVMS, e.g.:
> --- snip from whoever.cpp ---
> #include <Whatever/Whoever.h>
> To get cxx to find the headers, I created a logical root for the include
> root, e.g.:
> def/job/trans=conc INC_ROOT "DISK$USER:[MYDIR]"
> Then I can use this in a unix-style path to cxx, e.g.:
> cxx /INCLUDE_DIR=("/inc_root") => jam "-sHDRS=/inc_root"
> And then I can merrily compile the stuff - but it seems like jam can't to
> locate the header; if I change anything in
> "DISK$USER:[MYDIR.WHATEVER]WHOEVER.H" it doesn't result in a recompile of
> whoever.cpp !
bjam has a "-d+12" option which show the dependency graph. Maybe you can
use it to see what's going on. Be warned that you've have to rename
binary to "jam", if you want to use in in "compatibility mode".
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