23
edits
Packaging Android host utilities: Difference between revisions
Jump to navigation
Jump to search
macos build directions: use 'macOS shippable' universal binaries (vs x86_64)
(update mac os x build directions to handle artifact not being produced by the automated systems) |
(macos build directions: use 'macOS shippable' universal binaries (vs x86_64)) |
||
| Line 40: | Line 40: | ||
Preparing for macOS is not quite so simple. Due to requirements of macOS, it's best to do this on a Mac OS X machine so that you can codesign the host utility binaries. If binaries are unsigned, users will be prompted at every invocation to "allow network connections". For more information on signing macOS binaries, see [http://apple.stackexchange.com/a/150711 here]. | Preparing for macOS is not quite so simple. Due to requirements of macOS, it's best to do this on a Mac OS X machine so that you can codesign the host utility binaries. If binaries are unsigned, users will be prompted at every invocation to "allow network connections". For more information on signing macOS binaries, see [http://apple.stackexchange.com/a/150711 here]. | ||
# From the selected treeherder build, identify '''macOS | # From the selected treeherder build, identify '''macOS Shippable'''. | ||
# Click on the green B | # Click on the green B under the Bpgo subheading, which will bring up a pane covering bottom third of the window. | ||
# On the bottom left pane is a header named '''Task'''. Click on the hash. | # On the bottom left pane is a header named '''Task'''. Click on the hash. | ||
# A new tab will open and load Taskcluster. Click on tab named "Run Artifacts". | # A new tab will open and load Taskcluster. Click on tab named "Run Artifacts". | ||