The QT Mac deployment doc only talks about libraries with link information embedded at compile time, such as qt framework and the plugins. For those libraries, we can use the install_name_tool to change the path of the libraries to relative paths so that the executable can locate the supporting libraries properly after deployment. However, openssl is loaded at run time with no embedded link information. I am not a mac newbie and don't know how to help my app locate the library properly at run time in this case.


Quote Originally Posted by ChrisW67 View Post
I thought this was the sort of problem that private frameworks in Mac bundles addressed. Make OpenSSL a private framework and adjust the bundle's search path. See the Mac deployment docs.