compiling CloudCompare in debug mode
Posted: Thu Aug 18, 2016 2:39 pm
hello,when I compile cc in debug mode,It occurs some problem such as:
93 IntelliSense: "void (*)(GLenum source, GLenum type, GLuint id, GLenum severity, GLsizei length, const GLchar *message, GLvoid *userParam)" 类型的实参与 "GLDEBUGPROC" 类型的形参不兼容 e:\study\project\trunk-2.6.2\trunk-2.6.2\libs\qCC_glWindow\ccGLWindow.cpp 605 26 QCC_GL_LIB
错误 65 error LNK1104: 无法打开文件“..\libs\qCC_glWindow\Debug\QCC_GL_LIBd.lib” E:\study\project\trunk-2.6.2\cmake\ccViewer\LINK ccViewer
错误 92 error LNK1104: 无法打开文件“..\libs\qCC_glWindow\Debug\QCC_GL_LIBd.lib” E:\study\project\trunk-2.6.2\cmake\qCC\LINK CloudCompare
错误 32 error C2664: “void (GLDEBUGPROC,void *)”: 无法将参数 1 从“void (__cdecl *)(GLenum,GLenum,GLuint,GLenum,GLsizei,const GLchar *,GLvoid *)”转换为“GLDEBUGPROC” E:\study\project\trunk-2.6.2\trunk-2.6.2\libs\qCC_glWindow\ccGLWindow.cpp 605 1 QCC_GL_LIB
my software version is:VS2013+QT5.4+CMAKE3.4+trunk2.6.2
but there is no problem when I compile in release mode;
there is either noproblem when i compile trunk2.7 in the same condition.
how can i correct this problem!
93 IntelliSense: "void (*)(GLenum source, GLenum type, GLuint id, GLenum severity, GLsizei length, const GLchar *message, GLvoid *userParam)" 类型的实参与 "GLDEBUGPROC" 类型的形参不兼容 e:\study\project\trunk-2.6.2\trunk-2.6.2\libs\qCC_glWindow\ccGLWindow.cpp 605 26 QCC_GL_LIB
错误 65 error LNK1104: 无法打开文件“..\libs\qCC_glWindow\Debug\QCC_GL_LIBd.lib” E:\study\project\trunk-2.6.2\cmake\ccViewer\LINK ccViewer
错误 92 error LNK1104: 无法打开文件“..\libs\qCC_glWindow\Debug\QCC_GL_LIBd.lib” E:\study\project\trunk-2.6.2\cmake\qCC\LINK CloudCompare
错误 32 error C2664: “void (GLDEBUGPROC,void *)”: 无法将参数 1 从“void (__cdecl *)(GLenum,GLenum,GLuint,GLenum,GLsizei,const GLchar *,GLvoid *)”转换为“GLDEBUGPROC” E:\study\project\trunk-2.6.2\trunk-2.6.2\libs\qCC_glWindow\ccGLWindow.cpp 605 1 QCC_GL_LIB
my software version is:VS2013+QT5.4+CMAKE3.4+trunk2.6.2
but there is no problem when I compile in release mode;
there is either noproblem when i compile trunk2.7 in the same condition.
how can i correct this problem!