I was following the tutorial on setting up OpenGL on Mac OS X to the letter. But it doesn't run >_< http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=Mac_OS_X It actually compiles but returns some weird error when I try running it. Anyone found a solution? Jiro-

That kind of depends on the error.

"weird" is not a good enough description.

also, you should say what version of OS X your using

Hi again,

Zerolink: unknown symbol '_ReSizeGLScene'

GLUT Test App has exited due to signal 6 (SIGABRT).

That was the error.

OS X version 10.3.6


(As a sidenote, I tried installing that X11SDK and it installed, but it disappeared...zzzz -.- It's not where the apple site said it should be, in fact it is nowhere at all!)

that's because that's just an example. In it, 3 of the functions aren't defined(one which is named "ReSizeGLScene"), just try giving them empty definitions, that should work until you have something to put in them.

btw, that's a link error, not a runtime error(unless, for some reason, it's trying to dynamically link with something it thinks contains that function, but that doesn't seem likely)

I've been trying the same on 10.2.8 and had also problems. it was necessary to include additional frameworks. at the moment i have those 4 files included:
foundation.framework
libstdc++.a
OpenGL.framework
GLUT.framework

As mentioned you need to define your functions. the function called in glutRespaheFunc(...) or glutDisplayFunc(...) is called through the glut callback. whenever you want the scene to be redrawed, you call the glut callback "glutReshapeFunc".

if you havent done it yet, download the glut reference and have a look at it.

-joedelord

Thanks guys for the replies, it was so obvious i didn't see it. It's almost 8AM here and I spent the night awake...guess my brain went to sleep... ;-)

That is a runtime error, because Apple's XCode by default links at runtime instead of at compile time (only for development builds mind you), which greatly speeds up compiling, however, unlike the compiler, it doesn't usually give such a clear error message as it did here.