> On Dec 4, 2025, at 14:39, Robert Helling <[email protected]> wrote: > > Hi Dirk, > >> On 3. Dec 2025, at 23:30, Dirk Hohndel <[email protected]> wrote: >> >> cmake thinks that it should look for Qt in /usr/local/lib -- which is not >> something that is set anywhere in my script. >> When you run env | grep /usr/local/lib in your shell, what do you get? >> > > I get nothing. My $PATH is > PATH=/Users/Helling_1/Qt/6.10.1/macos/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/X11/bin:/Library/Apple/usr/bin:/usr/local/MacGPG2/bin:/Applications/Wireshark.app/Contents/MacOS:/usr/local/munki:/Applications/nmap.app/Contents/Resources/bin:/Applications/ncat.app/Contents/Resources/bin:/Applications/nping.app/Contents/Resources/bin:/Applications/zenmap.app/Contents/Resources/bin > > and there is no other variable that has any interesting path information in > it. > > Unfortunately, I don’t quite understand what Thiago was saying or better what > that means what I should do.
Essentially what Thiago is saying is that make will by default always look in the path where Homebrew drops their Qt. So you have to uninstall the Homebrew Qt build before this will work. Obviously (I can explain to anyone to who, this isn't obvious) we don't want to build our binaries with Homebrew. But I guess to make it easier for people who approach their computer with "but everyone does it that way" I guess I need to figure out how to make Subsurfacec build on a Mac using the Homebrew parts because this is just too painful for words. Dang. I was actually trying to make some progress instead of spending yet more time on build infra stuff... /D
_______________________________________________ subsurface mailing list -- [email protected] To unsubscribe send an email to [email protected]
