You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the symbols exports were removed in #184, I'm wondering how I can compile uSockets on windows and get aml the symbols when I link it to a shared library.
Since the macro is not applied anymore to all the functions, when compiling on windows (and macos btw), the symbols are not exported and the linking step of my shared library fails.
How can I solve that ?
Thanks in advance
The text was updated successfully, but these errors were encountered:
As mentioned in the PR you linked, this should really not be used as a shared library. The performance as a shared library is far worse than as a static library with LTO enabled. It was decided in that PR that support for shared libraries was not worth cluttering the output of statically built executables with extra exported symbols.
Hello,
Since the symbols exports were removed in #184, I'm wondering how I can compile uSockets on windows and get aml the symbols when I link it to a shared library.
Since the macro is not applied anymore to all the functions, when compiling on windows (and macos btw), the symbols are not exported and the linking step of my shared library fails.
How can I solve that ?
Thanks in advance
The text was updated successfully, but these errors were encountered: