Skip to content

Add notes for iOS compiling documentation #3594

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.

Sign up for GitHub

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

Open
ann0see wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −2
Open

Add notes for iOS compiling documentation #3594

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions COMPILING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
- For unattended installs, see the contributed [installation scripts](https://github.com/jamulussoftware/installscripts)
- The [Autobuild scripts](https://github.com/jamulussoftware/jamulus/tree/main/.github/autobuild) although only optimized to be used by the CI, might help you understand the process of setting up a build environment
- There are reports from people who successfully compile and run Jamulus on BSDs.
- Android and iOS are not officially supported. However, [binaries are generated by the autobuild process](https://github.com/jamulussoftware/jamulus/releases/latest) in the Jamulus repository.
- Android and iOS are not officially supported fully. However, [binaries are generated by the autobuild process](https://github.com/jamulussoftware/jamulus/releases/latest) in the Jamulus repository.

---

Expand Down Expand Up @@ -157,7 +157,7 @@ If you want to build the installer, please run the `deploy_mac.sh` script: `./ma
## iOS

1. Install [Xcode from the Mac AppStore](https://apps.apple.com/us/app/xcode/id497799835?mt=12)
Copy link
Collaborator

@pljones pljones Jan 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just out of interest, how close are these steps to the autobuild process? Do the dependencies and versions match, etc?

Copy link
Member Author

@ann0see ann0see Jan 12, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe they're different. The autobuild process uses Qt 6 and some hacks to generate an unsigned ipa. Xcode itself produces a signed binary which is installed to device or uploaded to AppStore Connect. I also use Qt5 as QT6 is buggy UI wise.

Copy link
Collaborator

@pljones pljones Jan 13, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I think we need to change autobuild to do the same thing, then.

EDIT: Added this in a new issue

2. [Download and install Qt5 with the Qt Installer](https://www.qt.io/download) (not homebrew). Explicitly select iOS when choosing the Qt version
2. [Download and install Qt5 with the Qt Installer](https://www.qt.io/download) (not homebrew, Qt6 is found to be buggy). Explicitly select iOS when choosing the Qt version
3. Go to the folder of the Jamulus source code via terminal and run `/path/to/qt/5.15.2/ios/bin/qmake -spec macx-xcode Jamulus.pro` to generate an .xcodeproject file
4. Open the generated .xcodeproject in Xcode
5. Go to the Signing & Capabilities tab and fix signing errors by setting a team. Xcode will tell you what you need to change.
Expand Down