taw@cmu-ri-fas.ARPA (Tom Wood) (08/21/85)
If you are a MegaMax C user and have received the version 2.1 update, I
am interested in hearing about how you have arranged the various
applications on disks (assume a two-drive system). I, for one, have been
unable to come up with a satisfactory arrangement (some of the new programs
are larger in this release, and many of the "neat" features depend on
program A being on the same volume as program B.) Interesting replies will
be posted.
Tom Wood
C-MU Robotics Institute
taw@cmu-ri-fas
...!{seismo,ucbvax}!cmu-ri-fas!taw
--
uucp: ...!seismo!cmucspt!cmucsfs!taw
arpa: taw@cmu-ri-fas.ARPAmike@smu (08/24/85)
Try this:
System (boot) disk: Batch
editor
<anything else that seems nice>
Other disk: mmcc
mmlink
syslib
all the .h files
a ram disk starter
One can then have the ram disk starter put the compiler, linker, and
libraries on the ramdisk, freeing up the second drive for source
files.
Problems include the fact that a program under development frequently
crashes the system, and re-building the ramdisk is not exciting.
The ramdisk should be big enough to keep the linker happy. You'll
notice that links are MUCH faster.
Mike McNally SMU
mike@smu
...convex!smu!mike