[Digikam-devel] [Bug 160966] some searches don't work properly with the new sqlite3-3.5.8

Gilles Caulier caulier.gilles at gmail.com
Mon Apr 28 06:55:26 BST 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=160966         




------- Additional Comments From caulier.gilles gmail com  2008-04-28 07:55 -------
Andi,

Your report #36 is very important.

It's certainly a specific part on digiKam core which failded if no debug options is used to compile digiKam.

Note : no debug option is the same way than to not use ".configure --enable-final". This mode is used to generate final package without debug info and with full optimization.

In KDE3 with autotools, there is a macro to disable optimizations to a specific folder to compile : KDE_OPTIONS = nofinal. It's used for ex. in digikam/libs/jpegutils/Makefile.am with transupp.cpp code which do not support compilation optimizations.

I recommend you to make investiguations where code failed exactly. Certainly in DB interface which is mixed indeep in digikam/digikam folder with GUI (code is separated in KDE4). Just place the KDE macro to the digikam/digikam/Makefile.am and check if it work...

Arnd,

yes, i suspect than #156146 has the same problem.

Marcel, if you have any tips here...

Gilles Caulier



More information about the Digikam-devel mailing list