svxlink
svxlink copied to clipboard
sm0svx
SVXLINK should switch to using >=SigC++-3
At the moment the package still uses sigc++-2.xxx. That forces the build system to use an old C++ standard (-std=c++11) which is a main stumbling block for a port of Qtel to Qt6 as that will require a C++17 compiler (see Issue #686).
Switching to sigc++-3.xxx would allow to use the more modern C++17.
As I and some others generally build without QT in the CMAKE command, this has no effect even using 24.02. but maybe in the future this will have to be considered.
On Mon, 3 Mar 2025, 14:09 Thomas Beierlein, @.***> wrote:
At the moment the package still uses sigc++-2.xxx. That forces the build system to use an old C++ standard (-std=c++11) which is a main stumbling block for a port of Qtel to Qt6 as that will require a C++17 compiler (see Issue #686 https://github.com/sm0svx/svxlink/issues/686).
Switching to sigc++-3.xxx would allow to use the more modern C++17.
— Reply to this email directly, view it on GitHub https://github.com/sm0svx/svxlink/issues/695, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5GQQMBE2OSCER77GLT2SRPANAVCNFSM6AAAAABYHDSS32VHI2DSMVQWIX3LMV43ASLTON2WKOZSHA4TCMZVHA4TMMY . You are receiving this because you are subscribed to this thread.Message ID: @.***> [image: dl1jbe]dl1jbe created an issue (sm0svx/svxlink#695) https://github.com/sm0svx/svxlink/issues/695
At the moment the package still uses sigc++-2.xxx. That forces the build system to use an old C++ standard (-std=c++11) which is a main stumbling block for a port of Qtel to Qt6 as that will require a C++17 compiler (see Issue #686 https://github.com/sm0svx/svxlink/issues/686).
Switching to sigc++-3.xxx would allow to use the more modern C++17.
— Reply to this email directly, view it on GitHub https://github.com/sm0svx/svxlink/issues/695, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5GQQMBE2OSCER77GLT2SRPANAVCNFSM6AAAAABYHDSS32VHI2DSMVQWIX3LMV43ASLTON2WKOZSHA4TCMZVHA4TMMY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
It's a bit of work to switch to libsigc++3 but doable. It has to be done sooner or later so it's more of a matter of how long older systems should be supported. I'd like to make one more release with C++11 and then move forward. But I'm not quite ready to make a new release just yet.
While not complete yet, at least the part needed to compile qtel seems to be ok. That allows me to start to work on the Qt6 port.
Great. Thanks. Any timeline for a new release? Otherwise I will prepare a patched version for Gentoo so we can move away from qt5.
A release is at least a couple of weeks away and maybe more. Depends on how much free time I have to work on this project. So I cannot give any promises.