Qt-jambi-interest Archive, October 2007
Debug vs. release
Message 1 in thread
Hi!
I followed the instructions on qtjambi-installation.html and ended up a
set of lib/*debuglib.so.* files. Applications refused to start until I
created symlinks from files without the "debuglib" prefix. Noticed the
loading error when running with -Dcom.trolltech.com.qt.verbose-loading.
What's up here? I saw some debug vs. release magic in the java.pro file
would have expected to get a working installation independant of my Qt
build which had been configured with -debug.
Harri.
Message 2 in thread
Harri Porten wrote:
> Hi!
>
> I followed the instructions on qtjambi-installation.html and ended up
> a set of lib/*debuglib.so.* files. Applications refused to start until
> I created symlinks from files without the "debuglib" prefix. Noticed
> the loading error when running with
> -Dcom.trolltech.com.qt.verbose-loading.
>
> What's up here? I saw some debug vs. release magic in the java.pro
> file would have expected to get a working installation independant of
> my Qt build which had been configured with -debug.
Hi, Harri.
The Qt Jambi build follows the configuration of Qt, so if Qt is
configured in debug, then you will get debug libraries in Qt Jambi as well.
In order to run Qt Jambi in debug mode, pass the following argument to
your JVM when starting the application:
-Dcom.trolltech.qt.debug=true
This will make sure Qt Jambi loads the correct libraries.
We'll update the build instructions to include this information.
-- Eskil
