tde-devels

devels@trinitydesktop.org

7 participants
3840 discussions

kdepim - installing files to wrong directory
by Baho Utot 15 Mar '11

15 Mar '11

I don't know anything about cmake but... the following files are installed in the root filesytem under /ktnef ktnefattach.h ktnefdefs.h ktnefmessage.h ktnefparser.h ktnefproperty.h ktnefpropertyset.h ktnefwriter.h Should they not be in /opt/trinity/lib I could be missing something in cmake as I build the packages like this cmake ${_source}/${_module}/ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DQTDIR=/opt/qt \ -DQT_LIBRARY_DIRS=/opt/qt/lib \ -DBUILD_ALL=ON make Which gives me an error in my packaging tools trinity-kdepim W: File (ktnef/ktnefattach.h) exists in a non-standard directory. trinity-kdepim W: File (ktnef/ktnefdefs.h) exists in a non-standard directory. trinity-kdepim W: File (ktnef/ktnefwriter.h) exists in a non-standard directory. trinity-kdepim W: File (ktnef/ktnefpropertyset.h) exists in a non-standard directory. trinity-kdepim W: File (ktnef/ktnefproperty.h) exists in a non-standard directory. trinity-kdepim W: File (ktnef/ktnefparser.h) exists in a non-standard directory. trinity-kdepim W: File (ktnef/ktnefmessage.h) exists in a non-standard directory.

2 1

WARNING: No Qt ui compiler (uic) found
by Darrell Anderson 15 Mar '11

15 Mar '11

I'm trying to work my way through building the core apps, either with cmake when supported or automake. I received the following trying to build kdeaccessibility: ================================ checking for Qt... libraries /usr/lib/qt-3.3.8c/lib, headers /usr/lib/qt/include using -mt checking for moc... /usr/lib/qt/bin/moc 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. ================================ I ran into the same message several days ago when first trying to build arts. The list archives show no response to that query. Thus I don't know what causes this message. I have qt-3.3.8c, tqtinterface, arts, kdelibs, and kdebase installed. Darrell

3 6

OpenSUSE KDE3 faced serious problems with updating to 11.4
by Ilya Chernykh 15 Mar '11

15 Mar '11

Now OpenSUSE 11.4 is out and all KDE3 users in OpenSUSE report the same error: crash in kcontrol icon theme module which makes kcontrol entirely empty on default install. The crash depends on used icon theme, but the most themes crash that module. I suspect the problem originates with zlib.

4 6

apps-amaok build error
by Baho Utot 15 Mar '11

15 Mar '11

On i686 svn sources amarok failed with [ 81%] Building CXX object amarok/src/CMakeFiles/amarok-shared.dir/newdynamic.cpp.o [ 82%] Building CXX object amarok/src/CMakeFiles/amarok-shared.dir/organizecollectiondialog.cpp.o /build/BUILD/amarok/src/organizecollectiondialog.cpp:256:9: error: prototype for 'QString OrganizeCollectionDialog::buildDestination(const QString&, const MetaBundle&)' does not match any in class 'OrganizeCollectionDialog' /build/BUILD/amarok/src/organizecollectiondialog.h:59:21: error: candidate is: virtual QString OrganizeCollectionDialog::buildDestination(const QString&, const MetaBundle&) const /build/BUILD/amarok/src/organizecollectiondialog.cpp:262:9: error: prototype for 'QString OrganizeCollectionDialog::buildFormatTip()' does not match any in class 'OrganizeCollectionDialog' /build/BUILD/amarok/src/organizecollectiondialog.h:60:21: error: candidate is: virtual QString OrganizeCollectionDialog::buildFormatTip() const /build/BUILD/amarok/src/organizecollectiondialog.cpp:268:9: error: prototype for 'QString OrganizeCollectionDialog::buildFormatString()' does not match any in class 'OrganizeCollectionDialog' /build/BUILD/amarok/src/organizecollectiondialog.h:61:21: error: candidate is: virtual QString OrganizeCollectionDialog::buildFormatString() const /build/BUILD/amarok/src/organizecollectiondialog.cpp:279:9: error: prototype for 'QString OrganizeCollectionDialog::cleanPath(const QString&)' does not match any in class 'OrganizeCollectionDialog' /build/BUILD/amarok/src/organizecollectiondialog.h:63:21: error: candidate is: virtual QString OrganizeCollectionDialog::cleanPath(const QString&) const make[2]: *** [amarok/src/CMakeFiles/amarok-shared.dir/organizecollectiondialog.cpp.o] Error 1 make[1]: *** [amarok/src/CMakeFiles/amarok-shared.dir/all] Error 2 make: *** [all] Error 2 Aborting... Is this a known error/ howto fix

3 5

Support for KDE3 removed from LibreOffice
by Ilya Chernykh 15 Mar '11

15 Mar '11

I have just installed 11.4 and Libre Office 3.3.1 uses GTK front-end under 11.4. With OpenOffice.org 3.2.1 under 11.3 all was OK.

