tde-devels

devels@trinitydesktop.org

13 participants
3722 discussions

by J Leslie Turriff

1 hour, 11 minutes

TDE and vintage computers

by Darrell Anderson

I would like to offer that with my efforts to build TDE on vintage systems, I built TDE R14.1.2 on Slackware 14.2 64-bit (gcc 5.5.0) and Slackware 14.1 32-bit (gcc 4.8.2). Both systems are EOL as of Dec. 2023. I did not build every package but core dependencies and packages built and run. I had to find some patches to back port. For example, some patches related to hotpluggable hwlib and ensuring '-std=c++11' is declared with tqt3. These days my brain is entrenched in old fart elderly territory and I have my days exhibiting grumpy old man traits. I have been out of the loop for many years with this kind of development and tend to lose patience easily. That said, that I have built the latest TDE on vintage systems is remarkable. Dare I say that the 14.1 builds are running on Pentium I/II single core systems with less than 512 MB of RAM and a 3.10.107 kernel? A tad slow? Yes, but everything functions and the slowness is mostly caused by PATA drives. I am impressed with the developers far more than a grumpy old man being able to build TDE on vintage systems. Good job devs. :)

8 hours, 3 minutes

Proposed Wiki Changes

by Darrell Anderson

Please comment, clarify, or improve. Thanks. https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#About_TQt and https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#Configure_and… ADD: ==== Although c++11 (and c++17) are supported in TDE, users compiling automake packages for systems with older versions of gcc might require explicitly declaring compatibility with '-std=c++11'. ============ https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#Other_Require… ADD: ==== Many TDE packages add features based on installing additional distro packages. For many people this approach is encouraged for a more robust desktop environment, but a good starting point is with a clean stock distro install and add supporting packages as needed. To avoid potential conflicts, compiling TDE probably is best done in an environment that does not contain any KDE related packages. ============ https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#Coexisting_wi… and https://wiki.trinitydesktop.org/Tips_And_Tricks#Look_and_feel ADD: ==== Some stand-alone Qt5 software (not necessarily KDE software) might not render toolbars, fonts, and colors correctly within TDE. Some users have found that installing the 'qt5ct' package helps improve the appearance of Qt5 software. While the qt5ct environment variable QT_QPA_PLATFORMTHEME can be exported globally to all users system-wide, a more suitable place to export the variable is $TDEHOME/env/qt5ct.sh. This limits the effects of qt5ct to each user and allows each user to customize the desired Qt5 features as desired. ============ https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#Build_Times DELETE the section.

10 hours, 6 minutes

error: 'nullptr' was not declared in this scope

by Darrell Anderson

I'm trying to build R14.1.2 on some vintage systems. The build log for tqt3 is filled with this error. I searched the web and not being a programmer, do not fully understand what is required for remedy. The error seems to have something to do with c++11. R14.0.12 built fine on these vintage systems. I am presuming something has since changed. One system has gcc 5.5.0. I accept this might be the end of the road for TDE on some vintage systems. That's fine, but please, no street preaching about unsupported systems. I'm trying to understand the error. Thanks.

12 hours

tdelibs FTBFS

by Darrell Anderson

I'm building R14.1.2 on some older systems. R14.0.12 compiled fine on these systems. I am hoping the trick is back porting a patch or two. On a Slackware 14.2 64-bit system the build fails as so: [ 37%] Generating tdespell-en-handbook cd /tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/build-tdelibs/doc/tdespell && /tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/build-tdelibs/kdoctools/meinproc --srcdir=/tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/build-tdelibs/ksgmltools2 --check --cache index.cache.bz2 /tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/doc/tdespell/index.docbook /bin/sh: line 1: 22600 Bus error /tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/build-tdelibs/kdoctools/meinproc --srcdir=/tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/build-tdelibs/ksgmltools2 --check --cache index.cache.bz2 /tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/doc/tdespell/index.docbook doc/tdespell/CMakeFiles/tdespell-en-handbook.dir/build.make:60: recipe for target 'doc/tdespell/index.cache.bz2' failed make[2]: *** [doc/tdespell/index.cache.bz2] Error 135 make[2]: Leaving directory '/tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/build-tdelibs' CMakeFiles/Makefile2:10862: recipe for target 'doc/tdespell/CMakeFiles/tdespell-en-handbook.dir/all' failed make[1]: *** [doc/tdespell/CMakeFiles/tdespell-en-handbook.dir/all] Error 2 make[1]: Leaving directory '/tmp/build/tmp-tdelibs/tdelibs-trinity-14.1.2/build-tdelibs' Makefile:138: recipe for target 'all' failed make: *** [all] Error 2 What do I look for? Side note: Before any pedantic Horshacks pipe in, Slackware 14.2 was declared EOL Dec 2023. Thanks.

15 hours, 29 minutes

Build requirements

by Darrell Anderson

Where in the wiki are the expected build environment requirements listed (and not out of date)? I'm am trying to build TDE 14.1.2 on Slackware 15.0 32-bit. Fails to build because of a "Value too large for defined data type" error. This seems to be a specific 32-bit error. I have not read anything that 32-bit no longer is supported in TDE. I'm trying to build 14.1.2 on some vintage 32-bit systems. The tqt3 build fails with many errors and fatal errors. Cmake version 3.5.2 is installed but tqt3 does not use cmake. While vintage systems are EOL, R14.0.12 built fine on these systems. So something else has changed or was introduced since them. Thanks.

18 hours, 20 minutes

tdelibs FTBFS

by darrella＠clovermail.net

1 day, 8 hours

Refreshing to pick up recent fixes, but...

by J Leslie Turriff

...I'm getting this: | @17:34:40 root@pinto | wd=~ | ● zypper dup --from trinity-bin | Refreshing service 'NVIDIA'. | Refreshing service 'openSUSE'. | Retrieving repository 'update-sle (15.5)' metadata ...........................................[done] | Building repository 'update-sle (15.5)' cache ................................................[done] | Loading repository data... | Reading installed packages... | Computing distribution upgrade... | | Problem: 1: the installed trinity-tde-guidance-backends-debuginfo-2:0.8.0svn20080103-14.1.1_1.oss155.x86_64 requires 'trinity-tde-guidance-debuginfo(x86-64) = 2:0.8.0svn20080103-14.1.1_1.oss155', but this requirement cannot be provided | deleted providers: trinity-tde-guidance-debuginfo-2:0.8.0svn20080103-14.1.1_1.oss155.x86_64 | | Solution 1: deinstallation of trinity-tde-guidance-backends-debuginfo-2:0.8.0svn20080103-14.1.1_1.oss155.x86_64 | Solution 2: keep obsolete trinity-tde-guidance-debuginfo-2:0.8.0svn20080103-14.1.1_1.oss155.x86_64 | Solution 3: break trinity-tde-guidance-backends-debuginfo-2:0.8.0svn20080103-14.1.1_1.oss155.x86_64 by ignoring some of its dependencies | | Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0

3 days, 14 hours

status TDE python

by Dr. Nikolaus Klepp

Hi! What's the status of the TDE python interface? Is it usable/stable for small applications? Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...

4 days, 22 hours

New contributor

by Jan Sucan

Hello, I would like to start contributing to TDE. Would it be possible to make me a contributor in Gitea? I'm using the same e-mail address for my account there. Have a good day Jan Sucan

5 days

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels