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_Requirem...
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_wit... 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.
On Monday 20 of May 2024 23:30:59 Darrell Anderson via tde-users wrote:
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_Build
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'.
The need to add -stt=c++11 does not apply to building with automake - there the option should be automatically added. This applies only to TQt3 as such, because it does not use either automake or cmake.
See rules in common admin module:
http://git.trinitydesktop.org/cgit/admin/commit/?id=a7f75ac0ff http://git.trinitydesktop.org/cgit/admin/commit/?id=b9fb6ca397
Cheers
See rules in common admin module:
http://git.trinitydesktop.org/cgit/admin/commit/?id=a7f75ac0ff http://git.trinitydesktop.org/cgit/admin/commit/?id=b9fb6ca397
From what I can see, the admin module directory should exist in the top level of the tarball source file. The admin module should contain both files regardless of building with cmake or automake.
In my case, the tqt3 source tarball I downloaded does not contain an admin module directory, which could explain the build failure and the related message thread.
I downloaded the tarballs from here:
https://mirror.ppa.trinitydesktop.org/trinity/releases/R14.1.2/R14.1.2-compl....
I just checked again and there is no admin module directory, configure.in.min, or acinclude.m4.in.
Am I missing the big picture configuring tqt3 or is the admin module directory missing in the upstream tarball? I'd like to straighten this out before making more noise. :)
Thanks.
Darrell Anderson via tde-users wrote:
Am I missing the big picture configuring tqt3 or is the admin module directory missing in the upstream tarball? I'd like to straighten this out before making more noise. :)
I think Slavek mentioned that for tqt3 there is no admin module.
you have the configure script and that is all. The configure is called from the build system of the Distro you use. Those build scripts are kept in packaging https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging
On 5/20/24 5:38 PM, deloptes via tde-users wrote:
Am I missing the big picture configuring tqt3 or is the admin module directory missing in the upstream tarball? I'd like to straighten this out before making more noise. :)
I think Slavek mentioned that for tqt3 there is no admin module.
you have the configure script and that is all. The configure is called from the build system of the Distro you use. Those build scripts are kept in packaging https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging
There's nothing in the Slackware section, but I browsed through some of the other files. I don't see how -std=c++11 gets added to tqt3 without an admin module directory.
-
Darrell Anderson -
deloptes -
Slávek Banko