On 5/20/24 2:08 PM, Slávek Banko via tde-devels wrote:
Oh, clearly, for TQt as such, there is not forced C++ dialect, because it
does not use either automake (common admin module) or CMake. In R14.0.12,
C++11 dialect was set as default for both automake and CMake. Together
with the release R14.1.0 there is allowed to use C++11 in code. Therefore,
TQt >= R14.1.0 now requires to enforce C++11 dialect if an older compiler
is used.
Basically then my remedy is correct?
I don't mind and I am not going to make mountains out of molehills, but
information like this should be in the wiki. I don't know if I still
have write access to the wiki, but at my stage of relearning TDE
development I am more comfortable with suggesting changes rather than
presuming and writing incorrect information.
Overall, the requirements have not changed too much. We always try to keep
the code for compatibility with older versions, because we still provide
packages for older versions of distribution.
And I'm thankful. Some people like tinkering with old cars or furniture.
I like tinkering with old computers. I even have a 486 with 16 MB of RAM
still running. :) Because TDE remains quite snappy and responsive
(almost frighteningly fast), I have a natural tendency to try to keep
TDE running on these vintage systems. I realize that perhaps someday
there will be a point of no return, but I'd like to think that day has
not yet arrived. Challenging for me is finding and learning which
patches to back port.
Very good changes have occurred for build times, especially for CMake if
used together with ninja-build. In this case, processors with multiple
cores are very well used and building can be significantly faster than it
used to be in the past.
Perhaps the wiki section about build times should be deleted?
____________________________________________________
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
