| We currently use MMS (and CMS for source code control) on VMS, which means | that the natural way to build software is to have multiple MMS ( i.e. make) | files in a single directory, which are then invoked from a main controlling | MMS file. The lower level MMS files can also be used independently. We also | use a separate RULES file (equivalent to JAMBASE), because the standard MMS | rules are not sufficient.

I don't quite understand this -- you say that all descrip.mms files live in the same directory for the whole tree?

| [ deletia ] | | I have considered "inverting" the include of Jamfile by Jambase by setting | up several Jambase files which consist of an include for the real jambase | rules followed by the code that would normally go in Jamfile, but this seems | rather messy, and would not work with a pre-compiled Jambase. I suppose what | I would like to do is to be able to do something like (invented syntax): | JAM [-JAMBASE=myJambase] -JAMFILE=myJamfile

You should note that there is syntax for setting variables on the command line, like this:

jam -sJAMBSE=myJambase -sJAMFILE=myJamfile

Now how those variables are used depends on the (now) compiled-in Jambase. But if you are looking for a custom solution, then having your own custom compiled-in Jambase is not outrageous. It can itself then include the original, external Jambase.

Christopher

----- Christopher Seiwald Perforce Software www.perforce.com seiw...@perforce.com f-f-f-fast SCM 1-510-865-8720