8 14

Downgrading autoconf/automake
by Darrell Anderson 14 Mar '11

14 Mar '11

What caveats should I know with downgrading autoconf/automake? The port to cmake is a wise long-term strategy but will take time. While svn remains in a mixed autotools and cmake environment, both sets of build tools are needed during the transition. As I am already two releases behind, I was thinking about moving to the next release of Slackware, which is now in RC status. That move also will allow me to test Trinity in an environment with KDE4 installed. That upcoming Slackware release comes with autoconf-2.68 and automake-1.11.1. As explained to me, I cannot build KDE 3.5.10 or Trinity with that version of those tools. I was thinking about updating to the new Slackware release and then temporarily downgrading to autoconf-2.63 and automake-1.10.1 so I can build and help test Trinity during the long-term port to cmake. I presume that if I want to build third-party packages for the new Slackware release, I might have to toggle to autoconf-2.68 and automake-1.11.1 to ensure no compatibility problems. Perhaps I need only downgrade autoconf and not automake. I have no clue if that is possible too. Will this work? Darrell

6 25

kdebase missing cmake for kioslave
by Timothy Pearson 14 Mar '11

14 Mar '11

Hi Serghei, In kdebase, kdebase/kioslave/media/propsdlgplugin does not have a CMake control file. Could you create one? This is currently holding up Debian/Ubuntu builds of kdebase. Thanks! Tim

2 2

kpowersave on x86_64 - pkg_search_module( XSCRNSAVER xscrnsaver ) fails??
by David C. Rankin 13 Mar '11

13 Mar '11

Guys, I can't explain this one. On i686, kpowersave built fine, but on x86_64, the build fails due to: CMake Error at cmake/modules/TDEMacros.cmake:20 (message): ################################################# xscrnsaver are required, but not found on your system ################################################# Call Stack (most recent call first): ConfigureChecks.cmake:42 (tde_message_fatal) CMakeLists.txt:40 (include) -- Configuring incomplete, errors occurred! In ConfigureChecks.cmake, we have: # check for xscrnsaver pkg_search_module( XSCRNSAVER xscrnsaver ) if( NOT XSCRNSAVER_FOUND ) tde_message_fatal( "xscrnsaver are required, but not found on your system" ) endif() On Arch the package is actually xscreensaver. On both i686 and x86_64 boxes, I have 'xscreensaver 5.12-2' installed, but for some reason, this works on i686. Dunno why... Where can I look at the actual code for "pkg_search_module()" so I can tell exactly what it is looking for? It almost seems like I've run into this before, but can't recall for the life of me what I did to address it? There must be some other package on the box that works that provides the dependency that kpowersave is looking for, but how do I figure that out? What say the experts? -- David C. Rankin, J.D.,P.E.

4 7

Re: [trinity-devel] kpowersave on x86_64 - pkg_search_module( XSCRNSAVER xscrnsaver ) fails??
by Calvin Morrison 13 Mar '11

13 Mar '11

We install them with regular packages, since arch users almost always are compiling, developing etc we just include them. While it takes more space it saves alot of work. Sorry for the top post Calvin Morrison Kristopher Gamrat <pikidalto(a)gmail.com> wrote: >On Sun, Mar 13, 2011 at 7:33 AM, calvin morrison <mutantturkey(a)gmail.com> wrote: >> On 12 March 2011 23:57, Kristopher Gamrat <pikidalto(a)gmail.com> wrote: >>> >>> Normally it is forgetting to install the devel package. Or it may be >>> looking for the 32bit version of xscreensaver, which means it would >>> need adjusted to check for 64bit. You probably know this, but 64bit >>> libs tend to go into lib64 instead of lib, so that might be where it >>> fails because some stuff have it hardcoded to assume 32bit libs. Of >>> course, I couldn't understand the code very well, so I couldn't tell >>> you for sure. >>> >>> -- >>> Kris >>> "Piki" >>> Ark Linux Webmaster >>> Trinity Desktop Environment Packager >> >> All of those assumptions here are wrong for arch :) we don't have >> devel packages and we don't have a lib64 > >I haven't seen a distro not have lib64, but I haven't used Arch either >(except for the time when I tried it and couldn't find something like >dhclient or dhcpcd to get online, didn't have 64bit then). I also >haven't seen a distro without dev or devel packages either -- unless >you guys are installing the devel headers with the main packages (not >necessary for people who aren't compiling software), I'd think you >have to put them somewhere? > >-- >Kris >"Piki" >Ark Linux Webmaster >Trinity Desktop Environment Packager > >--------------------------------------------------------------------- >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 >

1 0

kdebase FTBFS
by Timothy Pearson 13 Mar '11

13 Mar '11

Hi Serghei, Can you take a look at this please? https://quickbuild.pearsoncomputing.net/~trinity/+archive/trinity-nightly-b… It seems that even though I passed -DWITH_SAMBA to cmake the samba .la file was not built or installed. Thanks! Tim

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels