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_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'.
============
https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#Other_Requirements
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_with_QT5.2FKDE_Plasma
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.
____________________________________________________
tde-devels mailing list -- devels@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devels-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@xxxxxxxxxxxxxxxxxx
