tde-devels

devels@trinitydesktop.org

3 participants
3807 discussions

kdebase/kwin/kompmgr
by Castro 30 Mar '11

30 Mar '11

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.

3 8

tqtinterface build system
by Serghei Amelian 30 Mar '11

30 Mar '11

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

2 2

tqtinterface 3.5.12 Fails to build
by Darrell Anderson 30 Mar '11

30 Mar '11

I successfully built KDE 3.5.10 on Slackware 13.1, including many of extra apps. There were quite a few patches I had to find and apply. I'll submit any of those patches not yet merged into Trinity. I also can build all of Trinity 3.5.12 on Slackware 12.2. With that under me I started to build Trinity 3.5.12 on Slackware 13.1. I got qt3, qca, qca-tls, dbus-qt3 built and installed and poppler rebuilt to support qt3. Then tqtinterface wouldn't build: ==================================== /bin/sh ../libtool --tag=CXX --mode=link g++ -O2 -march=i486 -mtune=i686 -version-info 6:0:2 -no-undefined -o libtqt.la -rpath /usr/lib tqt.lo tqaccel.lo tqaccessible.lo tqaction.lo tqapplication.lo tqasyncio.lo tqbuttongroup.lo tqbutton.lo tqcanvas.lo tqcdestyle.lo tqcheckbox.lo tqclipboard.lo tqcolordialog.lo tqcombobox.lo tqcommonstyle.lo tqdatabrowser.lo tqdatatable.lo tqdataview.lo tqdatetimeedit.lo tqdesktopwidget.lo tqdial.lo tqdialog.lo tqdns.lo tqdockarea.lo tqdockwindow.lo tqdragobject.lo tqerrormessage.lo tqeventloop.lo tqframe.lo tqftp.lo tqfiledialog.lo tqfontdialog.lo tqgl.lo tqgplugin.lo tqgrid.lo tqgridview.lo tqgroupbox.lo tqguardedptr.lo tqhbox.lo tqhbuttongroup.lo tqheader.lo tqhgroupbox.lo tqhttp.lo tqiconview.lo tqimageformatplugin.lo tqinputcontext.lo tqinputdialog.lo tqlabel.lo tqlayout.lo tqlcdnumber.lo tqlineedit.lo tqlistbox.lo tqlistview.lo tqlocalfs.lo tqmainwindow.lo tqmenubar.lo tqmessagebox.lo tqmotifplusstyle.lo tqmotifstyle.lo tqmultilineedit.lo tqnetworkprotocol.lo tqnp.lo tqobjectcleanuphandler.lo tqobject.lo tqplatinumstyle.lo tqpopupmenu.lo tqprintdialog.lo tqprocess.lo tqprogressbar.lo tqprogressdialog.lo tqpushbutton.lo tqradiobutton.lo tqrangecontrol.lo tqscrollbar.lo tqscrollview.lo tqsemimodal.lo tqserversocket.lo tqsessionmanager.lo tqsgistyle.lo tqsignal.lo tqsignalmapper.lo tqsizegrip.lo tqslider.lo tqsocket.lo tqsocketnotifier.lo tqsound.lo tqspinbox.lo tqsplashscreen.lo tqsplitter.lo tqsqldatabase.lo tqsqldriver.lo tqsqldriverplugin.lo tqsqlform.lo tqsqlquery.lo tqstatusbar.lo tqstyle.lo tqstyleplugin.lo tqstylesheet.lo tqtabbar.lo tqtabdialog.lo tqtable.lo tqtabwidget.lo tqtextbrowser.lo tqtextcodecplugin.lo tqtextedit.lo tqtextview.lo tqtimer.lo tqtoolbar.lo tqtoolbox.lo tqtoolbutton.lo tqtooltip.lo tqtranslator.lo tqurloperator.lo tqvalidator.lo tqvbox.lo tqvbuttongroup.lo tqvgroupbox.lo tqwidget.lo tqwidgetplugin.lo tqwidgetstack.lo tqwindowsstyle.lo tqwizard.lo tqworkspace.lo tq1xcompatibility.lo tqabstractlayout.lo tqasciicache.lo tqasciidict.lo tqasyncimageio.lo tqbig5codec.lo tqbitarray.lo tqbitmap.lo tqbrush.lo tqbuffer.lo tqcache.lo tqcleanuphandler.lo tqcolor.lo tqcompactstyle.lo tqconnection.lo tqcstring.lo tqcursor.lo tqdatastream.lo tqdatetime.lo tqdeepcopy.lo tqdict.lo tqdir.lo tqdom.lo tqdrawutil.lo tqdropsite.lo tqeditorfactory.lo tqeucjpcodec.lo tqeuckrcodec.lo tqevent.lo tqfile.lo tqfileinfo.lo tqfocusdata.lo tqfontdatabase.lo tqfont.lo tqfontinfo.lo tqfontmetrics.lo tqgarray.lo tqgb18030codec.lo tqgcache.lo tqgdict.lo tqglcolormap.lo tqglist.lo tqgvector.lo tqhostaddress.lo tqiconset.lo tqimage.lo tqinputcontextfactory.lo tqintcache.lo tqintdict.lo tqinterlacestyle.lo tqiodevice.lo tqjpunicode.lo tqkeysequence.lo tqlibrary.lo tqlocale.lo tqmap.lo tqmemarray.lo tqmenudata.lo tqmetaobject.lo tqmime.lo tqmovie.lo tqmutex.lo tqnamespace.lo tqobjectdict.lo tqobjectlist.lo tqpaintdevice.lo tqpaintdevicemetrics.lo tqpainter.lo tqpair.lo tqpalette.lo tqpen.lo tqpicture.lo tqpixmapcache.lo tqpixmap.lo tqpngio.lo tqpointarray.lo tqpoint.lo tqpolygonscanner.lo tqprinter.lo tqptrcollection.lo tqptrdict.lo tqptrlist.lo tqptrqueue.lo tqptrstack.lo tqptrvector.lo tqrect.lo tqregexp.lo tqregion.lo tqrtlcodec.lo tqsemaphore.lo tqsettings.lo tqshared.lo tqsignalslotimp.lo tqsimplerichtext.lo tqsize.lo tqsizepolicy.lo tqsjiscodec.lo tqsocketdevice.lo tqsortedlist.lo tqsqlcursor.lo tqsqleditorfactory.lo tqsqlerror.lo tqsqlfield.lo tqsql.lo tqsqlindex.lo tqsqlpropertymap.lo tqsqlrecord.lo tqsqlresult.lo tqsqlselectcursor.lo tqstring.lo tqstringlist.lo tqstrlist.lo tqstrvec.lo tqstylefactory.lo tqsyntaxhighlighter.lo tqtextcodecfactory.lo tqtextcodec.lo tqtextstream.lo tqthread.lo tqthreadstorage.lo tqtl.lo tqtsciicodec.lo tqurl.lo tqurlinfo.lo tqutfcodec.lo tquuid.lo tqvaluelist.lo tqvaluestack.lo tqvaluevector.lo tqvariant.lo tqvfbhdr.lo tqwaitcondition.lo tqwhatsthis.lo tqwidgetfactory.lo tqwidgetintdict.lo tqwidgetlist.lo tqwmatrix.lo tqxml.lo tqucomextra_p.lo tqlistiterator.lo -lqt-mt -lz -lpng -lz -lm -lXext -lX11 -lSM -lICE -lpthread (cd .libs && rm -f libtqt.so.4 && ln -s libtqt.so.4.2.0 libtqt.so.4) (cd .libs && rm -f libtqt.so && ln -s libtqt.so.4.2.0 libtqt.so) creating libtqt.la (cd .libs && rm -f libtqt.la && ln -s ../libtqt.la libtqt.la) make[3]: Leaving directory `/dev/shm/dependencies/tqtinterface/qtinterface' make[2]: Leaving directory `/dev/shm/dependencies/tqtinterface/qtinterface' make[2]: Entering directory `/dev/shm/dependencies/tqtinterface' make[2]: Leaving directory `/dev/shm/dependencies/tqtinterface' make[1]: Leaving directory `/dev/shm/dependencies/tqtinterface' Making install in libltdl make[1]: Entering directory `/dev/shm/dependencies/tqtinterface/libltdl' make[2]: Entering directory `/dev/shm/dependencies/tqtinterface/libltdl' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/dev/shm/dependencies/tqtinterface/libltdl' make[1]: Leaving directory `/dev/shm/dependencies/tqtinterface/libltdl' Making install in qtinterface make[1]: Entering directory `/dev/shm/dependencies/tqtinterface/qtinterface' Making install in . make[2]: Entering directory `/dev/shm/dependencies/tqtinterface/qtinterface' make[3]: Entering directory `/dev/shm/dependencies/tqtinterface/qtinterface' test -z "/usr/lib" || /usr/bin/mkdir -p "/dev/shm/package-tqtinterface/usr/lib" /bin/sh ../libtool --mode=install /usr/bin/ginstall -c -p libtqt.la '/dev/shm/package-tqtinterface/usr/lib' /usr/bin/ginstall -c -p .libs/libtqt.so.4.2.0 /dev/shm/package-tqtinterface/usr/lib/libtqt.so.4.2.0 /usr/bin/ginstall: cannot stat `.libs/libtqt.so.4.2.0': No such file or directory make[3]: *** [install-libLTLIBRARIES] Error 1 make[3]: Leaving directory `/dev/shm/dependencies/tqtinterface/qtinterface' make[2]: *** [install-am] Error 2 make[2]: Leaving directory `/dev/shm/dependencies/tqtinterface/qtinterface' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/dev/shm/dependencies/tqtinterface/qtinterface' make: *** [install-recursive] Error 1 ==================================== I seem to recall a while back of a similar breakage. I searched the list archives and there was mention of a similar error and somebody submitted some kind of patch. Tim, do you remember which one? I would like to backport the patch. I don't think this is related to the automake 2.64 issue because I have 2.65 installed. The 2.65 change log says that the AH_CHECK_HEADERS macro was reinstated. Thanks. Darrell

