Using an existing DLL/Lib with Qt

loladiro

I think your understanding is generally right. I usually prefer to use headers declaring the prototypes over dynamic runtime loading (e.g. through QLibrary). This is of course easiest if you have the header files provided by the author of the library you want to use.

matthazley

Yeah - I figured since I had the C++ prototypes I wouldnt have to worry about Dynamic runtime loading. Tell me - do you just include the library in the .pro file?

Something like - win32:LIBS += path/to/myLib.lib

I'll give it a shot - better to experiment and learn!

loladiro

You still have the choice between dynamic and static linkage to your application (static is the .lib file, dynamic the .dll file). If you use static linking the file will be part of your app and you do not have to deploy additional files as you would with the dynamic lib (although you probably link Qt dynamically anyway, so you are probably familiar with that). If it is a popular library or if there are license issues (e.g. the library is LGPL) I would suggest you use dynamic linking otherwise static should be fine to.

romankr

you should

add to *.pro file something like that
@LIBS += d:/test/lib/somelib.lib@
add to *.cpp
@QLibrary library("somelib");
library.load();@

loladiro

A .lib file is a static library, you cannot use QLibrary to access it.

tobias.hunger

I would use normal linking instead of QLibrary. That is way more straight forward as your OS will handle all the error cases even before your application starts. QLibrary only makes sense if you need to have an optional dependency on some libary I think.

Plus your pro file should already link against somelib with the LIBS line, so you actually do not need to load it again using QLibrary... Use depends.exe (available somewhere on the microsoft website) to check the executable:-)

ludde

Some confusion here... On Windows, you always link against a .lib file, even if the library itself is in a DLL. What you normally have to do to use an external library, on any platform, is:

Add the library to the LIBS variable in your .pro file:
@LIBS += -llibrary@
Add the library path to the LIBS variables in your .pro file:
@LIBS += -LC:/path/to/library@
Add the include path to the INCLUDEPATH variable in your .pro file:
@INCLUDEPATH += C:/path/to/includes@

Then, if the library is a DLL, you must make sure the DLL is found when you run the program. On Windows you can e.g. add it the same directory as your executable. If you run the application from Qt Creator, it seems to be able to locate the DLL itself (if it's in the same place as the .lib file, I would guess).

matthazley

Thanks guys - all solid info!

goetz

[quote author="Tobias Hunger" date="1308582243"]Use depends.exe (available somewhere on the microsoft website) to check the executable:-)[/quote]

It's available on http://www.dependencywalker.com/ nowadays.

loladiro

[quote author="ludde" date="1308583463"]Some confusion here... On Windows, you always link against a .lib file, even if the library itself is in a DLL.
[/quote]

I never had to link .lib files (neither did I encounter them in my day-to-day development on windows). However I use MinGW. Is this different for MSVC?

EDIT: ok, I figured it out. The .lib extension is used for both, static libraries and import libraries. MinGw can link against dlls and (usually) doesn't need import libraries while MSVC apparently does.

jim_kaiser

@ludde: +1

Just to clear it up.. You can choose to link statically or dynamically, statically meaning the library is bundled along with your app, dynamic uses a dll. Now, if you have a .lib and a .dll, you have a library made to be used dynamically. You cannot use that .lib file statically, the static .lib is generally named (<somename>_a.lib), is of a bigger size than the .lib in the case of dynamic libraries. This is because the static .lib has to contain all the implementation, while in the dynamic .lib, you only have the exported symbols, and the actual implementation is in the dll.

@matthazley: You have a .lib and .dll but do you also have the header files (.h).. that is the general way to link to a library. You include the header in your code and use the methods. Compile with linking to the .lib. At runtime this loads the dll which has the implementation. Refer to @ludde for the definitions in the pro file.

matthazley

Cheers Jim.