The macdeployqtplus.py
script should not be run manually. Instead, after building as usual:
ninja osx-zip
When complete, it will have produced Bitcoin-ABC.zip
.
Xcode.app
A free Apple Developer Account is required to proceed.
Our macOS SDK can be extracted from Xcode_15.xip.
Alternatively, after logging in to your account go to ‘Downloads’, then ‘More’
and search for Xcode 15
.
An Apple ID and cookies enabled for the hostname are needed to download this.
The sha256sum
of the downloaded XIP archive should be 4daaed2ef2253c9661779fa40bfff50655dc7ec45801aba5a39653e7bcdde48e
.
To extract the .xip
on Linux:
# Install/clone tools needed for extracting Xcode.app
apt install cpio
# Unpack the .xip and place the resulting Xcode.app in your current
# working directory
python3 contrib/apple-sdk-tools/extract_xcode.py -f Xcode_15.xip | cpio -d -i
On macOS:
xip -x Xcode_15.xip
Xcode.app
To generate the SDK, run the script gen-sdk
(./gen-sdk
) with the
path to Xcode.app
(extracted in the previous stage) as the first argument.
./contrib/macdeploy/gen-sdk '/path/to/Xcode.app'
The generated archive should be: Xcode-15.0-15A240d-extracted-SDK-with-libcxx-headers.tar.gz
.
The sha256sum
should be c0c2e7bb92c1fee0c4e9f3a485e4530786732d6c6dd9e9f418c282aa6892f55d
.
macOS Applications are created in Linux using a recent LLVM.
Apple uses clang
extensively for development and has upstreamed the necessary
functionality so that a vanilla clang can take advantage. It supports the use of -F
,
-target
, -mmacosx-version-min
, and -isysroot
, which are all necessary when
building for macOS.
To complicate things further, all builds must target an Apple SDK. These SDKs are free to download, but not redistributable. See the SDK Extraction notes above for how to obtain it.
The GUIX process build 2 sets of files: Linux tools, then Apple binaries which are created using these tools. The build process has been designed to avoid including the SDK’s files in GUIX’s outputs. All interim tarballs are fully deterministic and may be freely redistributed.
As of OS X 10.9 Mavericks, using an Apple-blessed key to sign binaries is a requirement in order to satisfy the new Gatekeeper requirements. Because this private key cannot be shared, we’ll have to be a bit creative in order for the build process to remain somewhat deterministic. Here’s how it works: