Anybody interested in patching a few bugs? The most serious 3.5.12 bugs affecting me are limited to kdelibs/kdebase. I would backport the patches to 3.5.12 and rebuild to test.
Here is a short list of bugs that affect me.
293, Kde-config Incorrectly Creates a Profile Folder in the System root directory
385, Unmounted removable device icons do not appear on the desktop
387, Kicker/Panel Clock Font Display Looks Weird
388, KDESU Dialog Box Behavior
393, Incorrect kdesu Behavior When Opening Kate
394, Problems with DCOP After Using kdesu
427, NumLock light does not reflect actual state
I use kdesu a lot. Those bugs are especially hindering.
Please let me know. I'll test any patches immediately.
Thanks everybody for your devotion and work.
Darrell
One way to learn about Cmake is starting from scratch.
So I started with kdeadmin, it didn't look like to big a project.
Nothing like getting your feet wet by jumping in at the deep end. :-D
The trouble is the water is above my head. :-(
I have spent many hours on this one.
A pointer in the right direction would be appreciated.
[ 29%] Building CXX object ksysv/CMakeFiles/ksysv.dir/OldView.cpp.o
/home/castro/Work/trinity-build/trinity-kdeadmin/src/kdeadmin/ksysv/OldView.cpp:22:20:
fatal error: config.h: No such file or directory
compilation terminated.
make[2]: *** [ksysv/CMakeFiles/ksysv.dir/OldView.cpp.o] Error 1
make[1]: *** [ksysv/CMakeFiles/ksysv.dir/all] Error 2
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
[castro@castro2 trinity-kdeadmin]$
Castro.
Tim, Serghei,
I know you both are working hard, but would one of you please provide an estimated date when the porting to cmake will be complete for all Trinity packages?
Thanks.
Darrell
Hi all,
We will have a meeting on 19 April 2011. Raindate has been set for 20
April 2011.
Topic discussion is currently going on in Etherpad:
http://trinity.etherpad.trinitydesktop.org/19
Scheduling has started, so that people may be able to attend (advance notice).
There are 6 times available. Please mark your selection:
http://www.doodle.com/eivtcn5c3wndqt2u
--
later, Robert Xu
Hi serghei,
Hi all,
This is my second day of learning about cmake.
You may find these changes more to your acceptable than my first
attempt. :-)
See mods-kdebase.tar.bz2
Castro.
Hello,
tqtinterface build system was massively reworked.
Available options:
QT_VERSION=3
or
USE_QT3 - activate Qt3 support
--------------------
QT_VERSION=4
or
USE_QT4 - activate Qt4 support
--------------------
QT_PREFIX_DIR - the place where qt is installed
default: /usr
For Qt3, QT_VERSION inherits QTDIR, _if_ QTDIR environment variable is set.
--------------------
QT_INCLUDE_DIR - the place where qt headers are installed
default: ${QT_PREFIX_DIR}/include/qt${QT_VERSION}
--------------------
QT_LIBRARY_DIR - the place of qt libraries
default: ${QT_PREFIX_DIR}/lib${LIB_SUFFIX}
For Qt4, libQtGui.so presence is checked, if is not exists in
${QT_PREFIX_DIR}/lib${LIB_SUFFIX}, ${QT_PREFIX_DIR}/lib${LIB_SUFFIX}/qt4 is
checked as well
--------------------
QT_LIBRARIES - list of qt libraries required for linking
Default for Qt3 - qt-mt
Default for Qt4 - QtCore QtGui
--------------------
QT_BINARY_DIR - the place where qt tools are installed (moc and uic)
default: ${QT_PREFIX_DIR}/bin
--------------------
MOC_EXECUTABLE - absolute path to moc
default: ${QT_BINARY_DIR}/moc
--------------------
UIC_EXECUTABLE - absolute path to uic
default: ${QT_BINARY_DIR}/uic
--------------------
Note: PKGCONFIG_INSTALL_DIR is defaulted to /usr/lib${LIB_SUFFIX}/pkgconfig,
to avoid tqt detection problems.
Note: these options are available only for tqtinterface, the rest of packages
inherits it automatically from tqt (for example, you do not need to pass
argument QT_VERSION=3 to kdelibs' cmake).
--
Serghei
This is what I found when debugging Cmake problems when building kdebase.
[castro@castro2 kdebase]$ grep -r "WITH_XCOMPOSITE" *
CMakeLists.txt:option( WITH_XCOMPOSITE "Enable xcomposite support" OFF )
**** kicker/taskmanager compiles OK with or without XCOMPOSITE.
kicker/taskmanager/CMakeLists.txt:if( WITH_XCOMPOSITE )
kicker/taskmanager/CMakeLists.txt:endif( WITH_XCOMPOSITE )
**** kwin/kompmgr does not compile with or without XCOMPOSITE.
Looking into kompmgr.c shows that it requires XCOMPOSITE
#include <X11/extensions/Xcomposite.h>
#include <X11/extensions/Xdamage.h>
#include <X11/extensions/Xrender.h>
#include <X11/extensions/shape.h>
The question is should we have the option (WITH_XCOMPOSITE) in
kompmgr/CMakeLists.txt.
kwin/kompmgr/CMakeLists.txt:if( WITH_XCOMPOSITE )
kwin/kompmgr/CMakeLists.txt:endif( WITH_XCOMPOSITE )
If the answer is YES then should try and build it?
Looking into kwin/kompmgr/configure.in.in
if test "x$with_composite" != "xno"; then
KDE_CHECK_HEADERS(X11/extensions/Xdamage.h,,compile_kompmgr=no,[#include
<X11/Xlib.h>])
KDE_CHECK_HEADERS(X11/extensions/Xcomposite.h,,compile_kompmgr=no,[#include
<X11/Xlib.h>])
KDE_CHECK_HEADERS(X11/extensions/Xrender.h,,compile_kompmgr=no,[#include
<X11/Xlib.h>])
else
compile_kompmgr=no
fi
it shows us that we should NOT build it.
kwin/CMakeLists.txt: if( WITH_XCOMPOSITE )
add_subdirectory( kompmgr )
kwin/CMakeLists.txt: endif( WITH_XCOMPOSITE )
[castro@castro2 kdebase]$
The changes I have made to kwin/kompmgr/CMakeLists.txt are quick & dirty,
but it works for now.
I will put some more thought to it in the next few days.
Castro.