It might not be the issue on Boost but macOS, the*.dylib file to be signed if you want it to run it as distribution. https://developer.apple.com/library/archive/documentation/Security/Conceptua... On Sat, Mar 18, 2023 at 12:49 PM Nicholas Yue via Boost-users < boost-users@lists.boost.org> wrote:

Hi,

I have an application which uses Boost.DLL

I have built and run them successfully on Linux, Windows and MacOS.

I have an Intel Mac running Big Sur and have built Boost 1.81.0 successfully as a universal binary with both arm64 and x86_64 libraries combined.

However, while other parts of boost library runs fine, I have found that Boost.DLL will fail to load the plugins (also built as universal binary).

Is there additional steps we need to take when building DLL plugins via Boost.DLL as universal binary so that the loading mechanism is able to pick the correct portion of the *.dylib that is for the current architecture of the host application ?

Cheers -- Nicholas Yue https://www.linkedin.com/in/nicholasyue/ _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users