You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,25 +77,25 @@ To support windows code signing the user has to create two certificate files `ap
77
77
78
78
### MacOS -> DMG
79
79
80
-
The builds are all done on an x86_64 apple machine and we're enabling rosetta explicitly in the `.plist` file for M1 machines.
80
+
MacOS has two variants ARM (M1,2,3...) and legacy x86 if you want to enable your builds on both platforms the easiest way is to have the CI (e.g. GitHub) have the build done on a x86_64 machine. Then the rosetta compatibility layer will make it runnable on ARM too. For this rosetta is enabled explicitly in the `.plist` file for ARM machines.
81
81
82
-
To run either you will need a macos development account. There are two environment variables this depends on `DEVELOPER_ID` which is set by `build_macos.sh` automatically using the default. `AC_PASSWORD` which is the API key for your account
82
+
Code signing is done as part of the `desktop.installer` task if and only if a developer_id is provided. This can be provided through one of these environment variables:
83
83
84
-
1)`build_macos.sh`
85
-
2)`notarize_macos.sh`
84
+
-`MACOS_DEVELOPER_ID` - String of the user uid
85
+
-`MACOS_PEM` - PEM file with both user uid and user certificate for signing
86
86
87
-
#### Known Issues / Comments
87
+
In addition the keychain to be used can be specified using:
88
+
-`MACOS_KEYCHAIN` - Name/path of the keychain defaults to the result of `security login-keychain`
88
89
89
-
* Background images for the deployment window of the `.dmg` (when clicking that on macos) are hardcoded in the rel/macosx/ subdirectory. I've not yet discovered how to properly (dynamically) create them. Also haven't found out how to set the DMGs icon to be non-standard as some apps do.
90
90
91
-
* The DMG should be notarized in two phases but right now it's not :-(
1) Notarize the app directory (by zipping and uploading it)
94
-
1) Staple the ticket to the app directory and all executables
95
-
1) Package the app directory into the dmg, notarize the dmg
96
-
1) Staple the ticket to the dmg
94
+
#### Known Issues / Comments
95
+
96
+
* Background images for the deployment window of the `.dmg` (when clicking that on macos) are hardcoded in the rel/macosx/ subdirectory. I've not yet discovered how to properly (dynamically) create them. Also haven't found out how to set the DMGs icon to be non-standard as some apps do.
97
97
98
-
* Best to use a really recent wxWidgets on macos, such as wxWidgets (3.1.6) as e.g. taskbar icon size bug fixes are only present there.
98
+
* Best to use the most recent wxWidgets on macos, as e.g. taskbar icon size bug fixes are only present there.
0 commit comments