mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-01-26 11:13:23 -03:00
77 lines
2.8 KiB
Markdown
77 lines
2.8 KiB
Markdown
# MacOS Deployment
|
|
|
|
The `macdeployqtplus` script should not be run manually. Instead, after building as usual:
|
|
|
|
```bash
|
|
make deploy
|
|
```
|
|
|
|
When complete, it will have produced `Bitcoin-Core.zip`.
|
|
|
|
## SDK Extraction
|
|
|
|
### Step 1: Obtaining `Xcode.app`
|
|
|
|
A free Apple Developer Account is required to proceed.
|
|
|
|
Our macOS SDK can be extracted from
|
|
[Xcode_15.xip](https://download.developer.apple.com/Developer_Tools/Xcode_15/Xcode_15.xip).
|
|
|
|
Alternatively, after logging in to your account go to 'Downloads', then 'More'
|
|
and search for [`Xcode 15`](https://developer.apple.com/download/all/?q=Xcode%2015).
|
|
|
|
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:
|
|
|
|
```bash
|
|
# Install/clone tools needed for extracting Xcode.app
|
|
apt install cpio
|
|
git clone https://github.com/bitcoin-core/apple-sdk-tools.git
|
|
|
|
# Unpack the .xip and place the resulting Xcode.app in your current
|
|
# working directory
|
|
python3 apple-sdk-tools/extract_xcode.py -f Xcode_15.xip | cpio -d -i
|
|
```
|
|
|
|
On macOS:
|
|
|
|
```bash
|
|
xip -x Xcode_15.xip
|
|
```
|
|
|
|
### Step 2: Generating the SDK tarball from `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.
|
|
|
|
```bash
|
|
./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`.
|
|
|
|
## Deterministic macOS App Notes
|
|
|
|
macOS Applications are created on Linux using a recent LLVM.
|
|
|
|
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 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.
|
|
|
|
Using an Apple-blessed key to sign binaries is a requirement to produce (distributable) macOS
|
|
binaries. 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:
|
|
|
|
- Builders use Guix to create an unsigned release. This outputs an unsigned ZIP which
|
|
users may choose to bless, self-codesign, and run. It also outputs an unsigned app structure
|
|
in the form of a tarball.
|
|
- The Apple keyholder uses this unsigned app to create a detached signature, using the
|
|
included script. Detached signatures are available from this [repository](https://github.com/bitcoin-core/bitcoin-detached-sigs).
|
|
- Builders feed the unsigned app + detached signature back into Guix, which combines the
|
|
pieces into a deterministic ZIP.
|