tde-devels

devels@trinitydesktop.org

3 participants
3807 discussions

kdelibs doc common build problem
by Timothy Pearson 12 Mar '11

12 Mar '11

Serghei, I almost have kdelibs built, but from what I can tell the common/ symbolic link in the documentation directories is not being created. As one example, a symbolic link would normally be present in /opt/trinity/share/doc/kde/HTML/en/kspell/common, pointing to the /opt/trinity/share/doc/kde/HTML/en/common directory. This is so that the KHTML-based documentation renderer can find the needed graphics and style files. I would try to fix this myself, but I lack the requisite CMake knowledge to do it correctly. Thanks! Tim

3 2

QSettings: errors/ KDM problem
by Baho Utot 12 Mar '11

12 Mar '11

I am currently packaging TDE for use on Arch Linux I am getting the following errors in kdelibs QSettings: error creating /.qt QSettings: error creating /.qt QSettings: error creating /.qt QSettings: error creating /.qt QSettings: error creating /.qt QSettings::sync: filename is null/empty QSettings: error creating /.qt QSettings::sync: filename is null/empty QSettings: error creating /.qt QSettings::sync: filename is null/empty Anyone know what causes these and are they benign? I have built the svn source to kdevelop and the resulting binaries produce a system that generally works. I have installed TDE based on the svn source and it mostly works. I am using TDE svn as the primary desktop on my laptop. I have a problem with kdm - it runs but you can not login to a valid user. It tries to run the desktop then goes back to the login. If anyone has any pointers on how to fix it I am all ears. The only thing on my wish list to get ported is Ark, K3b and kpdf. Thanks for all your effort I am looking forward to the completed TDE, I know it will be a lot of effort. I would help in the port but I don't know cmake and by the time I would get up to speed you guys would be done ;)

3 3

dolphin (d3lphin) builds and runs fine on Arch:
by David C. Rankin 12 Mar '11

12 Mar '11

All, Dolphin is up and running. I say it runs fine, because I was never sure it worked fine :) Honestly, I have never see where it is better than konqueror. But hey, it's a good app for the kids to play with :) Write up: https://wiki.archlinux.org/index.php/Trinity#trinity-app-d3lphin.tar.gz package: trinity-app-d3lphin-1224085-1-i686.pkg.tar.xz -- David C. Rankin, J.D.,P.E.

1 0

kdepim build failure svn version 1224538
by Baho Utot 12 Mar '11

12 Mar '11

On x86_64 I get the following error, i686 is OK [ 23%] Building CXX object certmanager/lib/backends/qgpgme/CMakeFiles/kleopatra_backend_qgpgme-static.dir/qgpgmedecryptverifyjob.cpp.o [ 23%] Building CXX object certmanager/lib/backends/qgpgme/CMakeFiles/kleopatra_backend_qgpgme-static.dir/qgpgmecryptoconfig.cpp.o [ 23%] Building CXX object certmanager/lib/backends/qgpgme/CMakeFiles/kleopatra_backend_qgpgme-static.dir/qgpgmerefreshkeysjob.cpp.o /trinity.source/kdepim/certmanager/lib/backends/qgpgme/qgpgmerefreshkeysjob.cpp:79:2: error: #error MAX_CMD_LENGTH is too low /trinity.source/kdepim/certmanager/lib/backends/qgpgme/qgpgmerefreshkeysjob.cpp: In member function 'GpgME::Error Kleo::QGpgMERefreshKeysJob::startAProcess()': /trinity.source/kdepim/certmanager/lib/backends/qgpgme/qgpgmerefreshkeysjob.cpp:91:36: error: 'MAX_CMD_LENGTH' was not declared in this scope make[2]: *** [certmanager/lib/backends/qgpgme/CMakeFiles/kleopatra_backend_qgpgme-static.dir/qgpgmerefreshkeysjob.cpp.o] Error 1 make[1]: *** [certmanager/lib/backends/qgpgme/CMakeFiles/kleopatra_backend_qgpgme-static.dir/all] Error 2 make: *** [all] Error 2 Aborting... Build failed, check /home/build/copy/build make: *** [KDEPIM] Error 1 Fixes anyone?

1 0

Arch Linux - dev tip -> kate syntax highlighting for PKGBUILD scripts
by David C. Rankin 12 Mar '11

12 Mar '11

All Arch-Trinity devs (and everyone else): Most probably know this, but there is a great little trick to use in kate to automatically apply bash syntax highlighting to PKGBUILD scripts when you open them in kate/kwrite. The only requirement is that you give the PKGBUILD scripts a common extension. (I haven't been able to find a way to do this without using an extension). The extension can be anything - so long as it isn't already used by something else. (.pb or .pkgb will work). I ended up with '.svn' extensions by accident when I changed from building in tree to the traditional PKGBUILD format to distinguish the new PKGBUILDs. eg.: 19:02 alchemy:~> ls -1 tde/tnotes/pkgbuild/svn PKGBUILD-app-amarok.svn PKGBUILD-app-gtk-qt-engine.svn PKGBUILD-app-kgtk-qt3.svn <snip> If you are working on any other distro that has a known highlighting syntax file in kate/kwrite -- this will also work for you. To set this up, in kate: (1) Settings -> Configure Kate -> Highlighting (2) select the mime-type for your file from the "Highlight:" list-box (3) then add your script extension to the "File extensions:" field For my Arch setup where the PKGBUILD scripts have bash syntax, the setup looks like: Highlight: Scripts/Bash File extensions: *.sh;*.bash;*.ebuild;*.eclass;*.svn;<snip> Works like a champ... and beats the heck out of doing 'Tools->Highlighting->Scripts->Bash' over and over again :) -- David C. Rankin, J.D.,P.E.

1 0

kdelibs FTBFS
by Timothy Pearson 11 Mar '11

11 Mar '11

Serghei, Could you offer any suggestions as to why arts cannot be found during the kdelibs build process? http://quickbuild.pearsoncomputing.net:58080/2051543/buildlog_ubuntu-maveri… I wonder if it may have anything to do with moving the two main arts header files from include/arts/arts*.h to include/artsc/arts*.h Thanks! Tim

2 1

Sources&info, also reflects for qt3 3.3.8c sources required
by PICCORO McKAY Lenz 10 Mar '11

10 Mar '11

For many users recently incoming, the sources of qt3 3.3.8c now requires a this pachet version of qt3 for trinity building. This patched version is fully source and binary compatible with 3.3.8b, but provides additional methods that are required to complete the TQt interface. The following patch, when applied to 3.3.8b, will increase the version number to 3.3.8c: - qt3_3.3.8c.diff<http://trinity.pearsoncomputing.net/wiki/pub/Developers/Qt3/qt3_3.3.8c.diff> But this kind of info are not property reflected on wiki (old or new) and in README from sources (at least on kde 3.5.12), please help (or tell me how i could do that by my seltf) to update wiki and readme files property reflected this, and also upload to sources download the patch and/or qt3 complete/parcial sources for download. I know that documentation are also a recuested help on trinity proyect.. event i try to port bluez api, (but i colund yet), generates docu files and contents are easyl for me! ---------- Forwarded message ---------- From: Darrell Anderson <humanreadable(a)yahoo.com> Date: Thu, Mar 10, 2011 at 10:13 PM Subject: Re: qt3 3.8.8c To: PICCORO McKAY Lenz <mckaygerhard(a)gmail.com> That's a good question. I haven't a clue how to find the patch page through the normal links in the wiki, but here is the link from a past list message: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/Qt3 Hopefully someobdy who knows about these hidden pages will update the wiki with some links? Darrell --- On Thu, 3/10/11, PICCORO McKAY Lenz <mckaygerhard(a)gmail.com> wrote: > From: PICCORO McKAY Lenz <mckaygerhard(a)gmail.com> > Subject: qt3 3.8.8c > To: humanreadable(a)yahoo.com > Date: Thursday, March 10, 2011, 6:23 AM > please where can be obtained qt3 3.8.8c i > only find 3.8.8b ? > > -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; http://shutendouji.net creador de massenkoh linux.

5 10

arts CMake build enhancement request
by Timothy Pearson 10 Mar '11

10 Mar '11

Serghei, Could you please update the arts CMake files to build and install the artsc/artsdsp wrapper script into bin/? I need it in order to build the Debian/Ubuntu packages. Thanks! Tim

2 1

Numerous FTBFS Problems
by Darrell Anderson 10 Mar '11

10 Mar '11

Now that the ui-tqt problem is fixed, I tried again building the core packages. tqtinterface, arts, kdelibs, and kdebase build without errors. From there seems everything is broken. :( All of the following packages are still built with automake. I want to get the core packages built so I can help with test bug fixes next weekend. =========================================== PyKDE3 I previously posted a message that I can't build PyKDE3. Link to build log: http://humanreadable.nfshost.com/files/pykde3-3.16.7-i486-1-build.log.gz =========================================== kdebindings. Link to build log: http://humanreadable.nfshost.com/files/kdebindings-3.5.13-i486-svn_1224257-… I tried building without sip or pyqt3 installed to ensure there was no presumed python support. kdebindings still failed to build. =========================================== kdeaccessibility Link to build log: http://humanreadable.nfshost.com/files/kdeaccessibility-3.5.13-i486-svn_122… =========================================== kdeutils Link to build log: http://humanreadable.nfshost.com/files/kdeutils-3.5.13-i486-svn_1224257-bui… =========================================== kdemultimedia Link to build log: http://humanreadable.nfshost.com/files/kdemultimedia-3.5.13-i486-svn_122425… =========================================== At this point I stopped. Perhaps the failures are all related. Darrell

3 10

Trinity End-User Documentation
by Darrell Anderson 09 Mar '11

09 Mar '11

I have close to 3 decades technical writing experience. Naturally, I have an interest in any documentation packaged with Trinity. :) The Help files need serious attention. In KDE 3.5.10 many Help files are out-of-date. Eventually we have to update those Help files. I don't know how the original Help files were maintained or created. I need help and direction with that. I want to see an overall user guide to Trinity. The guide would be available in two forms: HTML and PDF. The HTML version would be a desktop shortcut available to all users who first install Trinity and should be a menu option for those who delete the shortcut. I am willing to lead this part of the project. I face an immediate challenge: my background is overwhelmingly with paper products and not electronic. I need help and advice with the tools I need to learn to produce two different outputs (HTML and PDF). OpenOffice Writer (now LibreOffice) might be a choice, but I suspect the HTML output will leave much to be desired. Some sort of structured authoring front-end would makes sense (DocBook?), but that means a lot of sweat equity to massage the back end formatting. The system used to produce the original Help files might be a solution. I am open to ideas and discussion. Darrell

5 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels