* Again, it's bad idea to randomly disable some logging sources based on
obscure compile-time defines (QT_DEBUG is not mentioned in qte-2.3.10, so
how could it get such name at all?). OE OPIE is going to have logging facility
helping to resolve issues, not obfuscate them.
--- /dev/null
+--- library/qpeapplication.cpp.org 2007-01-24 19:54:07.000000000 +0000
++++ library/qpeapplication.cpp 2007-05-03 03:34:10.000000000 +0000
+@@ -792,14 +792,14 @@
+ {
+ switch ( type ) {
+ case QtDebugMsg:
+-#ifdef QT_DEBUG
++//#ifdef QT_DEBUG
+ fprintf( stderr, "Debug: %s\n", msg );
+-#endif
++//#endif
+ break;
+ case QtWarningMsg:
+-#ifdef QT_DEBUG
++//#ifdef QT_DEBUG
+ fprintf( stderr, "Warning: %s\n", msg );
+-#endif
++//#endif
+ break;
+ case QtFatalMsg:
+ fprintf( stderr, "Fatal: %s\n", msg );
require ${PN}.inc
PV = "1.2.2+cvs${SRCDATE}"
-PR = "r7"
+PR = "r8"
SRC_URI = "${HANDHELDS_CVS};module=opie/library \
- file://fix-titleheight.patch;patch=1"
+ file://fix-titleheight.patch;patch=1 \
+ file://unbreak-logging.patch;patch=1 \
+ "