3 messages in com.perforce.jammingProblems with multilevel subdirectori...
FromSent OnAttachments
Jari...@picker.fi Jari.Salminen@picker.fi01 Nov 1996 05:52 
JimJ...@caldera.silverplatter.com01 Nov 1996 08:04 
Dian...@whistle.com01 Nov 1996 10:56 
Subject:Problems with multilevel subdirectories in a project ...
From:Jari...@picker.fi Jari.Salminen@picker.fi (Jari@picker.fi Jari.Salminen@picker.fi)
Date:11/01/1996 05:52:21 AM
List:com.perforce.jamming

Hi,

I'm trying to build a project which contains several nested subdirectories. I would like to locate my object and binary file in a different drive, but keep the same directory structure as the source directory tree. This would make possible to keep sources on read-only media (like CD-ROM) and have different platform binaries compiled into local disks.

To keep the jamfiles in module directories simple, I thought I could use Jamrules and define the root directory for the binaries there. Specially when I noticed that SubDir rule already defines LOCATE_TARGET by using $(ALL_LOCATE_TARGET) and $(SUBDIR) variables. So defining ALL_LOCATE_TARGET in Jamrules should do the job ...

Didn't work. First problem is the bug with include operation (described in jam.ps), which makes the Jamrules to be included AFTER setting that LOCATE_TARGET variable. So the first modules will not use the ALL_LOCATE_TARGET variable from Jamrules. Besides, with the nested directories the subdirectory name is lost for some reason.

Basically I could use LOCATE_TARGET setting in each Jamfile, but I would like to keep those Jamfiles as simple as possible (actually I would also like to get rid of those directory names in SubDir rule, but that's another story...)

Does anyone have examples of such multilevel subdirectory project? How about any workaround for that include bug?

Regards,

Jari Salminen