Influence Carthage Xcode project lookup #469
Closed
Conversation
This file contains 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
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.
Carthage just uses any Xcode project or workspace file it can find to build frameworks. This is an attempt to tell Carthage where to start.
Workspaces have higher precedence than projects, so I added a new Workspace with a reference to the framework project instead of merely a symlink.
Was an attempt to influence #468 but doesn't actually help (other projects are still traversed by Carthage and then fail). With the DatePlot project deleted to prevent the exception, Carthage would start to build the framework from the CorePlotExamples workspace, which sounds a bit odd, so this PR merely affects that lookup. -- Feel free to discard/close without merging this if that doesn't add enough value.