-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
OSX daily builds crash on startup #11999
Comments
Tried building master without gstreamer and that doesn't seem to work any more:
Used to be that build would detect no gstreamer framework installed and build a version automatically without it. |
I tried going to the dev guide for building to see what the new rules are but that doesn't seem to be current. This "Video Streaming/Gstreamer: - see Video Streaming." just goes to a 404 now. Not sure what the current state of affairs is with respect to gstreamer installs. |
@DonLakeFlyer these errors all mention exiv2. Maybe I should revert to before using that. Could you also try a built from before exiv2? |
Actually nevermind it gets built as a shared lib then doesn't get copied over when deployed, #12005 should fix that. Also in regards to gstreamer, yeah I guess currently you would have to disable build with gstreamer in the options. I can get it to just build without gstreamer, but I also feel like they should have to disable building with gstreamer to acknowledge it won't have it, rather than just be surprised because they didn't read the configure output log. |
Ah, I saw it poking around in the gstreamer framework! That it was that.
Make sense. Can you update the dev guide with respect to how you are supposed to build with/without gstreamer? |
Is this resolved now with the static lib thing? |
Tried daily again. Crashing in a different way:
|
Oof, okay. apparently something else not being copied over. I'll check it out tonight |
Can you try an artifact from #11971? I think that should fix this |
Whack-a-mole :)
|
So the frustrating part is setting the gstreamer environment variables based on whether you are just running a build or are running from an installation, because for the first case you want to pull from the system's gstreamer and in the second case you want to pull from the app's included gstreamer. Basically if you have it set up to work one way, it won't work the other way. Note the ifdef QGC_INSTALL_RELEASE here. For an appimage on linux, you can define these environment variables in a custom script that gets run at the start of the appimage. However for MacOS and DMG's, I have no idea how to approach this |
Can't you just go back to sort of what the old qmake build did: |
Yeah, just trying to keep it as automated and simple as possible. I'm hoping I solved this in master now, apparently you can set environment variables in the plist file so that's a potential solution as well. I really just need to get a MacOS system from ebay or something so it's easier for me to test |
Install latest OSX daily build from web site. Boot and it will crash on startup:
The text was updated successfully, but these errors were encountered: