home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!emory!worms-emh2.army.mil
- From: bob@worms-emh2.army.mil (Bob Kane)
- Newsgroups: comp.databases.informix
- Subject: 4GL, Make & SCCS
- Message-ID: <9468@emory.mathcs.emory.edu>
- Date: 4 Sep 92 09:48:11 GMT
- Sender: walt@mathcs.emory.edu
- Reply-To: bob@worms-emh2.army.mil (Bob Kane)
- Lines: 26
- X-Informix-List-ID: <list.1429>
-
- If anyone out is currently using Unix Make files to compile 4GL programs that
- are maintained by SCCS (Source Code Control System) I would appreciate some
- pointers. I am trying to set this up for all of our systems, but I am not
- terribly familar with SCCS and how to make the proper calls to it from the
- makefile. For example, 4GL modules that use a specific globals file require
- that the globals source file (the 4GL code) be available and readable at
- compile time. If you are using the makefile to compile a single module that
- you have changed, it would appear that you have to check out a copy of the
- globals file from SCCS before the compile. This means that each rule for
- a 4GL has to check out a copy of the globals file, and unget it when it is
- finished, so it is availble for the next module. Or is my logic faulty?
-
- Example of the rules I have set up is below:
-
- module.o :
- $(GET) -e s.globals.4gl
- $(GET) -e s.module.4gl
- c4gl -c module.4gl
- unget s.globals.4gl
- unget s.module.4gl
-
- -----------------------------------------------------------------------------
- Bob Kane Internet: bob@worms-emh2.army.mil (IP 134.235.9.2)
- TechDyn Systems Voice: (049) 6241-487304 (WORMS, GERMANY)
- CMR 421, BOX 706 Fax: (049) 6241-74530
- APO AE 09056 CIS: 71054,2661
-