<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">OK, since I had a day off today I didn't only finish 5.0.4, I also decided to at least poke a toe into this mess.<div class=""><br class=""></div><div class="">The summary of what I've learned so far?</div><div class=""><br class=""></div><div class="">UGH.</div><div class=""><br class=""></div><div class="">QtWebKit doesn't work with Qt 6 and it appears that no one is interested in porting that monster.</div><div class="">Frankly, I can't blame them.</div><div class=""><br class=""></div><div class="">Which means that we can't support printing with Qt 6.</div><div class=""><br class=""></div><div class="">The rest of the changes seemed like they should be doable in a few days of just hunting the build errors and warnings down - nothing seems catastrophic.</div><div class=""><br class=""></div><div class="">Adding Qt 6 support should give us Apple M1 support, support for additional localizations of the base widget (e.g., Dutch). But frankly not a lot more that I can identify.</div><div class="">The amount of work needed to upgrade our build infrastructure to Qt 6 for Windows, Mac, AppImage, Android, iOS... I really don't even want to contemplate it.</div><div class=""><br class=""></div><div class="">So my current plan continues to be "stay on Qt 5.15 for as long as I possibly can". After all, the major Linux distros are mostly still shipping Qt 4 :)</div><div class=""><br class=""></div><div class="">/D<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 15, 2021, at 12:05 PM, Dirk Hohndel via subsurface <<a href="mailto:subsurface@subsurface-divelog.org" class="">subsurface@subsurface-divelog.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Oct 15, 2021, at 9:55 AM, Robert Helling wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class="">has anybody managed to build Subsurface on Apple Silicone? Because I haven’t.<br class=""></div></div></blockquote><div class=""><br class=""></div>Yeah, I still don't have a Mac with M1 silicon, so no, haven't even tried... my understanding is that the x86 version works just fine, though...</div><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div class="">Here is a log of my frustrations.<br class=""><br class="">Before leaving for the summer vacation, I received a new MacMini at the office featuring the new ARM based Apple hardware that everybody is so excited about. It runs Big Sur.<br class=""><br class="">It took several weeks to find the time to properly take care of it, install all the software I need for work, get permissions right (it seems they changed what admin users can do when the machine is part of an active domain or better what they cannot do, for example install software updates etc etc). But those things I think I have under control by now.<br class=""><br class="">So I move forward and tried to set up a build environment for Subsurface. I encountered halve installed versions of Xcode which on the other hand leave behind zombi installations when removed that confuse auto build when still around when there is a second version as well (this took me two days to understand). But also that is solved. I think.<br class=""></div></div></blockquote><div class=""><br class=""></div><div class="">This might be good to document in more detail, especially how to fix it (for the next poor person coming around to this)</div><div class=""><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class="">But now I hit a road block: I am able to build the subsurface object files. But then I came to the understanding that Qt 5.x does not exist in version for Apple’s ARM processors, only for the 86 family (which could be used in Rosetta mode and indeed the official Mac binaries from Dirk’s server work fine on that machine). But I have not been able to convince the Subsurface build system to build 86 family binaries on my ARM machine.<br class=""></div></div></blockquote><div class=""><br class=""></div>No idea how to do that, frankly. I'm sure you've found this page <a href="https://www.qt.io/blog/qt-on-apple-silicon" class="">https://www.qt.io/blog/qt-on-apple-silicon</a> and if you wanted to experiment with Qt6 there's more stuff here <a href="https://doc.qt.io/qt-6/macos.html" class="">https://doc.qt.io/qt-6/macos.html</a></div><div class=""><br class=""></div><div class="">I think eventually we will need to port to Qt 6 - and that should fix the core of your problem, right?</div><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div class="">So I see three options to move forward: „Cross-build“ Subsurface for the old hardware platform. Or wait for ARM built binaries of Qt 5.x (which as I understand might never happen at least in the open source world). Or move Subsurface forward to work with Qt 6 (which might be in better shape w.r.t. ARM but I don’t really understand the current situation in detail).<br class=""></div></div></blockquote><div class=""><br class=""></div>I think you have that right. Allegedly one can build "fairly decent" Qt 5.15 binaries for M1. Just takes a while :)</div><div class=""><br class=""></div><div class="">But really, the only logical path is Qt6</div><div class=""><br class=""></div><div class="">/D</div><br class=""></div>_______________________________________________<br class="">subsurface mailing list<br class=""><a href="mailto:subsurface@subsurface-divelog.org" class="">subsurface@subsurface-divelog.org</a><br class="">http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface<br class=""></div></blockquote></div><br class=""></div></body></html>