Now I am not sure any more if MinGW creates a lib file as well, but I think it should. (so that other windows compilers will be able to links against the lib), but as I said, I am not sure any more (it has bin a while since I compiled a lib with MinGW under windows)There's a .a file and then there's the .dll
So I just checked a bit here:
So if you are using MinGW, it actually link against the DLL it self, as stated here.Building the DLL
To build the DLL use the following commands:
g++ -c -DBUILDING_EXAMPLE_DLL example_dll.cpp
g++ -shared -o example_dll.dll example_dll.o -Wl,--out-implib,libexample_dll.a
The -DBUILDING_EXAMPLE_DLL compiler option causes the DLL's functions to be declared as "dllexport", meaning that they will be "exported" from the DLL and available to client applications. The "-shared" option tells the linker to create a DLL instead of an .exe, and the "--out-implib" linker option causes an import library to be created, which is used later on.
Note:
The import library created by the "--out-implib" linker option is required iff (==if and only if) the DLL shall be interfaced from some C/C++ compiler other than the MinGW toolchain. The MinGW toolchain is perfectly happy to directly link against the created DLL. More details can be found in the ld info files that are part of the binutils package (which is a part of the toolchain).
So my guess is that you probably have a problem with paths somewhere or the like.
EDIT: it just occured to me that you LIBS tag in the pro file was wrong:
LIBS += -LD:\Anthony\Progs\Qt\plugins\designer\ -lPokerTableInfoPlugin
Bookmarks