spiegel-keyman/mac
Randy Boring 00e4b82a4e fix dark/light brokenness by going back to defaults for text colors and button borders
but having the background view use windowBackgroundColor instead of white to fill.
2019-02-27 01:54:05 -06:00
..
Keyman4Mac Sets Mac version in xcodeproj files to 12.0 for alpha. 2019-02-18 11:52:10 +07:00
Keyman4MacIM fix dark/light brokenness by going back to defaults for text colors and button borders 2019-02-27 01:54:05 -06:00
KeymanEngine4Mac Sets Mac version in xcodeproj files to 12.0 for alpha. 2019-02-18 11:52:10 +07:00
TestInput Corrected typo in instructions 2018-05-18 10:02:27 -04:00
.gitignore [Mac] #769 - Switched to using Cocoapods to get Crashlytics framework 2018-06-01 16:00:22 -04:00
bashHelperFunctions.sh Added #!/bin/sh to indicate that bashHelperFunctions.sh is an executable shell script. 2017-08-10 22:51:10 -04:00
build.sh Merge pull request #1343 from keymanapp/mac-update-podfile 2018-12-07 14:12:10 +11:00
Cartfile.private Use Carthage to pull OCMocks framework and added KMX file for testing 2018-01-30 12:19:29 -05:00
Cartfile.resolved Updated carthage to remove Crashlytics & Fabric (now gotten via cocoapods) 2018-06-04 10:43:10 -04:00
ComponentInputModeDict.rtf [Mac] Initial check-in to open-source repo 2017-08-10 13:11:52 +07:00
history.md Merge branch 'master' into beta-final-master-merge 2019-02-25 18:22:15 +11:00
is_same_version.sh added Script Phase to verify that the version in the project file matches the version in this git branch 2019-01-22 11:58:12 -06:00
README.md [Mac] Added pod install command to build and updated supporting files. 2018-06-04 10:29:17 -04:00

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.

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.

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.
    • Alternatively 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.

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