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
SwiftyJSON not building, no error, no Xcode build output #532
Comments
This is because Carthage is finding the In the meantime, possible workarounds would be to rename |
I've created a PR for SwiftyJSON that 'fixes' this issue by moving the example project to a subdirectory: SwiftyJSON/SwiftyJSON#244. I'll be using my own fork until it is merged: https://github.com/Thomvis/SwiftyJSON. I tagged it as 2.2.1. |
Thanks, Thomvis. By the way, I created this issue because I thought it was bad to fail silently, not that I thought that carthage should be able to handle any odd project structure. It'd be nice if there were some message to the effect that the project's structure wasn't supported or something. The current behavior makes it look like a bug in carthage. |
I'd like to get this issue re-opened. I agree with @petereddy that it seems wrong to skip a dependency silently - so entirely a reporting issue for me. The issues you linked do provide more information, but nothing concerning this silent reporting. |
agree w @hartbit |
+1 for a more useful console message |
+1 |
Agree with more output or error from console message, at least: can't find framework scheme. |
0.8 is released, it should fix the issue. |
This is in version 0.7.4. I created a Cartfile with the following contents:
github "SwiftyJSON/SwiftyJSON"
$ carthage update
*** Fetching SwiftyJSON
*** Checking out SwiftyJSON at "2.2.0"
*** xcodebuild output can be found in /var/folders/qm/6l_xyqjs35b5zbhhnf4fyvy00000gn/T/carthage-xcodebuild.hiSkw1.log
$ cat /var/folders/qm/6l_xyqjs35b5zbhhnf4fyvy00000gn/T/carthage-xcodebuild.hiSkw1.log
$
In other words, no errors and the log is empty. If I add other projects to the Cartfile it builds them normally.
The text was updated successfully, but these errors were encountered: