tde-devels March 2011

devels@trinitydesktop.org

20 participants
133 discussions

by Darrell Anderson

I'm trying to build Trinity from SVN. I'm still using my old build scripts with automake. As I have not tested my build environment since last autumn, I wanted to make one run to ensure everything still works before trying other things. Basically, start with a known good environment. According to recent list conversations, building with automake should still work with distros using older autotools. Building tqtinterface failed immediately: ============================================ cp: cannot create regular file `admin/libtool.m4.in': No such file or directory cp: cannot create regular file `admin/ltmain.sh': No such file or directory make: admin/Makefile.common: No such file or directory make: *** No rule to make target `admin/Makefile.common'. Stop. ============================================ There no longer is an svn admin directory in the tqtinterface sources. The wiki says "The current SVN tree is being ported to CMake. You cannot build part of the tree with CMake and then start building with autoconf." Do I now have to build tqtinterface with cmake? If so, then I according to the wiki I cannot build the remaining packages with autotools. I saw nothing obvious in the list archives. Darrell

13 years, 1 month

Building arts with automake fails (looking for qt uic)

by Darrell Anderson

After failing to build arts with cmake, I tried again with automake. Yes, I know the move is toward cmake, but automake remains supported. I received the following errors: =================================== checking for uic-tqt... not found configure: WARNING: No Qt ui compiler (uic) found! Please check whether you installed Qt correctly. You need to have a running uic binary. configure tried to run and the test didn't succeed. If configure shouldn't have tried this one, set the environment variable UIC to the right one before running configure. make: *** No targets specified and no makefile found. Stop. =================================== How to fix? I rebuilt and installed qt3 with the 3.3.8c patch. Oddly, when I compared the 3.3.8b and 3.3.8c packages, only the directory names were different. Were any qt3 files in the 3.3.8c package changed, or was the patch needed only to build qt3 with the latest tqtinterface? Darrell

13 years, 1 month

Building tqtinterface with cmake fails

by Darrell Anderson

I got qt patched to 3.3.8c and installed. :) Now I'm trying to update my tqtinterface build script to build with cmake because there is no admin directory in the tqtinterface source tree. IF tqtinterface can still be built with autoconf then somebody please explain. :) The build with cmake fails. I hope I am correctly following the directions at the wiki. Here are the relative snippets from my build script: ================================ PRGNAM=tqtinterface TMP=${TMP:-/tmp} ... cmake ${TMP}/${PRGNAM} \ -DCMAKE_INSTALL_PREFIX=${PREFIX} \ -DCMAKE_VERBOSE_MAKEFILE=ON \ -DWITH_QT3=ON \ -DQTDIR=$QTDIR \ -DQT_LIBRARY_DIRS=${QTDIR}/lib \ -DBUILD_ALL=ON make VERBOSE=1 ================================ I am building in $TMP and not the svn source tree. I am at svn 1223991. I receive the following cmake error output: ================================ -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- checking for 'Qt' -- Performing Test HAVE_PATCHED_QT3 -- Performing Test HAVE_PATCHED_QT3 - Success CMake Error at cmake/modules/TDEMacros.cmake:1051 (unset): Unknown CMake command "unset". Call Stack (most recent call first): cmake/modules/FindQt.cmake:96 (tde_restore) CMakeLists.txt:39 (find_package) -- Configuring incomplete, errors occurred! make: *** No targets specified and no makefile found. Stop. ================================ Darrell

13 years, 1 month

kdebase

by Baho Utot