2 3

kdebase & Cmake
by Castro 30 Mar '11

30 Mar '11

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.

1 0

Archlinux & kdebase compiles 100%
by Castro 29 Mar '11

29 Mar '11

Hi serghei, Hi all, Please accept the slopy cut & past in my last posting. kdebase now compiles 100% without errors. :-) The last fix is to kdebase/ksplashml/themeengine/simple/CmakeLists.txt I added this link_directories( ${TQT_LIBRARY_DIRS} ) before this ##### ksplashsimple (executable) ################ Is it only archlinux that is showing these problemes? Castro.

2 1

kdepim FTBFS
by Timothy Pearson 29 Mar '11

29 Mar '11

Hi Serghei, Can you take a look at why kdepim is failing to build with CMake? http://quickbuild.pearsoncomputing.net:58080/2055705/buildlog_ubuntu-maveri… Thanks! Tim

2 9

Finding patches in svn
by Darrell Anderson 29 Mar '11

29 Mar '11

I found some patches that I think have not been merged into svn. What is the best way for me to check whether a patch has already been merged into svn? Is there a smart/efficient/programmtic way to do this? Thanks. Darrell

2 1

Building PyKDE3 (Solved???)
by Darrell Anderson 29 Mar '11

29 Mar '11

I made some progress with building PyKDE3. I had to cheat. I think. The problem seems to be that building Trinity to install in /opt/trinity confuses the PyKDE3 build process. Last autumn when I built Trinity 3.5.12 to install in /usr I had no problems building PyKDE3. Since then I have not tried to build any packages to install in /usr. I have been focusing on installing in /opt/trinity in order to coexist with KDE4/QT4. When Trinity is installed in /opt/trinity the build always fails with this kind of error: ========================================= /usr/bin/ld: cannot find -lDCOP collect2: ld returned 1 exit status make[1]: *** [dcop.so] Error 1 make[1]: Leaving directory `/dev/shm/PyKDE-3.16.7/dcop' make: *** [all] Error 2 ========================================= I then create a sym link in /usr/lib to the allegedly not found library: ln -s /opt/trinity/lib/libDCOP.so libDCOP.so The next build proceeds past that error but again fails with a similar not found error message about the next module, kdecore. I create another sym link. The package proceeds to build to the next module, kdefx, and again fails. Rinse. Repeat. For each module: dcop kdecore kdefx kdeui kio kresources kabc kutils kfile kparts khtml kspell kdeprint kmdi I modified my build script to temporarily create the sym links on-the-fly and remove them after make completes. The package then builds without failure. Yet I wonder whether this will break the package libraries. Are they linked to /usr/lib rather than /opt/trinity/lib? Seems something in the PyKDE3 configuration is hard-coded to /usr/lib. I already have the following in my build script: sed -i -e "s:/usr:${PREFIX}:" configure.py where $PREFIX is /opt/trinity /etc/ld.so.conf contains /opt/trinity/lib, which was inserted from the kdelib package (and runs ldconfig, but I have run ldconfig manually too). Running ldconfig -v shows the allegedly not found libraries in /opt/trinity/lib. The build script configure output says the following: KDE base directory is /opt/trinity KDE include directory is /opt/trinity/include KDE lib directory is /opt/trinity/lib/kde3 lib directory is /opt/trinity/lib Everything seems to indicate the libraries should be found. Yet the package refuses to build without the temporary sym links. Seems make should find the libraries in /opt/trinity/lib. Exporting LD_LIBRARY_PATH in the build script does not help. Any ideas what is happening? Any ideas how to fix? Darrell

3 4

Amarok Build Options
by Darrell Anderson 28 Mar '11

28 Mar '11

I notice in the Amarok CMakeLists.txt there are several missing build options that were available in automake: --with-libnjb --with-libmtp --with-libkarma --with-mp4v2 --without-musicbrainz --without-daap --disable-amazon For myself I have no need for syncing to devices or sharing music. Would be nice to build Amarok without that overhead. :) I realize a lot of work is going on with everything. I thought I'd mention this and hopefully the options are added eventually. Thanks. Darrell

2 1

Tin Need help with 3.5.12 automake files
by Darrell Anderson 28 Mar '11

28 Mar '11

Tim, I am able to build all of the same 3.5.12 packages I built last autumn except PyKDE3, Digikam, and Gwenview. I already submitted a post about PyKDE3 (help is appreciated!). The primary difference this time that the builds are failing is I am trying to install the Trinity/KDE packages into /opt/trinity rather than /usr. Some library and support packages, such as sip, PyQT3, PyKDE3, libical, libcaldav, etc., I am still installing in /usr and /usr/lib. Digikam FTBFS with this error: ==================== grep: /usr/lib/libkdecore.la: No such file or directory /usr/bin/sed: can't read /usr/lib/libkdecore.la: No such file or directory libtool: link: `/usr/lib/libkdecore.la' is not a valid libtool archive ==================== Gwenview FTBFS with this error: ==================== grep: /usr/lib/libkio.la: No such file or directory /usr/bin/sed: can't read /usr/lib/libkio.la: No such file or directory libtool: link: `/usr/lib/libkio.la' is not a valid libtool archive ==================== Notice the builds are trying to find those files in /usr/lib rather than /opt/trinity/lib. Something in the configuration files is hard-coded to /usr/lib. I realize 3.5.12 is more or less etched in stone, but the cmake conversion will take time. All I need is a patch that I can merge on-the-fly in my build scripts to ensure automake looks in the correct location. Besides, neither of these packages have been converted to cmake yet and probably won't be for some time. Maybe the problem is an environment variable, although all of the other packages compiled fine. I want to get all of these 3.5.12 packages to build in Slackware 12.2 with /opt/trinity. Once proven they will build, install, and run there I then will start the testing the build process with the next Slackware release, which are required to get installed in a location other than /usr. This is very much proof of concept before moving to the next step. Not to mention that in the next step I need to build qt3 too. Should anyone start quashing bugs with the core or main suite packages I can rebuild Trinity packages in 12.2 and test those patches immediately. I also should be able to install Trinity 3.5.12 alongside KDE 3.5.10 in 12.2, which will help all of us with troubleshooting and comparisons to KDE3. Thanks much! Darrell

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels