Skip to content
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

google namespace vs. gflags namespace #34

Open
yurivict opened this issue Jun 20, 2016 · 2 comments
Open

google namespace vs. gflags namespace #34

yurivict opened this issue Jun 20, 2016 · 2 comments

Comments

@yurivict
Copy link

On FreeBSD I had to apply this patch:

--- hiptext.cc.orig     2016-06-17 23:50:21 UTC
+++ hiptext.cc
@@ -197,9 +197,9 @@ inline string GetExtension(const string&
 int main(int argc, char** argv) {
   // if (!isatty(1))
   //   FLAGS_color = false;
-  google::SetUsageMessage("hiptext [FLAGS]");
-  google::SetVersionString("0.1");
-  google::ParseCommandLineFlags(&argc, &argv, true);
+  gflags::SetUsageMessage("hiptext [FLAGS]");
+  gflags::SetVersionString("0.1");
+  gflags::ParseCommandLineFlags(&argc, &argv, true);
   google::InitGoogleLogging(argv[0]);
   google::InstallFailureSignalHandler();
   const char* lang = std::getenv("LANG");

I have gflags-2.1.2, glog-0.3.4 - the latest versions.

@jart
Copy link
Owner

jart commented Jun 22, 2016

Good to know. Thank you.

@yurivict
Copy link
Author

Still:

src/hiptext.cc:200:3: error: no member named 'SetUsageMessage' in namespace 'google'; did you mean 'gflags::SetUsageMessage'?
  google::SetUsageMessage("hiptext [FLAGS]");
  ^~~~~~~~~~~~~~~~~~~~~~~
  gflags::SetUsageMessage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants