I have been unable to make my Mac project use static OpenSSL libs.
(PC is a piece of cake)
Has anyone developing Extensions for SketchUp managed this on Macs?
While Chromium does use boringssl, as far as I’m aware they do not use it as a dynamic library, it’s built statically. You can verify this by looking in the CEF framework as well as our application bundles - we don’t distribute this dylib. I’m curious where that is coming from, but I’d guess it might be from another loaded extension, or maybe is installed to a system location due to some homebrew package or something similar.
I’m also curious if you get any warnings on startup about symbols being defined in multiple binaries because apparently this boringssl dylib and openssl are exporting the same one if you are somehow ending up in this dylib but are not linking against it.
Can you see what the path of that boringssl dylib is? If nothing else, it might explain where it’s coming from.
1 Like
Pretty sure its not a local / homebrew change on my part.
After Sequioa got released I started getting a stream of LightUp user support all describing the same symptoms of Sketchup shutting down (because of SSL_CTX_new failing)
If I use Xcode “Show Library info” on the crash site I get this:
But there is no such file as /usr/lib/libboringssl.dylib!
I’ve tried various dependency walker utilities to try and track down what is depending on libboringssl.dylib but no luck yet.