Use relative positioning in the Podfile for "non-standard" pods #622
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.
Closes: #619
The basic idea is to clone the two "non-standard" repos at the same level as this repo and then use "../.." in the
PodFileto reference them (rather than~/...).In addition to explaining that the two repos need to be cloned (and giving their locations),
the
README.mdfile also gives the smallest number of steps necessary to getXcodeto build the project.Unrelated rant: One might think that by now there'd be a file you could create, e.g.,
.xcenvthat would define all the top-level values (bundle identifiers, team identifiers, etc.), so that developers could simply.gitignorethe file and all the.pbxproj,.entitlementswould be use ${...} syntax....