should I add the CPP files into *.pro when I trying to load the DLL

Question

I need to compile some source code into a DLL, and load it in other project. I have an entry called

extern "C" LTCPOS_LSHARED_EXPORT tcpClient_Os* getClientInst(VhostInfo hostInfo, CtcpOpt *tcpOpt, QObject *parent = 0);

The type of "tcpClient_OS" is a self-defined class. When I load the DLL using QLibrary in a different project it appears that I must add the source file (cpp files) into the *.pro in order to make the project compiled without errors. Why?

What is the normal routine of building a DLL with a function returning self-defined class pointer and how do I load it?

AbdElRaheim AbdElRaheim · Accepted Answer · 2012-10-30T11:03:13

Not to familiar with building qt stuff but in windows we normally need a lib and some header files to call something in another dll. We also have LoadLibrary, GetProcAddress for executing stuff that is not known at compile time.

It looks like it is very similar building qt stuff. Compile your dll, it addition to the dll itself it should produce a lib. In proj config for referencing project need a LIBS += with path to the lib.

Here is a link I found on QLibrary which is an abstraction for Windows LoadLibrary/GetProcAddress and dlopen/dlsym http://tufangorel.blogspot.com/2011/11/call-symbol-from-shared-object-file-dll-with-qlibrary.html

should I add the CPP files into *.pro when I trying to load the DLL

1 Answers