Fix 4a7fc95 by updating SwiftState to v1.1.1 #15
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
inamiy
added a commit
that referenced
this pull request
Dec 12, 2014
Fix 4a7fc95 by updating SwiftState to v1.1.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Continuing #11, #12, #13, #14.
This pull request will fix
carthage build=xcodebuild -workspace XXX -sdk iphoneos ...failure (error log in #13)which sometimes selects
SwiftState-OSXbuild-scheme which eventually requires iOS-CodeSign.See ReactKit/SwiftState#12 for more info.
By the way, adding
LD_RUNPATH_SEARCH_PATHS=$(PROJECT_DIR)/Carthage.build/Mac (or iOS)for XCTest-targets will link toCarthage.buildframeworks, and will also be runnable from xcodeproj (not needed for xcworkspace)