Sign in to follow this  
Darkware

OpenGL openGL errors

Recommended Posts

When using the code you download here: http://nehe.gamedev.net/data/lessons/devc/lesson01.zip which uses openGL (lesson 1 code), why do I get the following errors when trying to run it? I'm using Dev-C++ compiler by the way. Also, for Dev-C++ you must #define CDS_FULLSCREEN because Dev-C++ isn't a compiler that already defines it. THIS define is NOT in the downloadable coding for some reason, so you'll have to put it in yourself. C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x38):lesson1.cpp: undefined reference to `glViewport@16' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x45):lesson1.cpp: undefined reference to `glMatrixMode@4' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x4d):lesson1.cpp: undefined reference to `glLoadIdentity@0' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x84):lesson1.cpp: undefined reference to `gluPerspective@32' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x91):lesson1.cpp: undefined reference to `glMatrixMode@4' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x99):lesson1.cpp: undefined reference to `glLoadIdentity@0' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0xb7):lesson1.cpp: undefined reference to `glShadeModel@4' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0xd1):lesson1.cpp: undefined reference to `glClearColor@16' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0xe0):lesson1.cpp: undefined reference to `glClearDepth@8' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0xf0):lesson1.cpp: undefined reference to `glEnable@4' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x100):lesson1.cpp: undefined reference to `glDepthFunc@4' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x115):lesson1.cpp: undefined reference to `glHint@8' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x13b):lesson1.cpp: undefined reference to `glClear@4' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x143):lesson1.cpp: undefined reference to `glLoadIdentity@0' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x258):lesson1.cpp: undefined reference to `wglMakeCurrent@8' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x282):lesson1.cpp: undefined reference to `wglDeleteContext@4' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x854):lesson1.cpp: undefined reference to `ChoosePixelFormat@8' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x898):lesson1.cpp: undefined reference to `SetPixelFormat@12' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x8ce):lesson1.cpp: undefined reference to `wglCreateContext@4' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0x914):lesson1.cpp: undefined reference to `wglMakeCurrent@8' C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccETaaaa.o(.tex t+0xc2f):lesson1.cpp: undefined reference to `SwapBuffers@4'

Share this post


Link to post
Share on other sites
I do not see why you are having problems. If you open the "Lesson1.dev" file, it has the correct libraries already in there:

-lopengl32 -lglu32 -lglaux -lkernel32 -luser32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -lodbc32 -lodbccp32


All I had to do was comment out the line:

#include <gl\glaux.h> // Header File For The Glaux Library


And that worked for me fine. I just installed Dev-CPP as well, so I havce not made any chagnes to it. I also do not see how you are having troubles with "CDS_FULLSCREEN". In that tutorial they include windows.h, so it is defined already. Once again, I downloaded that link you posted and it compiled without any modifications except removing the glaux.

I'd say make sure you open the "Lesson1.dev" file with Dev-CPP and you should be fine. Make sure you are using the latest Dev-CPP as well. Good luck!

- Drew

Share this post


Link to post
Share on other sites
ok, I have been researching this for hours. My brain feels like it's going to leak out of my ear.

I downloaded and unziped http://nehe.gamedev.net/data/lessons/devc/lesson01.zip then opened the project file. Under Project>ProjectOptions and in the "Further object files or linker options" place, there was nothing typed as you said. It was just blank. Also, no code appears to be visible at all either. I try to click on the lesson1.cpp link on the left where the manager colomn is, but nothing happens. I can only see code when I open the lesson1.cpp file specifically.

My way around this: Create a new project and copy/paste code into a new file, then save that project.

~~~~~~~~
NOW... this: http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=01 is the only tutorial or documentation on this website I can find that covers the installation of openGL. It does not specificy where to instal the lib, dll, or h files. I am completely new to this, so I don't know where these go. From my research, I have found that most of the documentations on installing openGL, mention the G++, include, and lib folders, so I just went and installed all the lib, dll, and h files to those locations. I also did not know how to "link" and what specifically NEEDED to be linked. I also found out that the dll files were supposed to go in your system32 folder. I now go to Project>ProjectOptions and under "Further object files or linker options" place, I type -lopengl32 -lglu32 -lglut32 and hit "OK".

Now when I compile, I just get errors like:
(.text+0x854):mycfilename.cpp: undefined reference to 'ChoosePixelFormat@8'
and whatnot. Just three of them though.

SOOOOOoooo..... I never would have guessed this to be this difficult. There are not very many documentations online that go over ALL installation setps for ALL of the files you get and tell you where EXACTLY you're supposed to place the files. This is slightly frustrating because I want to get to coding, not spend countless hours trying to figure out all this stuff my trial and error. But... hopefully I can just get through this soon to get it over with and all will be fine. =)

Share this post


Link to post
Share on other sites
Quote:
Original post by Darkware
I downloaded and unziped http://nehe.gamedev.net/data/lessons/devc/lesson01.zip then opened the project file. Under Project>ProjectOptions and in the "Further object files or linker options" place, there was nothing typed as you said. It was just blank. Also, no code appears to be visible at all either. I try to click on the lesson1.cpp link on the left where the manager colomn is, but nothing happens. I can only see code when I open the lesson1.cpp file specifically.


What the heck? How is that possible? Would you like me to send you the project I have? Maybe some freak occurance happened or something with your Dev-CPP...it is known for instability at times...Anyways, here is my project I downloaded and was able to run with no problems. Open it up and see if it works. If it does not, I would strongly suggest uninstalling your Dev-CPP and installing the newest one, even if you do have the most recent one. Good luck!

- Drew

Share this post


Link to post
Share on other sites
hey your file works.... what the heck.... why doesn't mine.... that's weird....

well... I'm going to try and figure out what exactly is going wrong here. If I figure it out, I'll post it back here.

thanks for all the help you guys!

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Quote:
Original post by Darkware
SOOOOOoooo..... I never would have guessed this to be this difficult. There are not very many documentations online that go over ALL installation setps for ALL of the files you get and tell you where EXACTLY you're supposed to place the files. This is slightly frustrating because I want to get to coding, not spend countless hours trying to figure out all this stuff my trial and error. But... hopefully I can just get through this soon to get it over with and all will be fine. =)


You are putting horse before the cart. You must understand how to do all those steps before you can start CODING. None of that stuff is very hard and if you google enough you will get ALL the info you need, so get going and LEARN the "stuff"

Share this post


Link to post
Share on other sites
Quote:
Original post by Darkware
now buy NEWEST do you mean the beta version? because I downloaded the one before that because I didn't want a beta


Ahh yes, the Beta! Not version 4. However, I am not a Dev-CPP user for the most part, so you might want to stay with what you are most comfortable with. I'm glad it works though! I can't figure out why it didn't in the first place either, but it *may* be that version of Dev, who knows.

- Drew

Share this post


Link to post
Share on other sites
Ok, well when I downloaded it, it didn't come with half the files your download file has. o.O so I dunno what the deal was...

Question: how can the cpp file be the same name as the dev project file? I try to create a new project, then save the cpp file as the same name as the dev project, but it won't let me. How is this done?

Where do you get the MakeFile.win Lesson1.o Lesson1.layout and Lesson1.~cp files? Some of them are encrypted. I tested, and you apparently need the ALL to compile the dev project or else you get errors.

How is the dev project 1.14 Kb, yet when I create a new project, it's only a few bytes? When I open the project, why can't I read the cpp code? why do I have to open the cpp separetly?

Share this post


Link to post
Share on other sites
Quote:
Original post by Darkware
Ok, well when I downloaded it, it didn't come with half the files your download file has. o.O so I dunno what the deal was...

Question: how can the cpp file be the same name as the dev project file? I try to create a new project, then save the cpp file as the same name as the dev project, but it won't let me. How is this done?

Where do you get the MakeFile.win Lesson1.o Lesson1.layout and Lesson1.~cp files? Some of them are encrypted. I tested, and you apparently need the ALL to compile the dev project or else you get errors.

How is the dev project 1.14 Kb, yet when I create a new project, it's only a few bytes? When I open the project, why can't I read the cpp code? why do I have to open the cpp separetly?


I would not strongly suggest you ditch your Dev-CPP and get the beta [grin]. Ok, this is what the deal is:

When you download the zip file, it has only has 5 files (the path is different from yours because I downloaded it a few times to make sure it was indeed valid, and it is)


Now when I open up the "lesson1.dev" file, I must comment out that GLaux line. After that I can compile and run.

When I complie, it generates temp files, namely "Lesson1.~cp" and "Lesson1.o". It is just the way Dev-CPP works. They represent the object code files and the ~.cp is a temp file.

Now I mainly suggest that you update your Dev-CPP because you are allowed to have a project named lesson1.dev then have the source file lesson1.cpp, since they are different file names (b/c of extension)

The reason my .dev file is bigger than yours [lol] is because mine has more text in it. I have the linkable libraries already listed and such so I can just ctrl+F10 and it compiles then runs.

The MakeFile.win and Lesson1.layout came with the zip file. Are you sure you are using the link you posted?

If so, upgrade the Dev, and see if your problems are solved. If you have any more questions feel free to ask.

- Drew

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
      628278
    • Total Posts
      2981789
  • Similar Content

    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
    • By test opty
      Hi,
      I'm trying to learn OpenGL through a website and have proceeded until this page of it. The output is a simple triangle. The problem is the complexity.
      I have read that page several times and tried to analyse the code but I haven't understood the code properly and completely yet. This is the code:
       
      #include <glad/glad.h> #include <GLFW/glfw3.h> #include <C:\Users\Abbasi\Desktop\std_lib_facilities_4.h> using namespace std; //****************************************************************************** void framebuffer_size_callback(GLFWwindow* window, int width, int height); void processInput(GLFWwindow *window); // settings const unsigned int SCR_WIDTH = 800; const unsigned int SCR_HEIGHT = 600; const char *vertexShaderSource = "#version 330 core\n" "layout (location = 0) in vec3 aPos;\n" "void main()\n" "{\n" " gl_Position = vec4(aPos.x, aPos.y, aPos.z, 1.0);\n" "}\0"; const char *fragmentShaderSource = "#version 330 core\n" "out vec4 FragColor;\n" "void main()\n" "{\n" " FragColor = vec4(1.0f, 0.5f, 0.2f, 1.0f);\n" "}\n\0"; //******************************* int main() { // glfw: initialize and configure // ------------------------------ glfwInit(); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); // glfw window creation GLFWwindow* window = glfwCreateWindow(SCR_WIDTH, SCR_HEIGHT, "My First Triangle", nullptr, nullptr); if (window == nullptr) { cout << "Failed to create GLFW window" << endl; glfwTerminate(); return -1; } glfwMakeContextCurrent(window); glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); // glad: load all OpenGL function pointers if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress)) { cout << "Failed to initialize GLAD" << endl; return -1; } // build and compile our shader program // vertex shader int vertexShader = glCreateShader(GL_VERTEX_SHADER); glShaderSource(vertexShader, 1, &vertexShaderSource, nullptr); glCompileShader(vertexShader); // check for shader compile errors int success; char infoLog[512]; glGetShaderiv(vertexShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(vertexShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::VERTEX::COMPILATION_FAILED\n" << infoLog << endl; } // fragment shader int fragmentShader = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(fragmentShader, 1, &fragmentShaderSource, nullptr); glCompileShader(fragmentShader); // check for shader compile errors glGetShaderiv(fragmentShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(fragmentShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::FRAGMENT::COMPILATION_FAILED\n" << infoLog << endl; } // link shaders int shaderProgram = glCreateProgram(); glAttachShader(shaderProgram, vertexShader); glAttachShader(shaderProgram, fragmentShader); glLinkProgram(shaderProgram); // check for linking errors glGetProgramiv(shaderProgram, GL_LINK_STATUS, &success); if (!success) { glGetProgramInfoLog(shaderProgram, 512, nullptr, infoLog); cout << "ERROR::SHADER::PROGRAM::LINKING_FAILED\n" << infoLog << endl; } glDeleteShader(vertexShader); glDeleteShader(fragmentShader); // set up vertex data (and buffer(s)) and configure vertex attributes float vertices[] = { -0.5f, -0.5f, 0.0f, // left 0.5f, -0.5f, 0.0f, // right 0.0f, 0.5f, 0.0f // top }; unsigned int VBO, VAO; glGenVertexArrays(1, &VAO); glGenBuffers(1, &VBO); // bind the Vertex Array Object first, then bind and set vertex buffer(s), //and then configure vertex attributes(s). glBindVertexArray(VAO); glBindBuffer(GL_ARRAY_BUFFER, VBO); glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3 * sizeof(float), (void*)0); glEnableVertexAttribArray(0); // note that this is allowed, the call to glVertexAttribPointer registered VBO // as the vertex attribute's bound vertex buffer object so afterwards we can safely unbind glBindBuffer(GL_ARRAY_BUFFER, 0); // You can unbind the VAO afterwards so other VAO calls won't accidentally // modify this VAO, but this rarely happens. Modifying other // VAOs requires a call to glBindVertexArray anyways so we generally don't unbind // VAOs (nor VBOs) when it's not directly necessary. glBindVertexArray(0); // uncomment this call to draw in wireframe polygons. //glPolygonMode(GL_FRONT_AND_BACK, GL_LINE); // render loop while (!glfwWindowShouldClose(window)) { // input // ----- processInput(window); // render // ------ glClearColor(0.2f, 0.3f, 0.3f, 1.0f); glClear(GL_COLOR_BUFFER_BIT); // draw our first triangle glUseProgram(shaderProgram); glBindVertexArray(VAO); // seeing as we only have a single VAO there's no need to // bind it every time, but we'll do so to keep things a bit more organized glDrawArrays(GL_TRIANGLES, 0, 3); // glBindVertexArray(0); // no need to unbind it every time // glfw: swap buffers and poll IO events (keys pressed/released, mouse moved etc.) glfwSwapBuffers(window); glfwPollEvents(); } // optional: de-allocate all resources once they've outlived their purpose: glDeleteVertexArrays(1, &VAO); glDeleteBuffers(1, &VBO); // glfw: terminate, clearing all previously allocated GLFW resources. glfwTerminate(); return 0; } //************************************************** // process all input: query GLFW whether relevant keys are pressed/released // this frame and react accordingly void processInput(GLFWwindow *window) { if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS) glfwSetWindowShouldClose(window, true); } //******************************************************************** // glfw: whenever the window size changed (by OS or user resize) this callback function executes void framebuffer_size_callback(GLFWwindow* window, int width, int height) { // make sure the viewport matches the new window dimensions; note that width and // height will be significantly larger than specified on retina displays. glViewport(0, 0, width, height); } As you see, about 200 lines of complicated code only for a simple triangle. 
      I don't know what parts are necessary for that output. And also, what the correct order of instructions for such an output or programs is, generally. That start point is too complex for a beginner of OpenGL like me and I don't know how to make the issue solved. What are your ideas please? What is the way to figure both the code and the whole program out correctly please?
      I wish I'd read a reference that would teach me OpenGL through a step-by-step method. 
  • Popular Now