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

Building with Carthage fails #169

Closed
DivineDominion opened this issue Oct 14, 2022 · 1 comment · Fixed by #171
Closed

Building with Carthage fails #169

DivineDominion opened this issue Oct 14, 2022 · 1 comment · Fixed by #171

Comments

@DivineDominion
Copy link
Contributor

Executing

$ carthage build --no-skip-current

fails; similarly, using OCMockito as a dependency via Carthage fails.

@DivineDominion
Copy link
Contributor Author

Building passes when Frameworks/gethamcrest is executed first. So the build process depends on the presence of that binary download. This affects Carthage, the only dependency manager that uses the Xcode project and its build settings, and thus suffers from this path being hard-coded.

Possible ways out:

  • Use Carthage in the Xcode project itself instead of a custom .xcframework reference;
  • add a "Run Script" phase that downloads OCHamcrest automatically

The latter creates inconsistencies in the dependency, though, since currently it'd download OCHamcrest 9.0.1 for the Xcode project, meanwhile Carthage fetches v8 during the resolution. See #170

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.

1 participant