home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!crdgw1!cook!psinntp!psinntp!newstand.syr.edu!cat.syr.edu!dms
- From: dms@cat.syr.edu (David Sternlicht)
- Newsgroups: comp.windows.interviews
- Subject: Re: what is kit in local.def
- Message-ID: <1992Dec28.115502.22176@newstand.syr.edu>
- Date: 28 Dec 92 16:55:00 GMT
- References: <1992Dec23.195705.26071@iplmail.orl.mmc.com>
- Organization: CASE Center, Syracuse University
- Lines: 30
-
- chucks@iplmail writes:
-
- I have built iv3.1 on a sun4. in local.def the following is found.
- /*
- * Default customization of kits.
- * Possible flags to define:
- * sgi_motif_kit (SMFKit), motif_kit (MFKit),
- * openlook_kit (OLKit), bw_kit (MonoKit)
- */
- #ifndef KitFlags
- #define KitFlags \
- -Dmotif_kit \
- -Dsgi_motif_kit \
- -Dopenlook_kit \
- -Dbw_kit \
- -Ddefault_kit=SMFKit
- #endif
-
- what is the function of selecting a different kit. I have not found
- anything in the papers regarding this.
-
- These flags control how src/InterViews/kit.c gets compiled. Therefor you could
- concievably choose not to allow the creation of certain kit styles by deleting
- one of these flags. See table 1.1 in section 1.3.1 of the reference manual for
- the setting of kit styles at runtime.
-
-
- dave sternlicht
- mit X consortium
- dave@expo.lcs.mit.edu
-