You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, CEFswift is using a module map to access Chromium Embedded framework itself, but that module map is not included in CEFswift.framework. If any user wants to use compiled CEFswift.framework directly, s/he will probably meet such error
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "Headers/CEFswift.h"
^
~/playground/CEF.swift/Samples/CEFDemo/Library/Release/CEFswift.framework/Headers/CEFswift.h:19:9: error: module 'ChromiumEmbedded' not found
@import ChromiumEmbedded;
^
<unknown>:0: error: could not build Objective-C module 'CEFswift'
To reproduce this error, just compile CEFswift and remove the modules folder in CEFswift's source code, then compile the sample project.
I'm not sure if it's a common practice to include multiple module map into one single framework, or should we just define both CEFswift and ChromiumEmbedded in the same module map for CEFswift.framework itself? Anyway, I guess the compiled framework shouldn't rely on any source code.
The text was updated successfully, but these errors were encountered:
Anyway, I guess the compiled framework shouldn't rely on any source code.
Completely agree and it came to me as a surprise that the headers must be present, but right now I don't have a solution off the top of my head. I'll give it a thought soon but if you can come up with something, I'm gladly accepting PRs.
Currently, CEFswift is using a module map to access Chromium Embedded framework itself, but that module map is not included in CEFswift.framework. If any user wants to use compiled CEFswift.framework directly, s/he will probably meet such error
To reproduce this error, just compile CEFswift and remove the modules folder in CEFswift's source code, then compile the sample project.
I'm not sure if it's a common practice to include multiple module map into one single framework, or should we just define both CEFswift and ChromiumEmbedded in the same module map for CEFswift.framework itself? Anyway, I guess the compiled framework shouldn't rely on any source code.
The text was updated successfully, but these errors were encountered: