MinGW and auto-import (what causes it?)
Like so many before me, I have been writing with a small game library. It works fine, but when I link to it during the compilation of a demo game, I get this message:
Here is the call in the executable that seems to dictate whether the message appears or not:
The camera is a class in the DLL, and it contains this method.
The whole project compiles and executes just fine, but that auto-import message is probably going to drive me insane. I checked out the linker's man page, but I did not understand the information there. Could you perhaps help me understand what is causing this message to occur? The code seems quite boring and normal to me, which is why it is bothering me so much. Did I do something crazy to cause this?
| Info: resolving vtable for Matrix4x4by linking to __imp___ZTV9Matrix4x4 (auto-import) C:\dev\apps\mingw\bin\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe: warning: auto-importing has been activated without --enable-auto-import specified on the command line. This should work unless it involves constant data structures referencing symbols from auto-imported DLLs. |
Here is the call in the executable that seems to dictate whether the message appears or not:
|
|
The camera is a class in the DLL, and it contains this method.
|
|
The whole project compiles and executes just fine, but that auto-import message is probably going to drive me insane. I checked out the linker's man page, but I did not understand the information there. Could you perhaps help me understand what is causing this message to occur? The code seems quite boring and normal to me, which is why it is bothering me so much. Did I do something crazy to cause this?
Topic archived. No new replies allowed.