Build error Xcode(Version 12.3 (12C33))

Open
#710 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
objective-c, swift

Research direction

Start with the reported Xcode compiler error, comparing Core.framework/Headers/Core-Swift.h at line 308 with SVGKit/SVGKit.framework/Headers/Document.h at line 78. Review the Podfile entry using the 3.x branch and determine what change makes the project build successfully in Xcode 12.3.

Written by the indexing model from the issue text.

Description

New Issue Checklist
  • I have read and understood the CONTRIBUTING guide
  • I have reproduced the problem while running in Xcode, and read the Console log, and acted upon any relevant error or warning messages
  • I have reproduced the problem while running in Xcode's Debugger, and used breakpoints to examine the actual values of variables vs the expected values
  • I am not using CocoaPods, or: I am using CocoaPods, but have verified my podspec points to SVGKit v2.x
Issue Description and Steps

Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.


Error:
/Build/Products/Debug-iphoneos/Core.framework/Headers/Core-Swift.h:308:12: error: 'Document' has different definitions in different modules; first difference is definition in module 'Core.Swift' found super class with type 'UIDocument'

/Build/Products/Debug-iphoneos/SVGKit/SVGKit.framework/Headers/Document.h:78:12: note: but in 'SVGKit.Document' found super class with type 'Node'
@interface Document : Node

in Podfile
...
pod 'SVGKit', :git => 'https://github.com/SVGKit/SVGKit.git', :branch => '3.x'
...

Dominant language
Objective-C
Stars
4.6k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SVGKit/SVGKit

All issues in SVGKit/SVGKit

Similar issues

More Objective-C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.