gary@sun.mcs.clarkson.edu (Gary Levin) (10/14/89)
Has anyone here had experience with the MPW //gs cross compiler? Is it reasonably stable? Can it be used to generate programs for the rest of the // family? With what size restrictions? I would get the MPW //gs C bundle with the //gs Tools, Assembler, Compiler, and MPW. Does it in fact let you make //gs disks on a Mac? If not, how do you get your program from the Mac to the //gs? I am normally a Unix / MSDOS programmer who has some software that others are requesting on the Apple family. THINK C let me port to the Mac, now I need to know how to get to the // line. Thanks for any information. APDA just gives me an 800 number to find out where the user groups are. This seems to be the largest user group I am likely to find. (I think this is suitable for cross posting. Please remember the cross posting when replying.) -- Gary Levin/Dept of Math & CS/Clarkson Univ/Potsdam, NY 13676/(315) 268-2384 BitNet: gary@clutx Internet: gary@clutx.clarkson.edu
jazzman@claris.com (Sydney R. Polk) (10/18/89)
From article <GARY.89Oct13170119@milo.clarkson.edu>, by gary@sun.mcs.clarkson.edu (Gary Levin): > Has anyone here had experience with the MPW //gs cross compiler? Is > it reasonably stable? Can it be used to generate programs for the > rest of the // family? With what size restrictions? I would get the > MPW //gs C bundle with the //gs Tools, Assembler, Compiler, and MPW. We here at Claris are using it for both AppleWorks (IIe/IIc) and AppleWorks GS (IIgs). It is very nice, esp. compared to anything else. AppleWorks GS is very large (790K) and we haven't had any problems with size. We do however, require a 6500K partition to link the whole thing together. You really need two to four meg for a reasonable size application. As for transfering, MPW IIGS Tools comes with a utility called "DuplicateIIGs" which can transfer files from your mac disk to a prodos disk. It only reads and copied into the boot direcotry of the prodos disk and it does not initialize the disk, but we just use the same disk over and over again. Unfortunately, HFS (the Mac file system) does not have sparse file optimizations like ProDOS does, so when we do a full build, we have to use AppleShare. We copy the file onto the server using MPW and copy it onto a ProDOS 3.5 using the GS finder and the AppleShare FST. It really works great. To give you some idea, AWGS is about 350,000 lines of code, 90% in assembly and 10% in C. It takes about 3.5 hours to build the program and the utilities from scratch. We estimate that it would have taken three or four DAYS continuously to assemble everything in APW, and we had to write a utility to combine executables because the APW linker could not handle it. Some other neat things include no 64K limit on source files, the ability to use Projector to keep an archive of source (it saved us many times), a real editor, a real environment, compiling and assembling in background, no auxiliary macro files associated with each source file, 512 level macro nesting compared to four, conditional assembly and compilation, make and makefiles, PascalIIGS is now available, the high level languages are exteremly compatible with the MPW Macintosh compilers, genereates OMF 2.1 files automatically, expresses the executable automatically, real shell scripts, much easier printing, etc. The list goes on. If you can afford the machine (a Mac II with 4 meg is recommended) this is -- Syd Polk | Wherever you go, there you are. jazzman@claris.com | Let the music be your light. GO 'STROS! | These opinions are mine. Any resemblence to other GO RICE! | opinions, real or fictitious, is purely coincidence.