|
Hello there! We work here with an SmartPhone application that used to use WengoPhone libraries for Voip infraestructure. Now we are migrating to up-to-date "qutecom-2-2-RC3" codes version. Our project have a main DLL library that links with all Wengo libraries built statically. In order to maintain this approach, I changed the configuration of "pthread" project to create a static library (.lib file) that will be linked to our main DLL, but on first tests I've faced a crash at line 75 from method "ptw32_mutex_check_need_init" of file "ptw32_mutex_check_need_init". It seems that when this project is compiled to generate a DLL, some initialization methods are triggered by Windows DLL callback functions when new processes and/or thread are attached to it. I found these methods implemented on file "dll.c" of this project. Now the question is. Considering that I still preffer to generate a static pthread library, how should I handle these initializations to don't get the crash like now ? Obs.: I'm using the following preprocessors during the library compilation = "__CLEANUP_C;WIN32;_DEBUG;_WINDOWS;WIN32_WINNT=0x400;PTW32_BUILD_INLINED;PTW32_STATIC_LIB;". Has anyone done this before ? Am I informing wrong definitions on my project ? Should I use the main DLL Windows callback functions on the same way it would happen if "pthread" generated binary was a DLL ? Should I use other initialization routines on this case ? Thanks and best regards, --
|
_______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
