Advertisement

SPHIGS/SRGP and CodeWarrior Question

Started by April 25, 2002 03:26 PM
2 comments, last by jdscolam 22 years, 8 months ago
Hey all, Yes, I am a newbie to this site/board/game programming, and I really have run into a bind. I''m about to start going through Foley''s book on Computer Graphics in C (C++ I hope) and I''ve run into a bit of a snag. I know he uses the SPHIGS/SRGP package in his book for most of the coding examples, and upon looking into things the group that is going through the book with me has decided that it would be too much work at this point to translate all his examples into OpenGL and try them. So my questions are simple: Where can I get a copy of the SPHIGS/SRGP package for Win 2k/98/XP? How do I install the package onto Windows 2k, 98, or XP systems? How do I get the package into a usable fasion (i.e. it will compile, work, and produce results) under one (or hopefully all) of the following development suites: Visual Studio 6.0 (Visual C++ is our language of choice at this moment), Metrowerks Code Warrior 6.0 (is what I have been messing with so far), and Visual Studio .NET (Specifically Visual C++ .NET which is what we''ll be using for our primary language in the future)? Any help that I can get with this would be excellent! I''m really in a bind here, and responsible for all of this stuff that I can''t even get to work. Thank you all for your time! I really appreciate it! Sincerely, Jon PS: On a funnier note (also I could use help on this) I noticed that the OpenGL API libraries GL.h and GLU.h are not present on my system in any fashion other than having been installed by CodeWarrior 6.0. That''s not the weird thing though, the weird thing is that CW won''t even compile those libraries in a real project (NeHe''s Combat Program Code). So far the complier always gets stuck on the following lines of code: BEGIN CODE ---------- #include <GL/gl.h> #include <GLU/glu.h> END CODE -------- Basically the complier hangs and says that it can''t find "GL/gl.h" Now I''m almost positive that the code author is using the / to say "either GL uppercase or gl lowercase for the file" and the compiler should recognize that syntax and just go on. Just in case it was a fluke I modified the NeHe code to just represent the uppercase GL.h and GLU.h (which matches the copy I have), and it passed by those lines of the code, compiling until it hit the same line of code in the actual GL.h library itself where the code reads "#include <GLU/glu.h>" When that happened I was about ready to kill myself (not to mention CW) and just gave up figuring that I''ll draw the line at editing industry standard API''s (they can do it a heck of a lot better than I can). So, as the saying goes.... "HELP!!!" Thanks . -------------------------- He knew what he doing, but look what happened!
-------------------------------------He knew what he doing, but look what happened!
actually you want to put the lines in as written...
#include "gl/gl.h"
#include "gl/glu.h"

Most compilers don''t include the gl headers in the standard include directories ( with stdio.h and such i.e. metrowerks/..blah../include/stdio.h) instead they put it in a subdirectory called ''gl'' so to use the gl headers, you either have to add the directory ''metrowerks/..blah../include/gl''to your compiler include path or do what they did in the tutorial and say:
#include "gl/gl.h"


Advertisement
Where can I get a copy of the SPHIGS/SRGP package for Win 2k/98/XP?

check out the book site at addison-wesley:
http://cseng.aw.com/book/related/0,3833,0201609215+7,00.html
Hey,

Thanks a ton for the location for SPHIGS/SRGP. I dled them and I''m going to try messing with them today and tomorrow to see if I can get them to work/plug into any of my programs.

If you have any more advice (i.e. how to actually go about getting the SPHIGS package to work practically) please let me know.

Jon

-------------------------------------
He knew what he doing, but look what happened!
-------------------------------------He knew what he doing, but look what happened!

This topic is closed to new replies.

Advertisement