erabo/spiegel-keyman
1
0
Fork 0
mirror of https://github.com/keymanapp/keyman.git synced 2026-08-05 16:35:33 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 13
spiegel-keyman/mac/README.md
Marc Durdin d9e8e546dc chore(mac): update build notes
2019-12-04 10:21:55 +01:00

5.1 KiB
Raw Blame History

Keyman for macOS

Mac Tools Requirements/Setup

Install Xcode 8.3.3 or later (it might also work to use an older version) Install Carthage *see Homebrew note below Install cocoapods (sudo gem install cocoapods) if not already installed.

Keyman for macOS Development

Keyman for macOS can be built from a command line (preferred) or Xcode.

Setting up your code signing and notarization environment.

With macOS 10.14 and later, Keyman must be signed then notarized by Apple, even for local test builds. This requires additional configuration for your build environment.

  1. First, open XCode, Preferences, Accounts, and select Manage Certificates for the identity you wish to use for signing. Click + and select Developer ID Application. A certificate will then be generated and listed in your Keychain. Get info for the certificate you generated from Keychain and copy its SHA-1 fingerprint. You'll need to remove spaces from between the hex pairs; you'll use this in step 3.

  2. Determine the Apple ID details in order to run a build. You may wish to create an App-Specific Password at https://appleid.apple.com/ and use this. Your Shortname will be either your 10-digit Team Identifier or a shortname that can be extracted with the following command:

    /Applications/Xcode.app/Contents/Developer/usr/bin/iTMSTransporter -m provider -u '<Username>' -p '<Password>' -account_type itunes_connect -v off

    Note: Use your Apple ID for <Username> and the app-specific password you generated above for <Password>. You'll use these in the next step as well.

  3. Add the following environment variables, probably to your .bashrc file, replacing with the values you collected in the previous steps:

     export CERTIFICATE_ID=<SHA1-Fingerprint>
 export APPSTORECONNECT_PROVIDER=<Shortname>
 export APPSTORECONNECT_USERNAME=<Username>
 export APPSTORECONNECT_PASSWORD=<Password>

Compiling from Command Line

To build Keyman for macOS, do the following:

  1. Open a Terminal window.
  2. cd to keyman/mac. build.sh must be run in the directory containing the script.
  3. Build using ./build.sh -no-codesign. Run ./build.sh -help to see all options.
    • If you have signing credentials from the core development team, you can build a signed version by omitting -no-codesign. Somewhat misleadingly, -no-codesign only stops automatic signing using the certificate maintained by the core development team!
    • If you want to deploy, you will need to also add -config Release, as a Debug build cannot be notarized.

Note: If Carthage prompts you to allow it access to your github credentials, it's fine to click Deny.

Running Keyman

  1. Deploy Keyman locally using ./build.sh -deploy local -deploy-only.
    • This will notarize the app, signing with your local credentials if not already signed, and copy keyman/mac/Keyman4MacIM/build/Debug/Keyman.app to ~/Library/Input Methods
  2. If running for the first time, follow the installation instructions at Installing Keyman for Mac OS X.

You can also use ./build.sh -no-codesign -deploy local to do a single-step build, notarize, and deploy.

Compiling from Xcode

To build using Xcode, you will need to build KeymanEngine4Mac first and then build Keyman4MacIM. The very first time after getting the source code (and any time the Podfile is edited; e.g., to install new pods), you need to go to keyman/mac/Keyman4MacIM and run "pod install" in Terminal.

  1. Launch Xcode
  2. Open keyman/mac/KeymanEngine4Mac/KeymanEngine4Mac.xcodeproj
  3. Build the project: Product > Build (or Cmd-B)
  4. Open keyman/mac/Keyman4MacIM/Keyman4MacIM.xcodeproj
  5. If you do not have signing credentials from the core development team, disable code signing in Xcode.
    1. Open the Project Navigator: View > Navigators > Show Project Navigator (Cmd-1)
    2. Select Keyman4MacIM and click Build Settings
    3. In the Signing section, change Code Signing Identity to Don't Code Sign. This will modify Keyman4MacIM.xcodeproj. Do not commit the change.
  6. Build the project. Refer to Running Keyman on how to install the app.

Testing

The Keyman4Mac project builds a test-bed app that can be used to test keyboards without installing the input method. It can also be used as reference for the usage of Keyman Engine.

Keyman4Mac tests are run using ./build.sh -test -no-codesign.

*note about Homebrew: Installing Carthage directly from the pkg file is simple. Homebrew seemed simple, but it changes a lot of settings and I think it messed up the build in a way that took me a long time to sort out. One specific problem is that using Homebrew seems to mess up the command-line tools, so you will probably get this error from xcodebuild: Error: xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory is a command line tools instance To fix it run this command: sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer