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

Automatically aggregate build products in one, consistent location #39

Closed
jspahrsummers opened this issue Oct 25, 2014 · 3 comments
Closed
Assignees

Comments

@jspahrsummers
Copy link
Member

Originally from #8.

The intention is that a Carthage user should be able to drag-and-drop a framework built by Carthage into their project/workspace, and have it Just Work™ going forward—even when building for a different platform, or if the dependency version changes, or when a different build configuration is chosen.

This might mean using Xcode's BUILT_PRODUCTS_DIR, but that worries me because it can get deleted frequently, and doesn't let users commit binaries to source control (if desired).

It might be easier to use a common, top-level subfolder of the application's repository. Users who don't want to commit the binaries can ignore this folder. However, this might require adding some search paths to their project settings.

@mdiep
Copy link
Member

mdiep commented Oct 25, 2014

However, this might require adding some search paths to their project settings.

@robrix suggested generating an xcconfig, which seems like a decent idea.

@jspahrsummers
Copy link
Member Author

I agree, if it becomes necessary. It'd be nice to avoid any need for custom settings at all, though.

@jspahrsummers
Copy link
Member Author

This issue also encapsulates bringing all dependencies up to the shared folder at the application level, so this is greater in scope than simply #12 (comment).

@jspahrsummers jspahrsummers self-assigned this Nov 9, 2014
natanrolnik pushed a commit to natanrolnik/Carthage that referenced this issue Feb 2, 2017
hujunfeng pushed a commit to hujunfeng/Carthage that referenced this issue Oct 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants