Re: [swift-users] SPM & Library with bridging header

2017-01-21 Thread Rien via swift-users
== This works: == First I need openSSL from Swift, that I have done with COpenSsl: Package.swift: import PackageDescription let package = Package( name: "COpenSsl", pkgConfig: "openssl" )

Re: [swift-users] SPM & Library with bridging header

2017-01-21 Thread Rien via swift-users
The thing I was missing is the “system module”.. found it now though ;-) So far so good, I want to put that little glue code I need in its own module. However I cannot find how to specify the import search path. “swift build -I /usr/local/include/“ does not work (unknown command -I) And

Re: [swift-users] SPM & Library with bridging header

2017-01-20 Thread Jordan Rose via swift-users
Hi, Rien. Libraries don’t support bridging headers because the client of the library has to be able to import the header, and arbitrary bridging headers may conflict. (This is actually the primary purpose of modules for Objective-C: to declare a group of headers that are self-contained—besides