Open pedropalmero opened 9 years ago
:+1:
I had the same problem and issued a pull request to solve it (#53). This request was merged in commit 9f1a7e63461341ab456fa290f38bc53f24517845. So you should be able to compile as a framework now.
If you are using Swift 2.0 #54 adds lightweight generics which reduces the amount of casting you need to do.
https://github.com/appsquickly/XcodeEditor/pull/60 has make XcodeEditor able to be nicely integrate with Carthage into Swift projects(the project did not set define modules to be Yes, so previously after linking the framework you still need to add necessary headers to the bridging headers).
I haven't tested Cocoapods yet, but it's totally fine with Carthage.
@iosdevzone @cezheng Shall we tag a new version and close this issue off?
@jasperblues Maybe better to make sure that Cocoapods is fine(not sure if podspec would need an update or not since Carthage reads the xcodeproj's header settings but Cocoapods does not), but currently I don't have a mac at hand to check this out.
I'm using cocoapods in a MacOSX command line app with this Podfile:
When i try to build the project, it fails building because of including of non-modular header inside framework module
I've tried different solutions, like customizing the modulemap file or adding the framework to the target, but the error is always the same.
¿is there some solution or is it simply a swift limitation?, thanks