I'm using the CVS version of Boost.Build on WinXP. Consider the
following project:
top/
|
+-- include/
| |
| +-- dir/
| |
| +--header.h
+-- Jamroot
+-- main.cxx
// -- main.cxx
#include
int main() {
return 0;
}
# -- Jamroot
path-constant TOP : . ;
exe app : main.cxx
: <include>$(TOP)/include
;
Modification of header.h does not invoke the app target. I'm not
familiar with bjam at all, but there is one thing I noticed and which
might be relevant. When bjam is run with -d7 the include directory
appears in the bjam's output with leading '/' and 'header.h' itself is
labeled as missing:
set SEARCH = /c:/Temp/bb2/include
set HDRSCAN = #[ t]*include[ ]*(<(.*)>|"(.*)")
set SCANNER = object(c-scanner)@45
set HDRRULE = scanner.hdrrule
set HDRGRIST = object(c-scanner)@45
build file: root = '/c:/Temp/bb2/include' dir = 'dir' base = 'header'
search dir/header.h: /c:/Temp/bb2/include\dir/header.h
build file: dir = '\c:\temp\bb2\include\dir' build file: dir = 'dir'
base = 'header' search dir/header.h: dir/header.h
build file: dir = 'dir' set SEARCH =
set HDRSCAN =
set SCANNER =
set HDRRULE =
set HDRGRIST =
bind -- dir/header.h: dir/header.h
time -- dir/header.h: missing
made stable dir/header.h
made* newer main.cxx
made+ update main.obj
made+ update app.exe
made update all
--
Jarda
