Transition Cocoapods to Swift Package Dependencies #415
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
paulplant
force-pushed
the
swift-package-dependencies
branch
from
c8ad820 to
043f535
Compare
paulplant
force-pushed
the
swift-package-dependencies
branch
from
043f535 to
9cdf228
Compare
|
I have just cloned this branch and installed it on top of my existing xDrip4iO5 that was installed using the Pods. No problems, it compiled immediately, installed fine and so far everything seems to be working OK. Nice. :) |
|
I have also built in top of previous local clone wih pods, no issues. Additionally, I have built using GitHub Actions / Fastlane by adapting #412 (without any pod related commits), and this also worked perfectly. This proves that it builds also on a fresh build environment, as the MacOS for Fastlan builds is "single use". |
- to fix red product error
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.
Cocoapod framework installation will no longer be needed. Packages will be automatically downloaded by Xcode.
if this commit is pulled into a previous build folder, the Pod folder, Podfile and also Podfile.lock files can be safely deleted from the folder.
@JohanDegraeve - once merged, Podfile and Podfile.lock should be deleted from the repository as they will be no longer needed