<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="">Hi Dirk,<div class=""><br class=""></div><div class="">thank you very much for all your help and all your comments!<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 12. Sep 2021, at 22:09, 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="">Ahh yes... the usual experience... time for my rant of how much I hate maintaining all these builds....<div class="">I honestly try to keep things working with the GitHub actions, but it's just so unbelievably frustrating and tedious.</div><div class="">So, let's see, how do I currently build Subsurface-mobile for iOS...</div><div class=""><br class=""></div><div class=""><font face="Courier New" class="">git clone <a href="git://github" class="">git://github</a>.com/subsurface/subsurface</font></div><div class=""><font face="Courier New" class="">ln -s PATHTOQTFORIOS ./Qt</font></div><div class=""><div class=""><br class=""></div><div class="">Then run essentially the following in as a script:</div><div class=""><br class=""></div><div class=""><font face="Courier New" class="">QT_PATH="$(cd Qt ; ls -d 5.*/ios/include/QtCore/5* | tr '.' '_')"</font></div><div class=""><font face="Courier New" class="">QT_VERSION=${QT_PATH##*/}</font></div><div class=""><font face="Courier New" class=""><br class=""></font></div><div class=""><font face="Courier New" class="">if [ ! -d build-Subsurface-mobile-Qt_${QT_VERSION}_for_iOS-Release ] ; then</font></div><div class=""><font face="Courier New" class=""> echo "cannot find the build folder build-Subsurface-mobile-Qt_${QT_VERSION}_for_iOS-Release"</font></div><div class=""><font face="Courier New" class=""> echo "creating a new one"</font></div><div class=""><font face="Courier New" class="">fi</font></div><div class=""><font face="Courier New" class="">mkdir -p build-Subsurface-mobile-Qt_${QT_VERSION}_for_iOS-Release</font></div><div class=""><font face="Courier New" class=""><br class=""></font></div><div class=""><font face="Courier New" class="">TOP=$(pwd)</font></div><div class=""><font face="Courier New" class="">cd subsurface</font></div><div class=""><font face="Courier New" class="">bash packaging/ios/build.sh</font></div><div class=""><br class=""></div></div></div></div></blockquote><div><br class=""></div><div>This brings me back to yesterday’s error with the architecture confusion.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class="">Now start Xcode and open the Xcode project in <span style="font-family: "Courier New";" class="">build-Subsurface-mobile-Qt_${QT_VERSION}_for_iOS-Release/Subsurface-mobile.xcodeproj</span></div><div class="">You should be able to build and run that on your device.</div></div></div></div></blockquote><div><br class=""></div><div>The problem is, there is no xcodeproj file. This is supposed to be created by some qmake run at some point, isn’t it?</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><br class=""></div><div class="">I do this on macOS 10.15 because macOS 11 is a pile of bovine excrement and breaks so many things it's not even funny.</div><div class="">And of course I do this on an Intel mac, not an m1 one.</div><div class="">None of this is to say that this wouldn't work with macOS 11 or with an m1 mac, it's just that can't tell you one way or the other.</div></div></div></div></blockquote><div><br class=""></div><div>I am trying this on an old intel MBP with Big Sur...</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Sep 12, 2021, at 7:34 AM, Robert.Helling <<a href="mailto:robert@neu.atdotde.de" class="">robert@neu.atdotde.de</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">I had a Sunday afternoon free, so I wanted to give it a shot. Addiert the capability to receive files based on mime-type from other apps seems not to require greater magic according to </div><div class=""><br class=""></div><div class=""><a href="https://www.qt.io/blog/2018/02/06/sharing-files-android-ios-qt-app-part-3" class="">https://www.qt.io/blog/2018/02/06/sharing-files-android-ios-qt-app-part-3</a></div></div></div></blockquote><div class=""><br class=""></div>Yes, all of these things are super easy and if the blog post you follow is older than approximately 6 weeks the likelihood of this still working as documented is similar to correctly predicting the Lotto numbers.</div><div class="">Since February 2018 our iOS build broke four times IIRC. Which is better than Android where absolutely everything changed and broke and nothing from 2018 is even remotely related to the way things need to be done today.</div><div class="">Also, both stores have dramatically tightened their rules for absolutely everything since then...</div><div class=""><br class=""></div><div class="">So, yeah, sure, this might work. In my experience it will be weeks of trial and error and googling before it works in reality. And that thing will be broken within a year.</div><div class=""><br class=""></div><div class="">But hey, that's just my cheerful outlook on the joy of how we support our mobile platforms :)</div></div></div></div></blockquote><div><br class=""></div><div>Hurray!</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div></div></div></blockquote><div class=""><br class=""></div><div class="">Oh, so you are talking about building mobile-on-desktop? That's a different can of worms.</div><div class=""><br class=""></div><div class="">rule #1 on macOS - you always, always need to run <font face="Courier New" class="">make install</font> - it sometimes magically works without it, but usually it fails with weird errors.</div></div></div></div></div></blockquote><div><br class=""></div><div>I can report that at least this did the job. mobile on desktop now runs (but isn’t helpful for the gpx issue as we both noted before, I was only afraid that this is somehow a prerequisite for the iOS build).</div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Rather cd to packaging/ios and run ./build.sh from there.</div><div class=""><br class=""></div><div class="">I am at a point where this fails with the kirigami libraries:</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">+ /Users/Helling/Qt/5.14.0/ios/bin/qmake /Users/Helling/mobile4/subsurface/mobile-widgets/3rdparty/kirigami/kirigami.pro CONFIG+=release</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Info: creating stash file /Users/Helling/mobile4/kirigami-build/.qmake.stash</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Project ERROR: Cannot run target compiler '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++'. Output:</span></div></div></div></div></blockquote><div class=""><br class=""></div><div class="">From the error it seems to simply be confused. Try following the steps above. Before you do that, make sure that you have the current Xcode and that you started it at least once to make sure you clicked on all the accept buttons that it throws at you.</div></div></div></div></div></blockquote><br class=""></div><div>That’s what I thought as well but Xcode seems to be uptodate and also the command-line-tools. I guess what I really need is to get the xcodeproj file somehow.</div><div><br class=""></div><div>Will keep trying. Later.</div><div><br class=""></div><div>Best</div><div>Robert</div><br class=""></div></body></html>