Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 4 of 4

Thread: Solaris Opengl Header problems

  1. #1
    Junior Member Newbie
    Join Date
    Mar 2007
    Posts
    23

    Solaris Opengl Header problems

    Hi,

    Im using solaris with bash.

    I have entered CC -o Demo demo.cc and I get the following error:

    Code :
    Error: Could not open include file<GL/gl.h>.
    I get several more for glx, glext and glut

    This means that the linker can not find the GL files as they are not in the system path. How do you do this in Solaris & Bash?

    Thanks For your help
    -Alex

  2. #2
    Junior Member Regular Contributor
    Join Date
    Jun 2006
    Location
    Edinburgh - Scotland
    Posts
    147

    Re: Solaris Opengl Header problems

    Actually it means the compiler not the linker cant find the files. Find the location of the files on your system. A brute force method is
    Code :
    find / -name gl.h
    and then add the path of that to the compiler using the -I flag e.g. if the gl.h is in
    Code :
    /usr/local/include/GL/gl.h
    then you would use
    Code :
    CC -I/usr/local/include -o Demo demo.cc
    Though I suspect you are going to have many more problems e.g. unresolved symbols because you aren't linking in the openGL and GLUT libraries.

    These kind of posts should really go in the Linux forum not here. Though I would suggest just reading the man pages on the compiler and linker to get an understanding of what they do and the command line flags first.

    --Stuart.

  3. #3
    Junior Member Newbie
    Join Date
    Mar 2007
    Posts
    23

    Re: Solaris Opengl Header problems

    hi,

    I tried what you said, it still is wanting those files...

    -Alex

  4. #4
    Junior Member Regular Contributor
    Join Date
    Jun 2006
    Location
    Edinburgh - Scotland
    Posts
    147

    Re: Solaris Opengl Header problems

    A bit more information might be helpful. For instance;
    1) So you found the directory containing the files. Where are they?
    2) What EXACTLY did you type on the command line to compile the demo?
    3) Show the EXACT output you get from that command line.

    People can't help without information to work with.
    --Stuart.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •