From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-07-11 06:13:02
On Saturday 07 July 2007 00:41, Ray Lambert wrote:
> (root) has an empty Jamroot and 'common' and 'tests' each have a (very
> simple) Jamfile. 'common' builds a static lib and the targets in 'tests'
> try to link to it.
> The Jamfile in 'common' looks like this:
> lib common : [ glob *.cpp ] : <include>. <include>.. <link>static ;
> The Jamfile in 'tests' looks like this:
> exe xmltest : xmltest.cpp ..//common [ lib expat ] : <include>../.. ;
This "..//common", strictly speaking, refers to entire directory 'common', not
the target 'common' in directory common. You might want to try
but I can't see why that can matter.
> 'common' builds successfully. When I try to build the target 'xmltest' in
> 'tests' I get the following error:
> error: Unable to find file or target named
> error: '..//common'
> error: referred from project at
> error: '.'
> Again, this all works perfectly on Linux. I've seached quite a bit but I
> cannot find anything relating to bugs or alternative behaviour of the
> '..//common' syntax on windows.
Are you sure there's no upper-case-vs-lower-case problem going on? Again,
bjam is supposed to ignore case on windows, completely.
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