Richard B.
Richard B.
Oups, didn't saw that CI was failing, I will update my commit again
So two commits behind master, current tests are fine Executed 236 tests, with 0 failures (0 unexpected) in 672.691 (672.723) seconds
rebased to current master
The reason I don't want to zip / unzip is that APFS makes copy almost instantly, so when a dependency at is compiled at version X.Y with swift version Y.Z...
it seems that using Xcode 10.2.1 wasn't a good idea... CI is down...
updated to current master, running `SWIFTPM_BOOTSTRAP=true make test` on my macbook : ``` Executed 236 tests, with 0 failures (0 unexpected) in 896.945 (896.963) seconds ```
@blender, thanks for pointing me to Rome, this is an interesting tool to share builds via the CI server (I'll need to think a bit more about what to do...
I like the way Carthage caches (e.g. using Xcode/swift version and dependency version in the path), does a PR adding an option like `--use-cached-builds` (only on `bootstrap` command, and why...
With the new Xcode / swift version (4.1), we have to "bootstrap or update" our dependencies on different projects having common dependencies (Alamofire, RxSwift...), same could occurs if Alamofire post...
One more use case: if a compilation fails during update (let's say the 7th out of 10), relaunching `carthage update` will recompile all dependencies, with `--use-cached-builds` it won't be the...