National Institute of Standards and Technology (NIST)
OpenGL Version 1.2.1 /GLUT 3.7.1/CVF6.1a
Developers Studio Useage JMS 2000.12.04 Rev.0
Ed Dunlop lays the groundwork for acquiring
Bill Mitchell's F90GL environment (Message #2458).
If you follow Ed's instructions, you'll be able
to compile, link, and run ~13 different .exe's
from the CVF command line environment. From my
point of view, ModView.Exe is the most instructive
of the .exe's.
I've been successfully using NIST's v1.2.1
from within developer's studio for a couple of
months now. Since my arrival path wasn't straight,
I invite replies to simplify what I say here.
My environment is:
Athlon 700 processor
Windows NT4.0+Service Pack 4
Diamond Viper 550 video card.
Adobe Acrobat v4.0 (or the reader)
Text's: Purchase The OpenGL ARB documentation for
OpenGL Version 1.1:
OpenGL Programming Guide ISBN 0-201-46138-2
OpenGL Reference Manual ISBN 0-201-46140-4
(^appendix F is worth the whole cost.)
I'll include the things which took me a long time to
figure out in getting to where I am.
1. Compaq hosts "our version" of the NIST software as
a download at their website (but doesn't support it).
"downloads" f90gl precompiled files Feb. 25, 2000
built with CVF6.1 & uSVC++6.0
2. (At least the NIST...) Download has long filenames
which get clobbered by PKUnZip. WinZip v7.0 unpacked
the files gracefully. What you then have is:
OpenGL Version 1.2.1 and GLUT Version 3.7.1
3. Note that NIST OpenGL uses GLUT rather than the GLAUX...
so don't waste any time on GLAUX related information.
The Adobe Acrobat .PDF documentation formats are good.
Download v1.2.1 documentation at:
(Note: this does not include appendix F in the hardcopy for v1.1)
And for v3.7.1, go to SGI's site and find:
"The OpenGL Utility Toolkit (GLUT)" (PDF)
by Mark J Kilgard, Silicon Graphics, Inc.
November 13, 1996
4. Put f90gl.lib, f90glu.lib, and f90glut.lib in subdirectory
C:Program FilesMicrosoft Developers StudioDF98Lib
Also, put all the .mod files there.
5. Follow Ed Dunlop's directions in message #2458
to see things work from the command line.
(It's a confidence builder.)
6. Open a project in developer's studio as a
FORTRAN CONSOLE APPLICATION
And request a simple project. Call it ModView.
After the project has been created, overwrite the new
ModView.F90 with NIST's ModView.F90.
7. Modify the Project Settings as follows:
"Fortran": Data Options
- Use Bytes as RECL=unit for Unformatted Files
- Use Run-time Libraries - Static*
"Link" : Object/library modules:
f90gl.lib f90glu.lib f90glut.lib kernel32.lib
8. Compile and link in debug mode.
9. If these directions are insufficient to get ModView.F90 running,
post a complaint. No
bad advice is intended.
General guidance for geezers:
If you're a non- "Fortran 90" programmer, you'll have to step up
to the line on programming in Fortran 90. Its not too painful
in CVF6.1a because most of the old ways of doing things
are still allowed.
"Implicit None" seems like a real hassle at first, but is a
significant aid to the debugger in helping you to get your
code running. The level of debugging detail totally outclasses
uS Fortran Powerstation 4.0's capability. Not flawless,
but extremely good.
Variable types: Integer*2, Real*4, etc., etc. are allowed.
But OpenGL is imple