mccoy@mace.cc.purdue.edu (Chris McCoy) (02/14/91)
I grabbed the source for ACM 2.0 from expo and after much effort was able to compile it. (ACM is the F16 flight simulator recently announced) When running on a 320 with 32MB RAM and a greyscale monitor, the update seems to flicker considerably. On a monochrome SUN SPARC 1, the display does not. Has anyone else tried ACM yet, and had similar experiences? I'm more curious about the ramifications w.r.t other software than just this particular piece. Might this be a side-effect of having greyscale vs. monochrome? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Chris McCoy : INTERNET: mccoy@acn.purdue.edu UNIX Systems Programmer : UUCP: ...!ecn-ee!mccoy Ag. Computer Network, Purdue Univ. : VOICE: (317) 494-8333 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
mccoy@mace.cc.purdue.edu (Chris McCoy) (02/14/91)
>I grabbed the source for ACM 2.0 from expo and after much effort was >able to compile it. (ACM is the F16 flight simulator recently announced) >When running on a 320 with 32MB RAM and a greyscale monitor, the update >seems to flicker considerably. On a monochrome SUN SPARC 1, the display >does not. Has anyone else tried ACM yet, and had similar experiences? Well, I seem to have become popular real fast! I've received many responses from people who want to get ACM running, so I'm going to try and post some of the steps I took to get it working. I didn't write down the steps when I got it working, but I'll give you the list I gave the first person who requested them (editted to give more information). There are probably many different angles to getting this to compile, but I just took the brute force method -- compile and fix what doesn't compile! -- since the imake templates and macros as supplied by IBM (seem to) depend upon software being in a certain location, I untared the source in my own sub-directory and created a sym-link in '/usr/lpp/X11/Xamples' (this causes some problems with the Makefiles and relative directories, so it would be better to untar the source directly in the Xamples directory) -- Maybe IBM can comment on this one, but the assignment TOP = TOPDIR in 'IBM.macros' and 'Imake.tmpl' should be TOP = $(TOPDIR) At least I needed to change this either in the imake includes or in the Makefiles created by imake in order to get make to run properly. -- made sure that 'imake' in /usr/lpp/Xamples/util/imake was built (see README in Xamples directory) -- set the IMAKEINCLUDE shell variable to point to the directory where the imake files are located, namely $ IMAKEINCLUDE=-I/usr/lpp/X11/Xamples/util/imake.includes $ export IMAKEINCLUDE -- set the IMAKECPP shell variable to point to the X cpp $ IMAKECPP=/usr/lpp/X11/Xamples/util/cpp/cpp $ export IMAKECPP -- modified the file 'acm.def' to point to necessary spots, and commented out the CDEBUGFLAGS line: #ifdef StandAloneImake TOP = . IMAKE = /usr/lpp/X11/Xamples/util/imake/imake IRULESRC = /usr/lpp/X11/Xamples/util/imake.includes IMAKE_DEFINES = -DStandAloneImake IMAKE_CMD = $(IMAKE) -s Makefile $(IMAKE_DEFINES) #endif -- ran 'imake -DStandAloneImake -s Makefile' to build a suitable Makefile -- ran 'make Makefiles' to build makefiles in the sub-directories -- editted the Makefile in sub-directory fsim : -- Changed TOP to 'TOP = $(..)' -- Changed TOPDIR to 'TOPDIR = /usr/lpp/X11/Xamples' -- Changed LIBSRC to 'LIBSRC = /usr/lpp/X11/Xamples/lib' -- Changed CFLAGS to include 'STD_INCLUDES' If you get this far, then you should end up with an 'acm' and an 'acms' in directory 'fsim'. Please let me know what happens. We probably shouldn't waste much bandwidth discussing this, so please send me your responses and I'll summarize after a resonable time. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Chris McCoy : INTERNET: mccoy@acn.purdue.edu UNIX Systems Programmer : UUCP: ...!ecn-ee!mccoy Ag. Computer Network, Purdue Univ. : VOICE: (317) 494-8333 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=