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

Carthage not building #564

Closed
abbeycode opened this issue Jun 16, 2015 · 12 comments
Closed

Carthage not building #564

abbeycode opened this issue Jun 16, 2015 · 12 comments
Labels

Comments

@abbeycode
Copy link
Contributor

I cloned the repo, ran a carthage update, and then opened the workspace. The Commandant, Quick, Argo, Runes, and Box projects all show up red. I see the frameworks built in the Carthage/Build/Mac directory, but I don't see the projects anywhere in Carthage/Checkouts, nor do I see any but Argo in the Cartfile. It looks like the rest must be upstream dependencies, but I'm not sure what's going on. I installed the 0.7.4 release ("Time Desk").

What am I missing? I'm trying to get a pull request started.

@neilpa
Copy link
Member

neilpa commented Jun 16, 2015

You should be running bootstrap not update when setting up a repo unless you're explicitly updating the dependencies. In this case you also need to specify --no-use-binaries to ensure all the workspace dependencies get checked out. Otherwise carthage will default to the binary framework releases.

@abbeycode
Copy link
Contributor Author

Thanks, I reset the repo, then ran carthage bootstrap now, and then I got a build error when building Nimble:

Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found.
CodeSign error: code signing is required for product type 'Framework' in SDK 'iOS 8.3'

Should the CONTRIBUTING.md file have instructions for first-time setup, including using the bootstrap command?

@neilpa
Copy link
Member

neilpa commented Jun 16, 2015

Should the CONTRIBUTING.md file have instructions for first-time setup, including using the bootstrap command?

Probably not because that's how it works when cloning any project that uses carthage to manage it's dependencies, including carthage itself. This is already covered in the README.

@neilpa
Copy link
Member

neilpa commented Jun 16, 2015

As for the codesigning error, you can specify --platform mac when bootstrapping since you don't need to build for ios.

@abbeycode
Copy link
Contributor Author

Okay, thanks, I'm still getting up to speed with it all. Now, having run carthage bootstrap --platform mac, I've still got 5 red projects. I did find their source - they're a few levels deep inside the carthage directory

@abbeycode
Copy link
Contributor Author

Actually, looking more closely, I see (e.g. for Commandant) a framework in Carthage/Build/Mac, but I don't see any source checkout for it. When I do a Finder search for "Commandant", all I see are a couple of headers in the framework, and the Cartfile.private and Cartfile.resolved files.

@mdiep
Copy link
Member

mdiep commented Jun 17, 2015

Commandant uses binaries releases. So a pre-built copy of the framework is downloaded directly from GitHub.

@abbeycode
Copy link
Contributor Author

Right, but I'm trying to open the Carthage workspace, which refers to Commandant, and 4 other xcodeproj files that don't seem to be downloaded after I bootstrap.

@mdiep
Copy link
Member

mdiep commented Jun 17, 2015

If you use the --no-use-binaries flag, then Carthage will download and checkout the source.

@abbeycode
Copy link
Contributor Author

Ah ok, that did it. May I submit a pull request to add that full command to the CONTRIBUTING.md file?

carthage bootstrap --platform mac --no-use-binaries

@mdiep
Copy link
Member

mdiep commented Jun 17, 2015

That would be great. 😄

@abbeycode
Copy link
Contributor Author

@mdiep I submitted a pull request for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants