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.

Sign up for GitHub

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

Jump to bottom

Comparison with Rome #31

Closed
paulb777 opened this issue Jan 8, 2019 · 1 comment
Closed

Comparison with Rome #31

paulb777 opened this issue Jan 8, 2019 · 1 comment

Comments

@paulb777
Copy link

paulb777 commented Jan 8, 2019

This looks awesome!

Would you update the README with a comparison with Rome?
@leavez
Copy link
Owner

leavez commented Jan 11, 2019 •
edited
Loading

The goal of Rome:
Generate a list of framework files.

The goal of cocoapods-binary:
The plugin doesn't affect the way using cocoapods. Do a pod install, get the workspace file and develop in your old way. The only difference is that every pod target just imports a framework file and no source code file.

In fact, cocoapods-binary also uses some code of Rome to build the framework files.

@leavez leavez closed this as completed Jan 16, 2019
@leavez leavez pinned this issue Jan 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@paulb777 @leavez