# OpenGL Having problems getting opengl working with mingw

## Recommended Posts

After spending the last four hours trying to get this working, I'm resorting to asking for help. I've installed MinGW on my XP64 machine, along with GLUT. I've put glut.h in C:\MinGW\include\GL, libglut32.a in C:\MinGW\lib and glut32.dll in C:\WINDOWS\system32. When I try to run a sample program, I get the following:
g++ helloGL.cpp -lopengl32 -lglu32 -lglut32
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x1c): undefined reference to __glutInitWithExit'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x37): undefined reference to __glutCreateWindowWithExit'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x7e): undefined reference to _imp__glViewport'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x8c): undefined reference to _imp__glMatrixMode'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x93): undefined reference to _imp__glLoadIdentity'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0xc9): undefined reference to _imp__glOrtho'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0xd7): undefined reference to _imp__glMatrixMode'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0xee): undefined reference to _imp__glClear'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0xf5): undefined reference to _imp__glLoadIdentity'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0xfc): undefined reference to glutSwapBuffers'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x12c): undefined reference to _imp__glClearColor'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x13a): undefined reference to _imp__glEnable'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x186): undefined reference to glutInitDisplayMode'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x19a): undefined reference to glutInitWindowSize'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x1b2): undefined reference to glutDisplayFunc'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x1be): undefined reference to glutReshapeFunc'
C:\.../ccY1lEyc.o:helloGL.cpp:(.text+0x1c8): undefined reference to glutMainLoop'
collect2: ld returned 1 exit status

Here's my code, which I'm assuming works since I got it from a tutorial.
#include <stdlib.h>
#include <GL/glut.h>

void keyboard(unsigned char key, int x, int y);
void display(void);

int main(int argc, char** argv)
{
glutInit(&argc, argv);
glutCreateWindow("GLUT Test");
glutKeyboardFunc(&keyboard);
glutDisplayFunc(&display);
glutMainLoop();

return EXIT_SUCCESS;
}

void keyboard(unsigned char key, int x, int y)
{
switch (key)
{
case '\x1B':
exit(EXIT_SUCCESS);
break;
}
}

void display()
{
glClear(GL_COLOR_BUFFER_BIT);

glColor3f(1.0f, 0.0f, 0.0f);

glBegin(GL_POLYGON);
glVertex2f(-0.5f, -0.5f);
glVertex2f( 0.5f, -0.5f);
glVertex2f( 0.5f,  0.5f);
glVertex2f(-0.5f,  0.5f);
glEnd();

glFlush();
}



##### Share on other sites
I'm going to go out on a limb here and say it's got something to do with you not telling it which directories to look in for the libraries (I've had quite a few issues with it myself, which is why I just get CodeBlocks to do everything for me now). Try using this:
g++ -LC:/MinGW/lib helloGL.cpp -lopengl32 -lglu32 -lglut32

##### Share on other sites
Thanks for the response. Unfortunately that didn't work.

##### Share on other sites
Apparently they've changed the compiler since way back when... Seems you have to include the libraries in the compiling line in addition to any source files these days (at least that's what Code Blocks is doing). The end result being:
g++ helloGL.cpp C:/MinGW/libopengl32.a C:/MinGW/libglu32.a C:/MinGW/libglut32.a -o helloGL.exe

I added the output target too, that way you don't end up with 'a.exe', which can be a little annoying if you plan on compiling multiple things in the same directory. You might need to add libgdi32.a too (depending on how glut works). That should fix your problem though.

##### Share on other sites
Thanks again.

I ended up just installing Code Blocks and following the tutorial, and that seems to have gotten it working.

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627665
• Total Posts
2978527
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 10
• 12
• 22
• 13