macos catalina install command line tools

Macos catalina install command line tools archive#
Macos catalina install command line tools software#
Macos catalina install command line tools code#
Macos catalina install command line tools password#

Xcrun altool -notarize-app -primary-bundle-id 'co.' -username -password 'zzzz-zzzz-zzzz-zzzz' -file BlowholeInstaller.pkg Copy that and paste it somewhere safe such as your keychain, but I also put it into a text document into which I assembled the notarization command itself. Do this from your Apple ID account page as explained here.

Macos catalina install command line tools password#

Your first step is to create an app-specific password for your Apple ID to use the Xcode altool command. Origin=Developer ID Installer: Howard Oakley (QWY4LRW926)Īpple details the notarization process here. Spctl -a -vv -t install BlowholeInstaller.pkg This new feature saves you from having to add the signature at the command line afterwards, and is a boon.īefore going any further, I checked that the Installer package was properly signed using Once those are set, select the Project tab again and add your Developer ID Distribution signature using the Set Certificate command in the Project menu.

Macos catalina install command line tools archive#

Click on that and select the hardened and signed command tool from Xcode’s archive to add it to the payload of the package. With the last folder selected, the + button at the foot is enabled. to view all folders, and work your way through to /usr/local/bin. Because this is just a single, simple command tool to be installed, I opt for a flat. Using Packages is straightforward, and detailed help is here. Origin=Developer ID Application: Howard Oakley (QWY4LRW926) Then check that your tool is all ready to build into a package.Įxecutable=/Users/hoakley/Documents/blowholeĬodeDirectory v=20500 size=549 flags=0x10000(runtime) hashes=8+5 location=embeddedĪuthority=Developer ID Application: Howard Oakley (QWY4LRW926)Īuthority=Developer ID Certification Authority Once you’re happy that the tool is ready to build for distribution, build an Archive, which should then contain a hardened and signed command tool, complete with timestamp. In the Packaging section of the Build Settings, ensure your ist is created in the binary, and uses the correct file, as shown below.įinally, ensure that the Signing section is properly set up to use your Developer ID Application certificate, and that the Hardened Runtime is enabled there.

Add a new Property List file with the name ist to your project, and add those items to it. When Xcode builds the tool, these will be embedded in the single Mach-O binary. If you’re successful in that, you finally staple the ticket to the package, and it’s ready to distribute.Ĭommand tools must have an ist file containing a minimum of three items: the Bundle Identifier, such as co.eclecticlight.blowhole, the Bundle Name, such as blowhole, and a version number, in a short Bundle Versions String. That signed package is then submitted to Apple for notarization. Once you’ve exported the built tool in an archive, you then build it into an Installer package, which has to be signed using a special Developer ID Distribution certificate from Apple. Those days have gone: to be hardened and signed, as required by Catalina, your tool needs an ist file, a signature, and the hardening flag.

Macos catalina install command line tools code#

There was no need for any ist file or code signature, so all you concentrated on was your code. In the past, writing command tools in Xcode has been relatively simple. This saves you a fair bit of effort, particularly now that it can sign the package too, but unfortunately there’s still plenty of preparation and commands. Some time ago, I described how I went about turning my command tools like blowhole into signed Installer packages, using Stéphane Sudre’s excellent free Packages. This article looks at how you can achieve that, working through what I have done with my tool blowhole.

Macos catalina install command line tools software#

Yesterday I noted how one of the changed requirements in macOS 10.15 Catalina is that software which isn’t run by LaunchServices, such as command tools, will still need to satisfy new requirements for signature, hardening and notarization.