> On Dec 2, 2025, at 01:15, Robert Helling <[email protected]> wrote: > > and miraculously, now works. I had tried a number of things, run macqtdeploy, > found that two frameworks were only symlinked with dodgy relative paths into > the home-brew Cellar, blew away the Subsurface.app, ran make again in the > build directory. I don’t know what did the job, but now it runs. > > I will try this again on my office Mac later today and see if I can reproduce > these steps. > > Status is: No printing, the map is white. There is a menu entry for the user > manual but clicking on it opens a window saying "Cannot find the Subsurface > manual“. > > But this is so much better than anything I had before on Mac in a long long > time!
Well, we're making progress. How did you install Qt 6 ? I worry that you may have done so using home-brew which would explain some of your problems. Please install the actual Qt Company macOS version, ideally in a separate path like /opt/Qt/ , and then call the build process again (the full script), starting with an empty directory. I want to make sure we really sort out the dependencies and make this truly reproducible. For example, at no point in the process should there have been a y/n question for you to answer... The binary this produces (tested with the official Qt 6.8.3 binaries and the official Qt 6.10.1 binaries) has working maps, working bluetooth, working MTP, working ftdi (all tested here). As for the user manual, I am half way there with a replacement solution for that. It's not perfect, but will likely meet the "good enough" standard. As for printing, I'm looking at options, but let's repeat myself, just in case this wasn't clear earlier: QtWebEngine is not an option. We can remove that from the build to simplify the source code. Adding 10x the size of everything else in the combined bundle for printing is not remotely reasonable. So let's please not spend any more time on this. /D
_______________________________________________ subsurface mailing list -- [email protected] To unsubscribe send an email to [email protected]
