-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Windows shared library generates linkage warnings #569
Comments
have you fixed this issue yet? I also got this error |
I don't think it is a problem. Looking at the source code, I can see that glog can work with both gflags options and GLOG_* env variables, that's why it has two definitions for each option, one is implemented in glog and other is promised from gflags, if required (note that this is managed internally by glog). I don't know if it's okay to have such Level 1 warnings or not, but I'm not educated enough to do anything about it. This is from // Define GLOG_DEFINE_* using DEFINE_* . By using these macros, we
// have GLOG_* environ variables even if we have gflags installed.
//
// If both an environment variable and a flag are specified, the value
// specified by a flag wins. E.g., if GLOG_v=0 and --v=1, the
// verbosity will be 1, not 0. This stackoverflow answer elaborates it well if you wanna read more about it. |
Hello!
First, thanks for providing this amazing project to the community!
I have some linkage warnings when building glog 0.4.0 as shared library (with gflags 2.2.0), it does not break the build, but looks suspect.
Environment:
arch=x86_64
build_type=Release
compiler=Visual Studio
compiler.runtime=MD
compiler.version=16
os=Windows
os.version=10
Do you think this is a problem?
The text was updated successfully, but these errors were encountered: