tde-devels

devels@trinitydesktop.org

3854 discussions

Estimate When SVN Will Ready
by Darrell Anderson 26 Mar '11

26 Mar '11

How about an estimate when SVN will again be ready to build? I see a lot of work going on with interfacing with QT4, which seems to have rendered SVN unbuildable. I tried building SVN last night and things broke quickly in kdelibs. The error had something to do with tqtinterface. I realize much is happening under the surface but us mushrooms would appreciate a drop of rain now and then. :) Darrell

3 4

dbus-tqt - missing cmake modules
by Baho Utot 26 Mar '11

26 Mar '11

The svn trre for dbus-tqt is missing the following files cmake/modules cmake/modules/FindQt.cmake cmake/modules/FindTDE.cmake cmake/modules/FindTQt.cmake cmake/modules/TDEMacros.cmake cmake/modules/TDESetupPaths.cmake cmake/modules/tde_uic.cmake cmake/modules/template_dummy_cpp.cmake cmake/modules/template_export_library.cmake cmake/modules/template_kdeinit_executable.cmake cmake/modules/template_kdeinit_module.cmake cmake/modules/template_libtool_file.cmake I copied them from kpower to get dbus-tqt to build Thanks

1 0

Re-Write of Qt3 PKGBUILD required for Arch - original script patched 3.3.8 instead of 3.3.8b
by David C. Rankin 26 Mar '11

26 Mar '11

Calvin, Baho, I will re-write the Qt3 PKGBUILD for Arch. The addition of the new 3.3.8c patch disclosed we were building and patching: 3.3.8 -> 3.3.8c instead of patching 3.3.8b -> 3.3.8c The original Arch PKGBUILD for Qt3 has a mess of combined patches contained within 2 .tar.bz2 files: qt-copy-kde-patches.tar.bz2 qt-patches.tar.bz2 Patching 3.3.8b fails with: Hunk #1 succeeded at 155 (offset 3 lines). patching file src/kernel/qprocess.cpp Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file src/kernel/qprocess.cpp.rej That part of the patch is somewhere in the tarballs above. I'll sort through it and put up a clean trinity-qt3 PKGBUILD when I find the issue. If you try and apply the new part of the trinity qt3_3.3.8c.diff you will find it fails on: -#define QT_VERSION_STR "3.3.8b" because the source the Arch PKGBUILD pulls is: -#define QT_VERSION_STR "3.3.8" Just FYI... -- David C. Rankin, J.D.,P.E.

2 7

openexr are requested, but not found on your system
by Darrell Anderson 26 Mar '11

26 Mar '11

I received the following message while trying to build arts from svn 1225868: "openexr are requested, but not found on your system" Serghei, I know English is not your primary language :). I suggest the following text: "The openexr package was requested but not found on your system." I have nothing against the warning but the build should not have stopped. There does not seem to be option in the arts CMakeLists.txt file to build without OpenEXR nor does the build simply pass through when not finding that package. The OpenEXR package is commonly installed but has never been required in KDE 3.5.10 or Trinity. If that package is now a Trinity prerequisite, then let's pass the word here and I'll be happy to update the wiki. :) Darrell

1 1

tqtinterface patch
by Baho Utot 26 Mar '11

26 Mar '11

Here is a patchto test/break to stop this error In file included from <command-line>:0:0: /opt/qt/include/tqt/tqt.h:25:0: warning: "USE_QT3" redefined <command-line>:0:0: note: this is the location of the previous definition

2 1

All current Arch PKGBUILDS now broken due to new Out of Source Build Requirement
by David C. Rankin 25 Mar '11

25 Mar '11

Tim, Serghei, I went to build trinity tonight and found all arch PKGBUILDS fail with the same error: CMake Error at cmake/modules/TDEMacros.cmake:20 (message): ################################################# Please use out-of-source building, like this: rm /home/david/tblds/trinity-tqtinterface/src/tqtinterface/CMakeCache.txt mkdir /tmp/tqt.build cd /tmp/tqt.build cmake /home/david/tblds/trinity-tqtinterface/src/tqtinterface [arguments...] ################################################# Call Stack (most recent call first): cmake/modules/TDEMacros.cmake:1124 (tde_message_fatal) CMakeLists.txt:29 (include) I'm not sure why this is needed since the PKGBUILD process takes place in a *newly* created src directory that is *outside* the svn tree. This will take a rewrite of all PKGBUILDS to accommodate this change. -- David C. Rankin, J.D.,P.E.

5 13

Re: [trinity-devel] All current Arch PKGBUILDS now broken due to new Out of Source Build Requirement
by Calvin Morrison 25 Mar '11

25 Mar '11

