-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile with -fvisibility=hidden
.
#3322
Conversation
Fixes errors when spdlog is statically linked into two shared libraries, caused by the one copy calling a function of the other. This will not cause any problems for consumers because the exported APIs are already marked with `SPDLOG_API`.
The user's project that is creating a custom sink must be using an API that is not publicly available with Instead, you should pass the |
Which API is this, and why not also mark it with |
Some of the For example |
I looked at all headers that have an spdlog/include/spdlog/logger.h Line 421 in 326f887
|
I'm concerned that some users may be using symbols that have not been exported in the constructors of custom sinks and function arguments and return values. Finally, this is just my opinion. |
Agree with @tt4g — who knows what user code this might break. I'll add it to the v2.x branch since it's meant for breaking changes anyway. |
Merged to v2.x in PR #3324. It required some changes to ansicolor_sink to make it work, but seems ok now. |
Fixes errors when spdlog is statically linked into two shared libraries, caused by the one copy calling a function of the other. This will not cause any problems for consumers because the exported APIs are already marked with
SPDLOG_API
.