-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for local/remote binary #52
base: feature/external-dependencies-single-module-experimental
Are you sure you want to change the base?
Conversation
For VersionRange, it's not possible to have a specific one We need to try/cacth every swift step and print on the ouput the error, it's important for the user All test are passing except local package The local package need to be done
we can now use local path, some manual update has been done all tests are passing
add new test for building and liking Firebase using triple for specify the build target
you can set multiple product from a dependency like Firebase
update comment in interface
We can now set the toolsVersion from the plugin By default, the command line uses the latest swift version available. By at some cases, it can't work and a specific version need to be set.
It needs to be set at Warning Level or it will be considered as a Error.
set a non null default value for toolsVersion in CompileTask
rollback unwanted commit change
commit 166468f Author: frankois <dabonot.francois@gmail.com> Date: Wed Nov 6 17:27:43 2024 +0100 cleaning CompileSwiftTask moving all command for updating the manifest to CreatePackageSwift
update sed command for injecting the package cleaning some code
the checksum is a mandatory value
update checksum update build script
use template now
…l' of https://github.com/frankois944/swift-klib-plugin into swift-spm-local-remote-lib # Conflicts: # plugin/src/functionalTest/kotlin/io/github/ttypic/swiftklib/gradle/SwiftPackageModulesTest.kt # plugin/src/main/kotlin/io/github/ttypic/swiftklib/gradle/api/SwiftPackageConfiguration.kt # plugin/src/main/kotlin/io/github/ttypic/swiftklib/gradle/internal/SwiftPackageConfigurationImpl.kt # plugin/src/main/kotlin/io/github/ttypic/swiftklib/gradle/task/CompileSwiftTask.kt # plugin/src/main/kotlin/io/github/ttypic/swiftklib/gradle/templates/CreatePackageSwift.kt
@IlyaGulya Done, the history is dirty, squash if you can :D |
Hmm, I'm not sure I want binaries in the repo. |
Also, I think it would be nice to use Xcodegen to avoid putting xcode project files into repo. They are not git-friendly =) |
There are required for testing, especially the .zip one, it needs to be remotly available and have a valid checksum. It can't be done during the tests. |
Using an external tools to manage the Xcode project will make thing more complicate to manage. Just stay on the simplest way, I can also put the sample project in a zip to clean the history of the git, If you want. |
Maybe we can use some community built binary framework for such tests? |
Regarding the xcodeproj - i don't really see any specific reason to keep whole xcode project in the repo, when it can be easily generated by xcodegen.
|
May be relevant: PaGr0m/kotlin-spm-plugin#7 |
Based on #47
Add the capability to use local and remote Binary
The folder
localBinarySample
contains the Xcode project and a script to generate the testing framework.