I installed glew, glfw and glm in eclipse cdt(c++) with the gcc/mingw, all statically.
All works fine, but I don't like the warning in the output console of eclipse:
Warning: corrupt .drectve at end of def file
How I can fix and hide this warning ?
What does it mean ?
And what I noticed is, that this warning comes only, if I call the 'glewInit' function.
When I ran into this problem it was because I was linking against incompatible MSVC libs. A comment by keltar helped me through this problem.
SDL 2.0: linking error
The message
Warning: corrupt .drectve at end of def file
could also mean, that the project is being built with MinGW but the library it uses is created for Visual Studio.
MinGW and Visual Studio builds are not interchangeable.
I had this error in CLion for MinGW toolchain, but when I switched to VisualStudio toolchain, it disappeared.
Related
I have the following problem: I have a library, let's call it library.lib that is written in VS C++ 2005. In VS 2017 I've got the following error when compiling:
LINK : fatal error C1047: The object or library file 'library.lib' was created with an older compiler than other objects; rebuild old objects and libraries
Could you help me to solve it? Possibly I have to run VS 2005. However, I cannot install it. I have Windows 10 and the installer does not work.
Pol
is there anybody here, who might help, the project cannot wait?
I just brought a project I was working on from linux with cmake and g++ to windows visual studio. I just copied the source files and did some changes to the code to fit windows and got the code to compile on windows. My problem is that when I try to run it it gives me missing dll run time errors. At first it gave me libgmp-10.dll missing which seems to be for minGW or gcc. I downloaded that one and put it besides my executable. Now it says libgcc_s_dw2-1.dll is missing. Aren't these dlls for gcc? Shouldn't visual studio not need these?
Check with liner->input options. It might be referring to .libs of these dlls. Replace them with windows equivalents.
I installed glew, glfw and glm in eclipse cdt(c++) with the gcc/mingw, all statically.
All works fine, but I don't like the warning in the output console of eclipse:
Warning: corrupt .drectve at end of def file
How I can fix and hide this warning ?
What does it mean ?
And what I noticed is, that this warning comes only, if I call the 'glewInit' function.
When I ran into this problem it was because I was linking against incompatible MSVC libs. A comment by keltar helped me through this problem.
SDL 2.0: linking error
The message
Warning: corrupt .drectve at end of def file
could also mean, that the project is being built with MinGW but the library it uses is created for Visual Studio.
MinGW and Visual Studio builds are not interchangeable.
I had this error in CLion for MinGW toolchain, but when I switched to VisualStudio toolchain, it disappeared.
I am using the VS 2012, and when I am compiling my project in debug mode, there are no errors. but while trying to compile the project in release mode I get the next error message (Error C1047) :
fatal error C1047: The object or library file 'file.lib' was created with an older compiler than other objects; rebuild old objects and libraries
I understood that the older versions of VS has a SP1 install that solves this issue, but can't find a solution to this issue.
Did anybody saw this and knows how to solve it?
If you are using libraries built from different compiler, you need to recompile those libraries in VS2012.
I am running VS2010 Express for C++ on Windows 7.
Everything was compiling and linking fine until the latest round of updates.
Now I get a series of link warnings of the form:
libcpmt.lib(xgetwctype.obj) : warning LNK4099: PDB 'libcpmt.pdb' was not found with 'libcpmt.lib(xgetwctype.obj)'
libcpmt.lib & libcpmt.pdb are in in the Visual Studio lib directory, so I can only speculate that there is some type of path problem. Has anybody else had/solved this problem?
I solved this problem by reinstalling VS2010 and then applying the service pack again.
I assume that it is better to install VS2010 after the initial onslaught of newly installed Windows 7 updates.