Hi Dirk,
> On 2. Dec 2025, at 16:13, Dirk Hohndel <[email protected]> wrote:
>
> 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.
This so far did not work: I had downloaded a fresh Qt using Qt’s own installer
and placed it in ~/Qt but that was not picked up. On my work Mac, this lead to
a build failure but once I had installed qt@6 using homebrew the build
succeeded (similar for libftdi). I did not create any symlinks (wasn’t that
required at some point in the past?). How can I force it to use the Qt in my
home directory?
>
> 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.
Which direction are you pursuing here?
>
> 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.
>
understood.
What is the perspective regarding Webkit and Qt6?
Best
Robert
_______________________________________________
subsurface mailing list -- [email protected]
To unsubscribe send an email to [email protected]
