rosberry / depo Goto Github PK

Currently, carthage could not build for catalyst platform properly. If it will be possible we need to implement something like this solution

Right now, when you call depo it will call all package managers (pod, carthage, spm), but for example this project contains only cartfile

For example, if you'll try to build Imp, which don't contain xcodeproj in root, xcodebuild will fail with

xcodebuild: error: The directory /Users/vz/Developer/Project/.build/checkouts/Imp does not contain an Xcode project.

Cache builded frameworks and create symlinks to it from /Build/iOS directory.

Also allow to store those frameworks remotely, on a ci or some cloud data base

• send them to some server by ftp
• or to ci via ssh
• or to git remote repo (like certificates for match)

Depending on https://github.com/Carthage/Carthage/blob/master/Documentation/Xcode12Workaround.md

Now they are failed because swift package dump-package only works with valid Package.swift files. It means that directory, in which this Package.swift is located, should be a valid swift package

Replace xcodebuild by this. It's much faster (on xcodebuild -list for sure)

• example of Depofile
• update help

Currently jsoner returns .localPackage in requirement.type for this -- which is handler by empty string which is wrong, since local package initializer have path field, not url

Right now when user runs depo it just freeze

It will be extermely useful if you can build carthage via depo with --cache-builds flag

In order to support new xcodebuild system it would be nice, to use xcframework for merging iphoneos and iphonesimulator frameworks. Right now the lipo is used

In case, when swift package --version and swift -version outputs different version, there is a problem. I think the solution is to work with swift package --version, when adding // swift-tools-version: line to Package.swift

Add ability to specify which packages should be proceeded, like in carthage

carthage update SomePackage AnotherPackage

Add ability to specify scheme, which should be build for dependency. Don't know how carthage can handle that, but Pods and SP are build locally and target can be specified. This is required, if project has multiple targets, but you want to build only one