I have thought of a simple solution. Why not create a flag to bypass this? That way for packaging we can use it, but normally it won't be allowed. Makes sense to me Calvin Morrison

1 0

kdelibs build FYI
by Baho Utot 25 Mar '11

25 Mar '11

I am getting a lot of the follwing error/warnings when building kdelibs [ 1%] Building CXX object dcop/CMakeFiles/DCOP-shared.dir/dcopclient.cpp.o In file included from <command-line>:0:0: /opt/qt/include/tqt/tqt.h:25:0: warning: "USE_QT3" redefined <command-line>:0:0: note: this is the location of the previous definition I have cleaned out my svn source directory and rechecked out the tree, so I wouldn't have any gremlins and would have a fresh starting point Thanks

2 1

PyKDE3 FTBFS: cannot find -lDCOP
by Darrell Anderson 25 Mar '11

25 Mar '11

Here is the end of the build log: =========================================== g++ -c -Wno-deprecated-declarations -pipe -fPIC -O2 -Wall -W -D_REENTRANT -DNDEBUG -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I. -I../extra/kde353 -I/opt/trinity/include -I/usr/include/python2.5 -I/usr/lib/qt/mkspecs/default -I/usr/lib/qt/include -I/usr/X11R6/include -o sipdcopDCOPClientTransaction.o sipdcopDCOPClientTransaction.cpp g++ -shared -Wl,-rpath,/opt/trinity/lib/kde3 -Wl,-rpath,/usr/lib/qt/lib -Wl,--version-script=dcop.exp -o dcop.so sipdcopcmodule.o sipdcopQPtrList0100DCOPObject.o sipdcopQValueList0100QCString.o sipdcopDCOPStub.o sipdcopDCOPRef.o sipdcopDCOPReply.o sipdcopDCOPObjectProxy.o sipdcopDCOPObject.o sipdcopDCOPClient.o sipdcopDCOPClientTransaction.o -L/opt/trinity/lib/kde3 -L/usr/lib/qt/lib -L/usr/X11R6/lib -lDCOP -lqt-mt -lXext -lX11 -lm -lpthread /usr/lib/gcc/i486-slackware-linux/4.2.4/../../../../i486-slackware-linux/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'm progressing my way toward building Trinity on the most recent Slackware release. For preparation, I am first building Trinity on Slackware 12.2 using the 3.5.12 tarballs. The idea is that Trinity 3.5.12 will get installed and coexist with KDE 3.5.10. When I eliminate the building bugs I then will start building on the latest Slackware release, where QT4 and KDE4 is installed. I can build 3.5.12 on Slackware 12.2. That was with an installation location in the traditional /usr rather than /opt/trinity. I built the four 3.5.12 core packages using $PREFIX=/opt/trinity. I built sip and PyQT3 without errors. The next package in the build sequence before building kdebindings with python support is PyKDE3. I'm building PyKDE3 with the following: python ./configure.py -k $PREFIX -L $LIBDIR -n $LIBDIR/kde3 -o $PREFIX/include -i where: KDE base directory ($PREFIX): /opt/trinity lib directory ($LIBDIR): /opt/trinity/lib KDE lib directory: /opt/trinity/lib/kde3 KDE include directory: /opt/trinity/include PyKDE3 built fine when I used the original locations of /usr, /usr/include, /usr/lib, /usr/lib/kde3. I built and installed sip and pyqt3 to /usr rather than /opt/trinity as there is no conflict with other packages that I know. When PyKDE3 FTBFS, I then rebuilt those two packages to install in /opt/trinity. Same failure. Probably a path problem. Any ideas? Darrell

1 1

svn.trinitydesktop.org -- need a bit of help with the URLs
by David C. Rankin 25 Mar '11

25 Mar '11

Tim, All, Before heading out with the kids for spring break, I was trying to upload the pkgbuilds to the svn server, but found I needed a bit of help. I've got the svn docs and think I got the commands right, but I'm not sure of the svn repository URL for uploading. Generally the checkout/commit url is different than the websvn url i.e. svn://svn.trinitydesktop.org/ compared to http://svn.trinitydesktop.org/. Also the space in "Trinity Packaging" will I guess take a %20 or something similar. I have all of the PKGBUILDs updated with the OpenSource statement from etherpad. I have also created a structure of Arch/master/src to hold the pkgbuilds. They are all available here: http://www.3111skyline.com/dl/dt/trinity/arch/master/src/ What I need to know is how I can get them to the svn.trinitydesktop.org server? Do I do a svn checkout, then modify and then a commit? Or do I just do a svn add? Then what URL? http://svn.trinitydesktop.org/websvn/listing.php?repname=Trinity+Packaging&… I know that's not right :) What say the svn experts? -- David C. Rankin, J.D.,P.E.

4 11

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels