Skip to content
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

Support for other package managers? #4

Closed
mpdifran opened this issue Apr 19, 2021 · 3 comments · Fixed by #7
Closed

Support for other package managers? #4

mpdifran opened this issue Apr 19, 2021 · 3 comments · Fixed by #7

Comments

@mpdifran
Copy link

Just wondering if there's a plan to support Carthage (looks like there's support for Cocoapods, SPM, and Apple Frameworks only).

Also, is it possible to run this tool on a Swift Package (i.e. pass in the Package.swift)?

@maxchuquimia
Copy link
Owner

I currently have no immediate plans to support Carthage - I did a proof of concept to add it initially but found that it's not easy to discover sub-dependencies (the Cartfile.resolved isn't helpful) and also I seem to remember this issue being a blocker. I'm more than happy to accept a PR that adds support for Carthage though!

Running xcgrapher on a Package.swift is very much on the table - I'm going to add it when I next have time!

@mpdifran
Copy link
Author

Re: Carthage, have you tried using the Cartfile.resovled that's in the Carthage/Checkout/<dependency> folder for each dependency? That should allow you to recursively build the dependency tree. But it's a bit of a moot point if that other issue is still blocking you.

@maxchuquimia
Copy link
Owner

I think I looked into that briefly - which reminds me of another issue with integrating against Carthage: there are many ways people use it and one of them involves only committing the frameworks, nothing more... so in cases like that we could run into issues too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants