Solved Map of Class Names onto Implementing Libraries
-
I'm porting an existing application to 64 bit Windows. The application was last built using QT 4.5 under Visual Studio 2005. I am building it under Visual Studio 2013 using QT 5.6.
I am not familiar with QT and I need to get this project done. I am looking for a list that maps QT classes, such as QFont, onto the implementing library so that I can add that library to my library list. QFont is a specific example, but I need this solution for the general case.
If such a document does not exist, then how would you solve his problem other than dumping the contents of the existing libraries and searching them?
This seems like a common problem, yet I could not find the solution in the forums.
Ideally, the QT class documentation would contain a reference to the implementing debug and non-debug libraries.
Thank you in advance.
-
Hi and welcome to devnet,
The first step is basically to add
QT += widgets
in your .pro file and the removed all module prefix from your includes. i.e.#include <QtGui/QWidget> => #include <QWidget>
Hope it helps
-
@Carey-Gister said:
I am not familiar with QT and I need to get this project done. I am looking for a list that maps QT classes, such as QFont, onto the implementing library so that I can add that library to my library list. QFont is a specific example, but I need this solution for the general case.
I don't understand the question. Are you looking in which module the class is defined? If so, the documentation provides that (e.g. for QFont)
QT += gui
So the class is in the
gui
module -Qt5Gui.dll
.Ideally, the QT class documentation would contain a reference to the implementing debug and non-debug libraries.
There's a difference only for windows. On linux the debug and release libraries are actually compatible and can be used interchangeably. For me they just reside in different folders. On windows the debug libraries have
d
suffix to them, soQt5Guid.dll
would be the debug version ofQt5Gui.dll
.Kind regards.
-
Yes, that answers the question. I was not aware that the qmake QT += X syntax specified the containing library.