Skip to content

Conversation

baumatron
Copy link
Contributor

Update installation instructions. A bridging header isn't necessary for Swift if linking against a Framework. Frameworks should also be linked as "Embedded Binaries."

Also remove ObjC and Swift examples from SDK workspace and create new projects/workspaces for each with versions of each using CocoaPods and Carthage. These are built as part of the Travis build to validate that the SDK will work with both types of projects and both languages.

I mostly left the existing examples intact, but removed some old non-ARC stuff from the ObjC example and changed the Swift example to link to KeenClient as a framework and do the proper imports instead of using a bridging header.

baumatron added 28 commits May 19, 2017 14:47
…to Travis build.

Carthage doesn't seem to really support local relative paths, so added a script to generate a cartfile with a full path to the git repo.
…ts to bin/.

This means building projects the normal Carthage or CocoaPods way will work and will pull down the library from github.

Cartfile.resolved and Podfile.lock have ben gitignored so that when a release is made a subsequent update to those files isn't required. The samples should always point to the latest version of the SDK in that branch as well.

Further of note, the samples won't necessarily always build using the provided Cartfile or Podfile since they don't reference the branch version of the SDK. In other words, they'll only be expected to work for the latest release tag in master. Only the travis build scripts will work in a general sense for any branch and any changeset.
…nd Cartfile are used for travis builds.

This seems less likely to cause issue down the road when unexpected things happen after running simulate_travis.sh since changes to these files will be apparent in git.
@baumatron baumatron requested review from josephwegner and masojus May 22, 2017 00:14
@coveralls
Copy link

coveralls commented May 22, 2017

Coverage Status

Coverage remained the same at 65.882% when pulling 82912d2 on update_examples into b5ac5c5 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 65.882% when pulling 82912d2 on update_examples into b5ac5c5 on master.

Copy link
Collaborator

@masojus masojus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. I'm glad we're verifying various methods of using the SDK now via CI. I didn't see anything that stood out as blocking. Thanks!

@baumatron baumatron merged commit 2b7efa1 into master May 23, 2017
@baumatron baumatron deleted the update_examples branch May 23, 2017 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants