1. 16 May, 2017 1 commit
  2. 24 Nov, 2016 1 commit
  3. 01 Mar, 2016 1 commit
  4. 02 May, 2014 1 commit
    • Andreas Schuh's avatar
      Support alternative namespaces in GFLAGS_NAMESPACE CMake variable. · 659b440f
      Andreas Schuh authored
      The first element in the GFLAGS_NAMESPACE list is used as primary/default namespace. The symbols are then imported from this primary namespace into each of the other alternative namespaces with the using keyword. This is in particular used to maintain backwards compatibility with previous gflags library versions that used the "google" namespace instead of the new default "gflags" namespace.
      659b440f
  5. 27 Mar, 2014 2 commits
    • Andreas Schuh's avatar
      Add GFLAGS_INCLUDE_DIR CMake variable (Fixes issue #80). · 0c6e5fdb
      Andreas Schuh authored
      Both GFLAGS_NAMESPACE and GFLAGS_INCLUDE_DIR can be used to customize the installation of the gflags library. One specifies the C++ namespace name of the gflags symbols, the other the include subdirectory path of the public header files. By default, both are set to "gflags", but other Google libraries still expect "google" as C++ namespace name, but not necessarily also include path.
      0c6e5fdb
    • Andreas Schuh's avatar
      Add GFLAGS_INCLUDE_DIR CMake variable (Fixes issue #80). · aff8ef82
      Andreas Schuh authored
      Both GFLAGS_NAMESPACE and GFLAGS_INCLUDE_DIR can be used to customize the installation of the gflags library. One specifies the C++ namespace name of the gflags symbols, the other the include subdirectory path of the public header files. By default, both are set to "gflags", but other Google libraries still expect "google" as C++ namespace name, but not necessarily also include path.
      aff8ef82
  6. 18 Mar, 2014 1 commit
  7. 17 Mar, 2014 4 commits
  8. 14 Mar, 2014 1 commit
  9. 31 Jul, 2013 2 commits