> On Dec 5, 2025, at 07:21, Thiago Macieira via subsurface
> <[email protected]> wrote:
>
> On Friday, 5 December 2025 05:55:00 Pacific Standard Time Robert Helling via
> subsurface wrote:
>> ... if it is just me, don't waste any further time on this! I have a build
>> using the homebrew supplied Qt whose only flaw is that it doesn't have the
>> map. I can totally live without that. In any near future, I am not going to
>> work on the map, so I don't care. If I want a map, I can still use the
>> binaries from github or use my Linux computer. I am totally happy with that
>> situation. And if I really wanted, I could always brew uninstall qt@6.
>>
>> Thanks for your help, I can build again. That is really all I wanted.
>
> I might have misunderstood your problem. I thought you had only one Qt and
> you
> had forgot to install it.
>
> You have two: one you've built using Dirk's scripts, and one by Homebrew.
> When
> compiling Subsurface against the Qt you compiled, it looks for stuff from
> Homebrew. Is this it?
The problem is that our build script up until my recent change really, really
wanted to
build a self-contained Subsurface.app with all the dependencies insides. And
that in
several situations, when you had both a Qt Maintenance Tool installed Qt
version and
a Homebrew-installed Qt version, you ended up with a mixture that broke things.
And I read your comments to state that the reason for that was that the
Homebrew one
ended up in a path that cmake always looked at first.
But since the self-contained binary really only matters when creating artifacts
that we
can give to users, I decided to flip the other way and encourage regular
developers to
simply use the Homebrew installed dependencies.
That's what my last comment was about. I don't think that branch is quite ready
to be
merged, yet, but we are getting there... and anyone building for Mac right now
should
definitely be using that branch.
/D
_______________________________________________
subsurface mailing list -- [email protected]
To unsubscribe send an email to [email protected]
