-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
brewtarget 4.0.1 doesn't work on macOS #809
Comments
Thanks for all the debug info. Do you have the log file too? |
It looks like it doesn't even get far enough to start the logging. See below, I removed. the log file tried to launch v4.0.1 and there is still no log file. I then launched v3.0.11 (which works) and the log file is populated.
|
I should add that when I first install v4.0.1 and try to run it I get this error: After googling I came across this post on the macOS community and so ran It's only then that I get the error reported above: |
Hmm, I wonder if we have to work out how to sign the app - at least that seems to be what's suggested at ahrm/sioyek#806 |
I was able to build 4.0.1 on my mac and it runs successfully. However, my mac architecture is arm64 not x86-64 so I had to change one line in
Perhaps you could try the following to include both architectures I don't know if this is really the underlying problem with the release macOS build; perhaps the code signature issue doesn't apply when you build and run locally but for now this is enough for me to move to v4. |
Ah, OK, brilliant. Glad you got it working. Will have a look at the compiler flags. Maybe we can do an Arm and an Intel build. |
Just a quick note to say I haven't forgotten about this. From what I understand we definitely need to think about separate ARM and Intel builds. I read that the ARM Macs can run Intel binaries, but not the other way around. At the moment, I'm leaning towards thinking we should ship ARM binaries and then encourage anyone still on Intel (which is hardware over 4 years old) to build from source - mainly because GitHub MacOS actions run on ARM hardware. (I'm sure we'd be able to cross-compile Intel binaries on ARM, but I'm less sure about how easy it would be to do Intel packaging on ARM hardware.) |
No worries. I did manage to build 4.0.7 locally on my mac so that's still good enough for me right now. I also have an Ubuntu VM on the ARM Mac where I can do an Ubuntu build on ARM architecture. Since 4.0.7 this build is crashing on startup with |
Ah, hmm, interesting. Could be all sorts of things for the problem on ARM Ubuntu. Might have to wait until someone with the relevant hardware is able to reproduce and dig into the stack trace in the core file. But, in the meantime, if it's not blocking you, that's good. |
OK, to come back to the MacOS issue, from what I've been able to glean from various sources, it's not a compilation or packaging issue that we can resolve (without at least paying Apple some money). The suggestions are to run the following two commands (ie the one you mentioned before and an additional one) in the console (with the appropriate substitution for
This assumes you have Xcode already installed. If you get a chance to try this at some point, I'd be keen to hear how you get on. |
Still aborts on startup but it's a different reason. Is there some QT library missing? I did install QT6 with
I wonder could this be the root of the problem? |
I should also add that to build locally since the move to Qt6 I've had to comment out line 621 ( If I don't I get this error running
|
After installing Qt 6, there are some other things you need to do to make the compilation work on Mac, including:
and
Alternatively, if you go to the top directory of Brewtarget and run |
I got an |
I tried 4.09 on an M1 Macbook... I run into a missing Qt Library... The Entire QtDBus.framework directory isn't present in /Applications/brewtarget_4.0.9.app/Contents/Frameworks
|
Ah, hmm, OK. That's interesting. Looks like we're missing a library. Will try the fix at https://doc.qt.io/qt-6/macos-issues.html#d-bus-and-macos. |
Hold up... I didn't notice the other missing QtNetwork.framework and only cut & pasted the DBus one... Here's the rest:
|
If you have homebrew installed, could you try:
And then rerun Brewtarget and see if it makes any difference? |
Already had dbus... Adding dbus-glib didn't seem to make a difference:
|
Thanks for trying this. I've been doing some more digging. It turns out we are getting some errors during Mac packaging from the |
Brewtarget 4.0.1 quits on startup on macOS:
The details from clicking on
Report..
are:The text was updated successfully, but these errors were encountered: