[comp.os.cpm] MAKE for CP/M?

dave@stcns3.stc.oz.AU (Dave Horsfall) (01/16/90)

No, this is not a joke.  Has anyone ported "make" for CP/M?  It would
have to be really simple, of course.  Ignore the (non-existent) time
stamps and just re-compile (or perhaps keep a simple data-base of
time stamps based on the file-modified bit?) etc.  Ignore the rules
about yacc/lex/whatever, and heaps of other shortcuts...

For the record, my C compiler supports execl()/execv(), as well as
spawnl(), spawnv() and spawnve(), (but not fork()/system() :-).
(Please don't ask for the compiler - it's commercial, and the author
probably reads this group.  I can supply details upon request though.)

Failing an existing product, I may take a stab at doing it myself.
Although constrained by 360k floppies (albeit with 64kb RAM disk) does
tend to severely limit one...

(Hmmm...  has anyone outside of Australia heard of the Microbee
computer, in its various incarnations?  Great little machine!)

Cheers, as they say "down-under".

PS - that dis-assembler was great!

-- 
Dave Horsfall (VK2KFU),  Alcatel STC Australia,  dave@stcns3.stc.oz.AU
dave%stcns3.stc.oz.AU@uunet.UU.NET,  ...munnari!stcns3.stc.oz.AU!dave

michaelk@copper.WR.TEK.COM (Michael D. Kersenbrock) (01/18/90)

Yes, I did quite some years ago.  It had to jump thorough some hoops to
work properly (esp. for it to terminate when a module had a compile
error).  

> It would
>have to be really simple, of course.  Ignore the (non-existent) time

Why?  My "base" for my port was one posted (from Australia) for some
odd (for here) version of UNIX.  It ran under CP/M pretty much the
same as one does for UNIX.

>stamps and just re-compile (or perhaps keep a simple data-base of
>time stamps based on the file-modified bit?) etc.  Ignore the rules
>about yacc/lex/whatever, and heaps of other shortcuts...

One thing though: mine WAS for CP/M 3.0 ("CP/M Plus") with time
stamps supported.  If the CP/M 3.0 timestamp "call" were implemented
under some other CP/M (using a OS-call filter, I forget the CP/M term),
then it'd work as-is.

>For the record, my C compiler supports execl()/execv(), as well as
>spawnl(), spawnv() and spawnve(), (but not fork()/system() :-).
>(Please don't ask for the compiler - it's commercial, and the author
>probably reads this group.  I can supply details upon request though.)

Mine was built using the Aztec C II compiler.  My mechanism was to build
a .BAT file with the suitable "command-lines", then chain to that file.

>
>Failing an existing product, I may take a stab at doing it myself.
>Although constrained by 360k floppies (albeit with 64kb RAM disk) does
>tend to severely limit one...

I had 1.2 MB floppies and 1Meg of DRAM (mostly disk cache).  The floppy size
might hurt things if your compiler is big....

>
>(Hmmm...  has anyone outside of Australia heard of the Microbee
>computer, in its various incarnations?  Great little machine!)
>
>Cheers, as they say "down-under".
>
>PS - that dis-assembler was great!
>
>-- 
>Dave Horsfall (VK2KFU),  Alcatel STC Australia,  dave@stcns3.stc.oz.AU
>dave%stcns3.stc.oz.AU@uunet.UU.NET,  ...munnari!stcns3.stc.oz.AU!dave


I had my "make" put into the Simtel CP/M archive (probably under CPM3).
It'd be a good starting point if you can't upgrade to CP/M 3.0 nor
write something to "fake" CP/M 3.0's "standard" timestamp call.
I might have it at home as well.  The old beast is gathering dust....

Mike Kersenbrock WB4IOJ
Tektronix Microprocessor Development Products
michaelk@copper.WR.TEK.COM
Aloha, Oregon
--
Mike Kersenbrock
Tektronix Microprocessor Development Products
michaelk@copper.WR.TEK.COM
Aloha, Oregon