Thanks, that was interesting.
However I did not find a solution.

The problem is not that my COpenSsl does not work, it does. I can compile & 
link SecureSockets just fine.

However the (macOS cocoa) app that uses SecureSockets -even though it does not 
use COpenSsl- wants access to that module. And I don’t know how to provide 
that, nor do I know how to prevent this.

Regards,
Rien

Site: http://balancingrock.nl
Blog: http://swiftrien.blogspot.com
Github: http://github.com/Balancingrock
Project: http://swiftfire.nl





> On 26 Jan 2017, at 11:53, Alex Blewitt <alb...@apple.com> wrote:
> 
> Have a look at BlueSockets which does the same kind of thing:
> 
> https://github.com/IBM-Swift/BlueSocket 
> https://github.com/IBM-Swift/BlueSSLService
> 
> There's a wrapper around OpenSSL as well:
> 
> https://github.com/IBM-Swift/OpenSSL.git 
> 
> Alex
> 
>> On 26 Jan 2017, at 09:49, Rien via swift-users <swift-users@swift.org> wrote:
>> 
>> I have created the following packages:
>> 
>> 1) SwifterSockets (Swift)
>> 2) COpenSsl (wrapper for system libraries)
>> 3) SecureSockets (Swift, uses SwifterSockets and COpenSsl)
>> 
>> Now I want to build a macOS app that uses SecureSockets.
>> 
>> I have created the app in the traditional way, via Xcode.
>> In this app I imported the frameworks created by SwifterSockets and 
>> SecureSockets.
>> 
>> When I try to use SecureSockets I get the error “No such module COpenSsl”
>> 
>> Any idea how I can include the system library wrapper ?
>> 
>> Regards,
>> Rien
>> 
>> Site: http://balancingrock.nl
>> Blog: http://swiftrien.blogspot.com
>> Github: http://github.com/Balancingrock
>> Project: http://swiftfire.nl
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> swift-users mailing list
>> swift-users@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-users
> 

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users

Reply via email to