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

SwiftyJSON not building, no error, no Xcode build output #532

Closed
petereddy opened this issue Jun 6, 2015 · 11 comments
Closed

SwiftyJSON not building, no error, no Xcode build output #532

petereddy opened this issue Jun 6, 2015 · 11 comments

Comments

@petereddy
Copy link

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.

@jspahrsummers
Copy link
Member

This is because Carthage is finding the Example.xcodeproj of SwiftyJSON, instead of the project file containing the framework itself. See #476 for a related discussion.

In the meantime, possible workarounds would be to rename Example.xcodeproj so it's sorted after the main project, or move it into a folder so it’s more nested.

@Thomvis
Copy link

Thomvis commented Jun 9, 2015

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.

@petereddy
Copy link
Author

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.

@jspahrsummers
Copy link
Member

See #476 and #108, which kinda cover this.

@hartbit
Copy link

hartbit commented Jun 18, 2015

See #476 and #108, which kinda cover this.

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.

@ikesyo
Copy link
Member

ikesyo commented Jun 18, 2015

@hartbit I'm working on it (#476) now. 🌝

@kortina
Copy link

kortina commented Jun 22, 2015

agree w @hartbit

@pcantrell
Copy link
Contributor

+1 for a more useful console message

@morizotter
Copy link
Contributor

+1

@tualatrix
Copy link

Agree with more output or error from console message, at least: can't find framework scheme.

@ikesyo
Copy link
Member

ikesyo commented Aug 7, 2015

0.8 is released, it should fix the issue.

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

9 participants