Skip to content
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

Xcode build crashes if PlugIns directory is not present #3078

Open
ann0see opened this issue Jun 5, 2023 · 4 comments
Open

Xcode build crashes if PlugIns directory is not present #3078

ann0see opened this issue Jun 5, 2023 · 4 comments
Labels
bug Something isn't working macOS macOS runtime issue

Comments

@ann0see
Copy link
Member

ann0see commented Jun 5, 2023

Describe the bug

The Xcode build of Jamulus after the merge of #3076 crashes with the error message - allocated port number: 22134 qt.qpa.plugin: Could not find the Qt platform plugin "cocoa" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

To Reproduce

Compile Jamulus with Xcode. To do so run qmake -spec macx-xcode Jamulus.pro
Run the app via Xcode and observe a crash. Running the binary from the command line from the Debug folder gives this error message.

Strange enough, if the I build with qmake Jamulus.pro; make the created binary works as expected but doesn't seem to have a PlugIns directory in Jamulus.app/Contents. If I copy the PlugIns directory from a previous build to the crashing build, everything works.
Expected behavior

Xcode builds don't crash
Screenshots

/
Operating system

macOS 13.4; Xcode 14.2
Version of Jamulus

Build form 10c7eaf4a7ecb59c6a79dd65f3bd6bd172e217dd
Additional context

this Mac runs an unsupported version of macOS, so it could be another issue (dortania/OpenCore-Legacy-Patcher#1046) but I doubt that.

@ann0see ann0see added the bug Something isn't working label Jun 5, 2023
@ann0see ann0see changed the title Xcode build crashes if PlugIns directory misses Xcode build crashes if PlugIns directory is not present Jun 5, 2023
@ann0see
Copy link
Member Author

ann0see commented Aug 20, 2023

Maybe macdeployqt must be run somehow

@ann0see
Copy link
Member Author

ann0see commented Jul 30, 2024

Maybe copying missing files from a successful build via deploy_mac.sh works?

@ann0see
Copy link
Member Author

ann0see commented Jul 30, 2024

@ann0see
Copy link
Member Author

ann0see commented Aug 10, 2024

Ok. It seems that you must run macdeployqt on the produced binary on macOS. Maybe this can be incorporated somehow in the Xcode build process? If I run macdeployqt, the app starts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working macOS macOS runtime issue
Projects
Status: Triage
Development

No branches or pull requests

2 participants