ctm@russell.cs.unm.edu (Clifford T. Matthews) (09/16/90)
Just a couple quick comments on Walt Leipold's review of ROMlib. >> The most difficult >> part of the porting process was getting the supplied ROMlib makefile >> working on my system; ARDI's development was done with Gnu make and gcc, >> so I had to make some changes to get the bloody thing working with Sun's >> standard tools. But even this took only a few hours; the total time for >> the most difficult port of a Mac application was about eight hours. Although some of the early beta tapes inadvertantly assumed you were using gnu make and gcc [after all, *we* were; doesn't everybody :-)] the current release makes no such assumptions. Everything now comes configured to use the standard utilities by default. >> ... The >> Standard File routines work normally within each virtual Macintosh >> volume, except that you cannot type to select a file in the SF{Get,Put} >> routines. You *can* type to select file names with SFGetFile; I guess we forgot to tell Walt (sorry Walt). >> The bottom line: ROMlib is a nice product, and appears to be a bargain at >> $400/copy. If you have a Sun 3, you can develop and run Mac software on >> it today. If you have some other flavor of Unix platform, I recommend >> that you call ARDI and tell them you're interested in a version for your >> system -- they might just be able to supply you with one. Hey if you order now you get a free pre-alpha, known-buggy, copy of "Executor" the program that allows you to run binaries that were compiled on the Macintosh. Another posting describes the current state of executor. Cliff Matthews Abacus Research & Development, Inc. (505) 766-9115 [not affiliated with the University of New Mexico]