Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!ucsfcgl!cgl.ucsf.edu!kneller From: kneller@cgl.ucsf.edu (Don Kneller) Newsgroups: comp.sys.ibm.pc Subject: Re: MKS Make Message-ID: <11574@cgl.ucsf.EDU> Date: 5 May 89 01:41:19 GMT References: Sender: daemon@cgl.ucsf.edu Reply-To: kneller@socrates.ucsf.edu.UUCP (Don Kneller) Organization: UCSF Computer Graphics Lab Lines: 77 In article lfk@mbio.med.upenn.edu (Lee Kolakowski) writes: > > >I posted a note asking about MKS Make. I was less than clear about >what I wanted to know, also I got the first name of author of NDMAKE >wrong (Sorry Don Kneller! :->) That's OK. I have a brother named Doug. > >I want to know the following: > > 1) Does it work with shell so that I can have parts of a > script in may makefile, or does it use the dos exec function? > > 2) Does it do anything radically different and better than > NDMAKE. I think the big difference is MKS Make is more attuned with MKS shell. We (OPUS Make) are more like a UNIX make running under MSDOS (and OS/2) with some higher level support that looks like a shell (conditionals, foreach and while). We will be adding MKS shell support and MKS RCS support in the near future, but we don't have it yet. > > 3) Is it possible to be running the MKS ksh, then Jove > then type M-x compile then have make run than have MS-C > run and have enough space? Supposedly OPUS will do that. Yes, OPUS does run in *at most* 3K of memory with a command line flag. So, if you can compile from inside of your editor, you will be able to "make" from inside of it too, which is really what you want to do if you're maintaining a project. > > 4) What are some of the other features of the make? I'll mention some of our features (at the risk of plugging). - automatic response files for link and lib (and link and lib compatibles (TLINK, OPTLINK, OPTLIB) to overcome the DOS command line limits. - multiple directory support - POLYTRON PVCS logfile support (Burton Systems TLIB and MKS RCS pending) - enhanced I/O redirection ala OS/2 under MSDOS - OS/2 version included One major difference is that we have an automatic dependency generator which snoops through your source files to find includes and deposits the information in your makefile. > 5) There is some info about ar. Is the output of the ar .lib format? Our version 5.20 supports timestamps inside of LIB files in an OPTLIB compatible format. So you don't have to have separate OBJ files and duplicates inside of the library. > 6) Is it worth the $149.00 as compared to OPUS? If you need the MKS shell compatibility now, I would say yes. If not, then it is up to you. We have some of the capability of the shell builtin to our product. Our dependency generator is a nice addition. ----- Don Kneller UUCP: ...ucbvax!ucsfcgl!kneller INTERNET: kneller@cgl.ucsf.edu BITNET: kneller@ucsfcgl.BITNET SMAIL: OPUS Software 1032 Irving Street #439 San Francisco, CA 94122 (415) 664-7901 (OPUS) 476-8291 (my other job) ----- Don Kneller UUCP: ...ucbvax!ucsfcgl!kneller INTERNET: kneller@cgl.ucsf.edu BITNET: kneller@ucsfcgl.BITNET