paths and subprojects: Anyone? Beuhler?

From: Paul Schmidt (prs_at_[hidden])
Date: 2003-07-30 08:08:34

--- In jamboost_at_[hidden], "Paul Schmidt" <prs_at_k...> wrote:
> I'm having problems building a subproject. My directory structure is:
> 
> $(Top) -> jamtest\
> jamfile
> ee\
> jamfile
> init\
> jamfile
> init.c
> hello\
> jamfile
> hello.c
> iop\ <stuff below here not important>
> 
> And I'm running bjam in the ee\hello directory:
> 
> bjam -s"TOOLS=snps2" -s"BUILD=debug"
> 
> I see these messages:
> 
> don't know how to make <ee!init>init.c
> don't know how to make <ee!init\init\snps2\debug\instruction-set-ee>init
> ...found 34 targets...
> ...updating 14 targets...
> ...can't find 2 targets...
> ...can't make 3 targets...
> MkDir1 ee
> MkDir1 ee\init
> MkDir1 ee\init\bin
> MkDir1 ee\init\bin\init
> MkDir1 ee\init\bin\init\snps2
> MkDir1 ee\init\bin\init\snps2\debug
> MkDir1 ee\init\bin\init\snps2\debug\instruction-set-ee
> ...skipped <ee!init\init\snps2\debug\instruction-set-ee>init.o for
> lack of <ee!init>init.c...
> ...skipped <ee!init\init\snps2\debug\instruction-set-ee>init.a for
> lack of <ee!init\init\snps2\debug\instruction-set-ee>init.o...
> MkDir1 bin
> MkDir1 bin\hello
> MkDir1 bin\hello\snps2
> MkDir1 bin\hello\snps2\debug
> MkDir1 bin\hello\snps2\debug\instruction-set-ee
> snps2-Cc-action bin\hello\snps2\debug\instruction-set-ee\hello.o
> As bin\hello\snps2\debug\instruction-set-ee\crt0.o
> ...skipped <ee!hello\hello\snps2\debug\instruction-set-ee>hello for
> lack of <ee!init\init\snps2\debug\instruction-set-ee>init...
> ...skipped 3 targets...
> ...updated 14 targets...
> 
> 
> Init.c is in fact in the right place, so why shouldn't bjam find it? 
> 
> 
> Also, the directory structures that got created are:
> 
> $(TOP)\ee\hello\ee\init\bin\init\snps2\debug\instruction-set-ee
> 
> $(TOP)\ee\hello\bin\hello\snps2\debug\instruction-set-ee
> 
> The second one is fine, but what's up with the first line? Shouldn't
> the binary for init.a have been placed in a structure under
> $(Top)\ee\init? 
> 
> The build works when bjam is started in the $(Top) directory