SDK with newer GCC that supports c++17 standard?

Definitely good progress! I am waiting for new SDK to start using c++14 :-) Did you considering howto handle ABI switch in the future? I am not even sure where it may cause troubles and if it is possible to build all c++ libraries (Qt for example) with dual ABI...

I guess you mean https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html

That should not cause too much harm. Exact details are still pending until we are closer with the next gcc upgrade.

See also: https://developers.redhat.com/blog/2015/02/05/gcc5-and-the-c11-abi/

Hi Sage! I was able to build GCC 8.3 for Sailfish OS (https://build.merproject.org/package/show/home:equeim:gcc and https://build.merproject.org/project/show/home:equeim:cross-gcc), it is configured to use old ABI by default. Currently I'm testing building my apps with it, and deploying RPM with its own libstdc++ and setting rpath for executable. Everything seems to work fine, but I'm in doubt, are there any pitfalls that I'm not aware about?

Hi equeim, that is just the one of the very first steps what you did. Would need to build the whole core OS with your new toolchain including the crosstoolchains and supporting packages. So basically taking e.e. whole core os build all packages there, add your gcc into the mix that installs on top of the current gcc and then fix the fallout. Most likely you need to touch somewhere between 20-200 packages to get that gcc fully building the OS as that is so huge step forward.

With the gcc update to 4.9.4 we did the same, here are few (by no means all) pull request showing what kind of changes we did previously:

https://git.sailfishos.org/mer-core/gcc/merge_requests/7/diffs

https://git.sailfishos.org/mer-core/buteo-mtp/merge_requests/22//diffs

https://git.sailfishos.org/mer-core/libiodata/merge_requests/2/diffs

https://git.sailfishos.org/mer-core/maliit-framework/merge_requests/7/diffs

https://git.sailfishos.org/mer-core/nemo-qml-plugin-systemsettings/merge_requests/100/diffs

Br, Sage

I'm not saying that rebuilding a system with newer compiler is not neccassary, it's obviously a must and you're doing a ton of work to make it possible. I'm just interested in building apps using newer compiler while remaining compatibility with OS versions that was built with older compiler. Also, do I understand it correctly that when you will update to newer (post 5.0) GCC version you will keep building system with GCC 4 language/libstdc++ ABI to remain compatible with third party apps? Or will you break compatibiluty someday?