Build with Carthage fails
Closed this issue · 0 comments
dcaunt commented
New issue checklist
- I have read all of the
README
and documentation. - I have reviewed the contributing guidelines.
- I have searched existing issues and this is not a duplicate.
General information
- Library version(s): 4.0
- OS version(s): 10.11.6
- Devices/Simulators affected: All
- Reproducible in the demo project (Yes/No): n/a
- Related issues:
Expected behavior
Frameworks are built and compilation succeeds.
Actual behavior
*** Checking out JSQDataSourcesKit at "4.0.0"
*** xcodebuild output can be found in /var/folders/t6/566y64zd1c54v7tkfq9jx4300000gn/T/carthage-xcodebuild.tTB6wq.log
*** Building scheme "JSQDataSourcesKit-iOS" in JSQDataSourcesKit.xcodeproj
*** Building scheme "Example" in Example.xcodeproj
** BUILD FAILED **
The following build commands failed:
CompileSwift normal arm64 /Users/dcaunt/Projects/cinema-ios/Carthage/Checkouts/JSQDataSourcesKit/Example/Tests/ExampleTests.swift
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler
(2 failures)
/Users/dcaunt/Projects/cinema-ios/Carthage/Checkouts/JSQDataSourcesKit/Example/Tests/ExampleTests.swift:21:18: error: module 'Example' was not compiled for testing
A shell task (/usr/bin/xcrun xcodebuild -project /Users/dcaunt/Projects/cinema-ios/Carthage/Checkouts/JSQDataSourcesKit/Example/Example.xcodeproj -scheme Example -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** BUILD FAILED **
The following build commands failed:
CompileSwift normal arm64 /Users/dcaunt/Projects/cinema-ios/Carthage/Checkouts/JSQDataSourcesKit/Example/Tests/ExampleTests.swift
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler
(2 failures)
Steps to reproduce
carthage build --no-skip-current
As Carthage builds the Example
project, it encounters this error under Release configuration. For Release, projects should not generally run their tests, so a scheme change will fix this.