I am trying to build kdebase SVN checkout of revision 1223901 -- Complete , which resluts in this error [ 48%] Building CXX object kioslave/man/CMakeFiles/kio_man-module.dir/kio_man.cpp.o Linking CXX shared module kio_man.so [ 48%] Built target kio_man-module [ 48%] Generating kmanpart.moc Scanning dependencies of target libkmanpart-module [ 48%] Building CXX object kioslave/man/CMakeFiles/libkmanpart-module.dir/kmanpart.cpp.o Linking CXX shared module libkmanpart.so [ 48%] Built target libkmanpart-module [ 48%] Generating mount_xdr.c file `mount_xdr.c' already exists and may be overwritten make[2]: *** [kioslave/nfs/mount_xdr.c] Error 1 make[1]: *** [kioslave/nfs/CMakeFiles/kio_nfs-module.dir/all] Error 2 make: *** [all] Error 2 Aborting... Building a few days ago worked SVN revision 1222980 works Can anyone look into this?

13 years, 1 month

TDE CMake learning Q - How does 'install ( FILES...' put things in 2 places?

by David C. Rankin

Guys, I'm making headway figuring out CMake so I can be a bit more helpful. I'm currently reverse engineering kruler (it's small enough to learn with). So far, the kruler CMakeLists.txt is easy to follow, but I can't figure out how the following creates 2 files?? install( FILES kruler.desktop DESTINATION ${XDG_APPS_INSTALL_DIR} ) /opt/trinity/share/applications/kde/kruler.desktop /opt/trinity/share/applnk/Graphics/kruler.desktop Is there something that says if to ${XDG_APPS_INSTALL_DIR} put it in both the following places: /opt/trinity/share/applications/kde/ /opt/trinity/share/applnk/Graphics/ The other install ( FILES... just end up in one place. (eg. install( FILES eventsrc DESTINATION ${DATA_INSTALL_DIR}/kruler ) /opt/trinity/share/apps/kruler/eventsrc install( FILES move.wav DESTINATION ${DATA_INSTALL_DIR}/kruler/sounds ) /opt/trinity/share/apps/kruler/sounds/move.wav What's the difference? -- David C. Rankin, J.D.,P.E.

13 years, 1 month

partial port to cmake for kdepim was commited to svn

by Serghei Amelian

[kdepim]: initial cmake support for following subpackages: akregator, certmanager, kaddressbook, kalarm, kioslaves, kmail, ktnef, libemailfunctions, libkcal, libkdenetwork, libkdepim, libkmime, libkpgp, libkpimidentities, libksieve, mimelib -- Serghei

13 years, 1 month

knetworkmanager CMake Error - FindQt.cmake:91 (check_cxx_source_compiles)

by David C. Rankin

Serghei, I think I found a cmake error in knetworkmanager: -- checking for 'Qt' CMake Error at cmake/modules/FindQt.cmake:91 (check_cxx_source_compiles): Unknown CMake command "check_cxx_source_compiles". Call Stack (most recent call first): ConfigureChecks.cmake:43 (find_package) CMakeLists.txt:49 (include) -- Configuring incomplete, errors occurred! Aborting... -- David C. Rankin, J.D.,P.E.

13 years, 1 month

Latest Build - no kcontrol -> panels, kicker icons for home, etc. gone?

by David C. Rankin

Guys, I just finished a rebuild of everything this morning and the kcontrol settings for desktop -> 'panel' are gone and my kicker icon for home and others are gone. x86_64 icons are there, but i686 is messed up. The versions I have are: trinity-app-amarok 1223570-1 trinity-app-gtk-qt-engine 1222892-1.0 trinity-app-style-qtcurve 1182805-1 trinity-arts 1222998-1 trinity-kdebase 1223270-1 trinity-kdegraphics 1223711-1 trinity-kdelibs 1222999-1 trinity-kdevelop 1222477-1 trinity-kdewebdev 1222551-1 trinity-pyqt3 3.18.1-9 trinity-qt3 3.3.8-20 trinity-tqtinterface 1222551-1 Has anybody else see this behavior? I'll try deleting all sources and try another rebuild. If you know anything else about this behavior, please let me know. On x86_64 kruler causes a desktop crash on orientation switch. (still looking at this one, but 'west' seems to be the one that does it) -- David C. Rankin, J.D.,P.E.

13 years, 1 month

Re: [trinity-devel] Keyserver and ppa server

by Calvin Morrison

Tiago Marques <tiagomnm(a)gmail.com> wrote: >On Fri, Mar 4, 2011 at 5:43 AM, Timothy Pearson <kb9vqf(a)pearsoncomputing.net >> wrote: > >> > On Fri, Mar 4, 2011 at 12:02 AM, Tiago Marques <tiagomnm(a)gmail.com> >> wrote: >> >> Not very fast (20KiB/s) but currently installing. Thanks! >> > >> > A lot of top posts from several people. Probably just the haste of >> > trying to input in the renaming thread (mistakes like that happen a >> > lot), so just a friendly reminder to bottom post. >> > >> > The quickbuild server has always been a bit slow. Tim mentioned why >> > awhile ago (I think on IRC?), I think he might have said it was a >> > personal connection? If my memory is correct, that's a lot of stress >> > for a standard home connection with the other mirrors sync'ing and >> > people at the home or office downloading. >> >> Thank you for pointing that out; it appears that the round robin redirect >> system was not functioning properly. This should now be fixed and you >> should be getting much faster download speeds. >> >> >I'm unable to connect again. I have access to a server in the local >university, I could set up a mirror there, since we have some free space. >What are the space requirements for it? > >Best regards, >Tiago > > >> Tim >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: >> trinity-devel-unsubscribe(a)lists.pearsoncomputing.net >> For additional commands, e-mail: >> trinity-devel-help(a)lists.pearsoncomputing.net >> Read list messsages on the Web archive: >> http://trinity-devel.pearsoncomputing.net/ >> Please remember not to top-post: >> http://trinity.pearsoncomputing.net/mailing_lists/#top-posting >> >>

13 years, 1 month

Naming: Trinity Desktop Environment or KDE Classic developed by the Trinity Project?

by Kristopher Gamrat

On Thu, Mar 3, 2011 at 12:34 PM, David C. Rankin <drankinatty(a)suddenlinkmail.com> wrote: > On 03/03/2011 07:28 AM, Ilya Chernykh wrote: <snip> >> Recently I saw in the KDE forum that somebody suggested that Trinity could be >> named "KDE Classic" to empathize the connection with all the KDE heritage and >> history and also underline that it is the true KDE. >> >> I think I should agree that this is reasonable idea. >> >> - It would spare you from re-branding and re-drawing the artwork. >> - KDE is well known desktop and brand. >> - Many KDE3 apps claim they are written for KDE. This may create confusion >> with some users if they use Trinity. >> - Continuous version system (KDE Classic 4 etc vs. Trinity 4). >> - You empathize that KDE3 did not dead, and KDE Classic is the true KDE rather >> than KDE SC 4. >> - Parallels with Mac OS Classic, Windows Classic (a Windows appearance theme) >> terms. >> - You can keep the both names: "KDE Classic by Trinity project" etc. >> >> I thought many times what would happen if the creators of KDE4 named their >> desktop "Plasma" or something and left the brand of KDE to KDE3. I think in >> that case KDE4 would not be so popular because the users would not associate >> it with KDE and perceived only KDE3 as the last true KDE. Indeed the name >> means very much. >> >> >> > > If you look at the openSuSE and kde lists as early as 2008, I thought "KDE > Classic" made sense for kde.org for 4 reasons: > > (1) there was no rational reason for 'abandoning' the kde3 code - it was a > fantastic desktop; > > (2) kde3 and kde4 are not mutually exclusive, they can both exist side-by-side, > > (3) continuing to offer kde3 provided users a 'choice' of kde desktops (which > is what open-source is supposed to be all about), and > > (4) the manpower provided by kde.org required to maintain kde3 was minimal > compared to the requirements of developing the new kde4. > > Basically, it was a "why throw the baby out with the bath water?" issue. > > I think kde.org may be more receptive to this idea now than they were 2 years > ago and this project has proven the kde3 can be maintained and moved into the > future with virtually no resources from kde.org, ...and... to be fair I should > also add a 5th reason it makes sense for kde.org to continue KDE Classic. It > provides them with a fallback: > > (5) "what do we do when kde4 blows up in our face?" A discussion started on another thread on whether to keep the name Trinity Desktop Environment or to rename to KDE Classic. I thought I'd make this discussion a bit more obvious to those who may want to provide input. -- Kris "Piki" Ark Linux Webmaster Trinity Desktop Environment Packager

13 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels March 2011