zoukankan      html  css  js  c++  java
  • opengl在vs2010中运行问题解决

    http://www.cppblog.com/guojingjia2006/archive/2009/01/08/68874.html

    OpenGL vs2010中碰到的配置问题,网上找了下,以下和我碰到的一样,可以解决,感谢作者
    unresolved external symbol __imp____glutInitWithExit@12 unresolved external symbol __imp____glutCreateWindowWithExit@8


    I have the folling files in the following locations: -

    glut.h
    glu.h
    gl.h
    C:\Program Files\Microsoft Visual Studio 8\VC\include\GL

    glut.32.lib
    C:\Program Files\Microsoft Visual Studio 8\VC\lib

    glut32.dll
    glu32.gll
    C:\WINDOWS\system32


    I make a new project (Win32 Console App).
    Set the Additional Dependencies under
    Project | Properties | Config Properties | Linker | Input
    I have: -
    opengl32.lib glu32.lib glut32.lib

    This is basically what just about every site I look at tells me to do.
    So I copy over some code that I know compiles and runs under my Dev C++ setup...
    And it fails to compile with the following errors: -
    1>main.obj : error LNK2019: unresolved external symbol __imp____glutInitWithExit@12 referenced in function _glutInit_ATEXIT_HACK@8

    1>main.obj : error LNK2019: unresolved external symbol __imp____glutCreateWindowWithExit@8 referenced in function _glutCreateWindow_ATEXIT_HACK@4


    This is didn't happen a little while ago, as I was trying to solve a previous problem. This was that when I tried to run a successfully compiled program, an error would say: -
    The procedure entry point __glutInitWithExit could not be located in the dynamic link library glut32.dll


    solution:

    Try define the following line right before including the header, glut.h.

    #define GLUT_DISABLE_ATEXIT_HACK

    为什么出现这个错误,这是我在网站上找到的原因,和大家分享一下:

    Win32 has an annoying issue where there are multiple C run-time
    libraries (CRTs). If the executable is linked with a different CRT
    from the GLUT DLL, the GLUT DLL will not share the same CRT static
    data seen by the executable. In particular, atexit callbacks registered
    in the executable will not be called if GLUT calls its (different)
    exit routine). GLUT is typically built with the
    "/MD" option (the CRT with multithreading DLL support), but the Visual
    C++ linker default is "/ML" (the single threaded CRT).
    One workaround to this issue is requiring users to always link with
    the same CRT as GLUT is compiled with. That requires users supply a
    non-standard option. GLUT 3.7 has its own built-in workaround where
    the executable's "exit" function pointer is covertly passed to GLUT.
    GLUT then calls the executable's exit function pointer to ensure that
    any "atexit" calls registered by the application are called if GLUT
    needs to exit.

    Note that the __glut*WithExit routines should NEVER be called directly.
    To avoid the atexit workaround, #define GLUT_DISABLE_ATEXIT_HACK. */



    --------------------------------------------------------------------天道酬勤!
  • 相关阅读:
    飞腾2000+上面银河麒麟v10 安装virt-manager创建虚拟机的操作过程
    postgresql重置序列起始值
    行为链分析zipkin
    Elasticsearch冷热分离原理和实践
    Window 各个版本对应的版本号大全
    为何fdisk和df 输出的信息不一致?
    Java使用ConcurrentHashMap实现简单的内存式缓存
    Linux系统中如何查找大文件或文件夹的方法
    Class.newInstance()与Constructor.newInstance()创建对象
    Wazuh完整性监测和命令监测注册表并邮件告警
  • 原文地址:https://www.cnblogs.com/graph/p/2215991.html
Copyright © 2011-2022 走看看