-
Notifications
You must be signed in to change notification settings - Fork 8
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
Use clang modules in cinterop instead of headers #32
Use clang modules in cinterop instead of headers #32
Conversation
@IlyaGulya awesome! does this fix #25? |
Yes, it should be fixed. 🙂 |
… arguments for swift build. Some logging.
058a392
to
e58f2be
Compare
…d of configuration phase
e58f2be
to
dad59aa
Compare
@IlyaGulya are we able to tag this release? |
Sure, I'll try to do it later this week. |
@markst this is available in latest release: https://github.com/ttypic/swift-klib-plugin/releases/tag/v0.6.2 |
Thanks @IlyaGulya ! |
This PR is based on #31 and should be reviewed and merged after #31.
This change makes
cinterop
support usage of clang modules in Objective-C headers.This is required to be able to use any modern apple framework (including
UIKit
,AVFoundation
, etc).Basically, any Objective-C header containing
@import
directive requires modules to be enabled.This change seems to be backwards compatible since we are generating cinterops for our own builds which are guaranteed to be clang modules.
Also, I've added
iosX64
andiosSimulatorArm64
to list of targets which are required sdk path to be provided toswift build
.Finally, I've fixed all configuration cache issues.
Also, this fixes issue #25