<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">That is good news indeed. I have added this info on <a href="https://wiki.scummvm.org/index.php?title=Compiling_ScummVM/C++11_Readiness" class="">https://wiki.scummvm.org/index.php?title=Compiling_ScummVM/C%2B%2B11_Readiness</a></div><div class=""><br class=""></div><div class="">Would you be willing to take over providing the mac PPC release builds? Now that I no longer have a PPC mac, making and testing those is a pain for me, and I am not particularly motivated to update my toolchain to support c++11. I can still take charge of doing it for the 2.2.0 release using my old toolchain if you need time to prepare for it.</div><div class=""><br class=""></div><div class="">Thierry</div><br class=""><div><blockquote type="cite" class=""><div class="">On 4 Sep 2020, at 20:58, Joseph Davies <<a href="mailto:deledrius@hotmail.com" class="">deledrius@hotmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Great news for OSX PowerPC users: ScummVM continues to build and run<br class="">without error when this C++11 code is enabled.<br class=""><br class="">I successfully tested ScummVM in OSX 10.5.8, built using gcc 7.3.0<br class="">(installed through Homebrew). There were no compile errors, and all 259<br class="">tests completed as "OK" when running `make test`.<br class=""><br class=""><br class="">On 8/30/2020 7:30 AM, Eugene Sandulenko wrote:<br class=""><blockquote type="cite" class="">Hi Team, particularly porters,<br class=""><br class="">As I wrote today, ScummVM 2.2.0 has just been branched. I highly<br class="">encourage you trying building your ports now, before tagging, so if any<br class="">changes are needed, you could make them in time.<br class=""><br class="">Also, while you will be at it, please, try the following command for<br class="">testing compatibility of your port toolchain with C++11 standard<br class="">(unless you already did it and provided the info on the Wiki):<br class=""><br class=""> ./configure --enable-c++11 --enable-test-c++11 --disable-all-engines<br class=""><br class="">This should either compile well or die horribly during compilation.<br class="">Engines do not matter, this is why there is the option disabling them.<br class="">The results for most of our ports could be seen on this Wiki page:<br class=""><br class=""> <a href="https://wiki.scummvm.org/index.php?title=Compiling_ScummVM/C%2B%2B11_Readiness" class="">https://wiki.scummvm.org/index.php?title=Compiling_ScummVM/C%2B%2B11_Readiness</a><br class=""><br class="">I plan to have ScummVM switched to C++11 standard by default from 2.3.0<br class="">and announce allowing its features everywhere, starting from our common<br class="">code.<br class=""><br class="">That means that some ports will, unfortunately, have 2.2.0 as their last<br class="">release. It's a pity, but the ancient C++ standard is holding us down at<br class="">the moment.<br class=""><br class=""><br class="">Eugene<br class=""><br class="">_______________________________________________<br class="">Scummvm-devel mailing list<br class=""><a href="mailto:Scummvm-devel@lists.scummvm.org" class="">Scummvm-devel@lists.scummvm.org</a><br class="">https://lists.scummvm.org/listinfo/scummvm-devel<br class=""><br class=""></blockquote>_______________________________________________<br class="">Scummvm-devel mailing list<br class=""><a href="mailto:Scummvm-devel@lists.scummvm.org" class="">Scummvm-devel@lists.scummvm.org</a><br class="">https://lists.scummvm.org/listinfo/scummvm-devel<br class=""></div></div></blockquote></div><br class=""></body></html>