Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!amdcad!sun!pitstop!sundc!seismo!uunet!portal!cup.portal.com!Michael_mkahl_Kahl
From: Michael_mkahl_Kahl@cup.portal.com
Newsgroups: comp.sys.mac.programmer
Subject: Re: Lightspeed C projects
Message-ID: <6879@cup.portal.com>
Date: 26 Jun 88 02:13:32 GMT
References: <1407@its63b.ed.ac.uk> <4710@husc6.harvard.edu>
Organization: The Portal System (TM)
Lines: 21
XPortal-User-Id: 1.1001.4169

> Something that I would like to see in LSC is the ability to define
> preprocessor symbols for the *project* as a whole (ala Unix "cc -D").
> ...
> "Putting the definitions in an include file" doesn't work because I want
> different definitions depending on the particular project.  LSC's #include
> search path partially solves the problem, except it means that you can only
> have one project per directory, and the "library" file must be in a distinct
> directory.

There is no great way to do this in LSC 2.xx, but there is in 3.0 (shipping
imminently).  The method is basically the "put the definitions in an include
file" approach, with a hack to make it work for multiple projects in a single
directory.  As you may know, any directory whose name is parenthesized is
skipped during directory searches.  In 3.0, this rule is modified:  if a
directory's name is the parenthesized name of the project, it's not skipped.
Thus each project sharing a directory can have its own private subdirectory.
Each subdirectory can have a different "config.h", for example.

In addition, LSC 3.0 pre-#defines the symbol "THINK_C".

-- Michael Kahl, Symantec