From: kir (Kirk Rader)

Subject: Re: Defsystem long form module specifications

Date: 1994-12-8 17:19

   Date: Thu, 8 Dec 1994 11:06:23 -0800
   From: Gary Hall <cs.sfu.ca at hall>


   Greetings,
     I am attempting to use the long form module specifications in Defsystem
   to  override system default values and not having any success.  I would
   appreciate some assistance from someone who knows the secret.

   Specifically, I am trying to define a system and to override the 
   default-module-class for the system (lisp-module) in the specification
   of one of its modules. (I want it to be of type c-module.) In addition, 
   I want to override the default-pathname for that same module.

   If anyone has an example of a successful use of long form module specifications
   within a defsystem call to do this or something similar, I would very much
   appreciate seeing it.

   Gary Hall                  | Voice (604) 291-3208 | INTERNET: <cs.sfu.ca at hall>
   Centre for Systems Science | Fax   (604) 291-4424 | 
   Simon Fraser University    | 			  
   Burnaby, B.C.  V5A 1S6     |       


The following is taken from one of the defsystem files used in the
application on which I work.  The module-class, ark-so-module, is a
home-grown extension to the default module classes supplied with
Allegro CL which supports non-standard keywords like :source-files,
but you should get the idea.


(defsystem :IMAGE-C-FILES
    (:default-pathname "/usr/local/delrey/src/image/")
  (:serial
   (:module image-c-files "arkimage-c-functions"
	    (:module-class ark-so-module)
	    (:product-pathname "/usr/local/delrey/obj/image/")
	    (:source-files ("arkimage-c-functions")))))