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 builds ExampleModel.framework #13

Closed
alexcurylo opened this issue May 7, 2015 · 7 comments
Closed

Carthage builds ExampleModel.framework #13

alexcurylo opened this issue May 7, 2015 · 7 comments
Labels

Comments

@alexcurylo
Copy link

Since Example.xcodeproj and JSQCoreDataKit.xcodeproj are at the same level, Carthage builds ExampleModel.framework which is undesired. Moving /Example into /JSQCoreDataKit seems to me to be the best way to resolve this if you have no objections.

@jessesquires
Copy link
Owner

thanks @alexcurylo !

@jessesquires
Copy link
Owner

hey @alexcurylo - actually, i just tried this and carthage did not build ExampleModel.

Running from the root directory:

$ carthage build --no-skip-current
*** xcodebuild output can be found in /var/folders/tx/s__fjnns3yd_23813_gwk7sh0000gn/T/carthage-xcodebuild.LwNg08.log
*** Building scheme "JSQCoreDataKit" in JSQCoreDataKit.xcworkspace

Then:

$ tree
├── Carthage
│   └── Build
│       └── iOS
│           └── JSQCoreDataKit.framework
│               ├── Headers
│               │   ├── JSQCoreDataKit-Swift.h
│               │   └── JSQCoreDataKit.h
│               ├── Info.plist
│               ├── JSQCoreDataKit
│               ├── Modules
│               │   ├── JSQCoreDataKit.swiftmodule
│               │   │   ├── arm.swiftdoc
│               │   │   ├── arm.swiftmodule
│               │   │   ├── arm64.swiftdoc
│               │   │   ├── arm64.swiftmodule
│               │   │   ├── i386.swiftdoc
│               │   │   ├── i386.swiftmodule
│               │   │   ├── x86_64.swiftdoc
│               │   │   └── x86_64.swiftmodule
│               │   └── module.modulemap
│               └── _CodeSignature
│                   └── CodeResources

@jessesquires
Copy link
Owner

And, running carthage update with the following Cartfile produces the same results:

github "jessesquires/JSQCoreDataKit"
$ carthage update
*** Cloning JSQCoreDataKit
*** Checking out JSQCoreDataKit at "1.1.0"
*** xcodebuild output can be found in /var/folders/tx/s__fjnns3yd_23813_gwk7sh0000gn/T/carthage-xcodebuild.dcvTQy.log
*** Building scheme "JSQCoreDataKit" in JSQCoreDataKit.xcworkspace

Can you provide steps on how to reproduce your issue?

@alexcurylo
Copy link
Author

Sure: here's a cartfile on a shell project demonstrating the problem.

bill:PoseGallery alex$ carthage version
0.7.0
bill:PoseGallery alex$ carthage update --platform iOS
*** Fetching XCGLogger
*** Fetching Swiftalytics
*** Fetching JSQCoreDataKit
*** Checking out JSQCoreDataKit at "1.1.0"
*** Checking out XCGLogger at "Version_2.0"
*** Checking out Swiftalytics at "0.1.1"
*** xcodebuild output can be found in /var/folders/n2/j5b8v36d7l722kg872pw616h0000gn/T/carthage-xcodebuild.sD9rhH.log
*** Building scheme "ExampleModel" in JSQCoreDataKit.xcworkspace
*** Building scheme "JSQCoreDataKit" in JSQCoreDataKit.xcworkspace
*** Building scheme "Swiftalytics" in Swiftalytics.xcworkspace
*** Building scheme "XCGLogger (iOS)" in XCGLogger.xcodeproj
bill:PoseGallery alex$ 

@jessesquires
Copy link
Owner

Well, we're clearly getting different results. 😄

I recently did a bit of refactoring regarding the project setup/organization. There is no longer an ExampleModel scheme in the workspace. So I think this is a caching problem.

Trying clearing DerivedData/ and the carthage cache, and everything should be working.

@jessesquires jessesquires added question and removed bug labels May 7, 2015
@alexcurylo
Copy link
Author

Yup, cleared out everything Carthage-related and it rebuilt fine. Sorry to bother you!

@jessesquires
Copy link
Owner

No worries! 😄

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

Successfully merging a pull request may close this issue.

2 participants