dll + application

[fpujol]

Hello,

I compiled my library as staticlib and the application don't have problems runs all rigth with Q_OBJECT defined, but what that's mean ? with static lib runs ok, this mean that all is exported all rigth. This problem tells me that precomipiled binaries 4.2.2 for windows are working in static ? I'm confused in some concepts, why not in dynamic ?

[fullmetalcoder]

Honestly your project file does not help much, especially because it is only a subdir wrapper. What would be interesting is a minimum compilable example reproducing the bug you're facing.

I compiled my library as staticlib and the application don't have problems

Didn't you previously said that YOUR library had been compiled as dll (shared library)??? The notion of exporting symbols is something that is very specific because AFAIk it is required only under Window$ with SHARED libraries... Thus, a static version compiling/linking/running fine does not imply that a shared one will do the same under Window$... Exporting/importing under Qt is done through two macros Q_DECL_EXPORT and Q_DECL_IMPORT which are often wrapped by another macro for more ease of use :

#ifdef _BUILD_MY_LIB_
#if defined(QT_DLL) || defined(QT_SHARED)
#define MYLIB_EXPORT Q_DECL_EXPORT
#endif
#else
#define MYLIB_EXPORT Q_DECL_IMPORT
#endif

#ifdef _BUILD_MY_LIB_
#if defined(QT_DLL) || defined(QT_SHARED)
#define MYLIB_EXPORT Q_DECL_EXPORT
#endif
#else
#define MYLIB_EXPORT Q_DECL_IMPORT
#endif

To copy to clipboard, switch view to plain text mode 

Then definitions of classes/functions to export should be prefixed with th MYLIB_EXPORT macro (or whatever you called it of course) as follows :

class MYLIB_EXPORT SomeClass {};
 
MYLIB_EXPORT void someFunction();

class MYLIB_EXPORT SomeClass {};

MYLIB_EXPORT void someFunction();

To copy to clipboard, switch view to plain text mode 

Hope this helps.