Jan

I had to completely rewrite the “Package.swift” file’s content to get the “[email protected]” necessary for > Swift 4. Here is my result. It works, but please assume that I have...

I just ran into this myself: I was prototyping an NSDocument-based app where each document uses a Socket for client-server communication. Closing the document properly deallocated the socket, but the...

Are you using queues? In this case they might be hanging on to the parent object with its reference to your Socket. You will have to signal the queue’s closure...

I ran 'Xit/objective-git/script/update_libssl_ios' on a whim and the error changed to this: ``` ld: library not found for -lssl clang: error: linker command failed with exit code 1 (use -v...

It looks to me like the libssl you are linking into your release builds might not be the one you think.

ObjectiveGit-Mac Group

`brew upgrade carthage` followed by `bootstrap` didn’t resolve the issue. A clean followed by another release build didn’t resolve it either.

I have fixed the build temporarily by adding the following paths to the “ObjectiveGit-Mac” target: `External/libssl` to `OTHER_LDFLAGS` `openssl` to `HEADER_SEARCH_PATHS` `Xit/objective-git/Carthage/Checkouts/xcconfigs/Base/Configurations` exists and the file exists there as well....

`otool -L Xit.app/Contents/MacOS/Xit` shows that a Xit build depends on this (experimental M1 build): "/opt/homebrew/opt/libssh2/lib/libssh2.1.dylib" This likely is similar on x86_64. Maybe we can get cmake/the linker to use "/opt/homebrew/lib/libssh2.a"...

Any thoughts @Uncommon?