Closed UnsafePointer closed 8 years ago
I think that this is a result of some change in Xcode. We should probably update all imports to use the @ outside of modules as well as the normal import "DTWeakSupport.h" in the umbrella header as well as all code inside the module.
:+1: Having the same issue and thought of same solution
I would think that having DTWeakSupport.h both in DTFoundation and in DTCoreText might be a cause for troubles here...
I am open to pull requests fixing that.
I have a branch that fixes the build and works in cocoapods beta but not sure if that's the solution you want to use https://github.com/ropiku/DTFoundation/commits/modular_import
That should help, all public headers from the framework should be imported with the framework prefixed.
@ropiku I ended up with exactly the same change as you mentioned.
Can somebody please confirm that this now builds with CocoaPods 1.0?
I can confirm that building from develop
works in 1.0.0.beta.6
with pod 'DTFoundation/Core', git: 'https://github.com/Cocoanetics/DTFoundation.git', branch: 'develop'
.
It would be great if you could release it to cocoapods soon.
@ropiku thanks for checking! I guess I'll make a release today then!
@odrobnik @ropiku thank you guys!
@odrobnik Thanks ! Could you release an updated DTCoreText
that updates the dependency against DTFoundation
? I have the foundation pod fixed in my podspec but I think new users would still get an error in cocoapods beta.
I am working on the 1.7.10 release of DTFoundation.
ok, released. @Ruenzuo please update and - if that hopefully resolves your issue - close this issue.
The project is not compiling with the latest CocoaPods beta version, as a dynamic framework, I got the following error:
Which I can fix by changing all
DTWeakSupport
andDTCompatibility
import statements in the project to modular imports:#import <DTFoundation/...>
but that doesn't look right to me, they're exported in the umbrella header either way: https://github.com/Cocoanetics/DTFoundation/blob/develop/Core/DTFoundation.h#L27Do you have any idea why this is not working? This happens on a beta version of CocoaPods either way, so maybe it's a bug on CocoaPods but I'm opening this PR to gather some information before filling an issue there.