name = "android", values = {"crosstool_top": "//external:android/crosstool"}, ) load(":bazel/gflags.bzl", "gflags_library", "gflags_sources") (hdrs, srcs) = gflags_sources(namespace=["google", "gflags"]) gflags_library(hdrs=hdrs, srcs=srcs, threads=0) gflags_library(hdrs=hdrs, ...
bazel Use += for appends 7年前 cmake Fix check of targets in package config when GFLAGS_USE_TARGET_NAMESPACE 5年前 src remove attribute where it does not apply 5年前 test Use CMake namespace gflags:: for export and alias target 7年前 .gitattributes Add .gitattributes...
name = "x64_windows", values = {"cpu": "x64_windows"}, ) config_setting( name = "android", values = {"crosstool_top": "//external:android/crosstool"}, ) load(":bazel/gflags.bzl", "gflags_library", "gflags_sources") (hdrs, srcs) = gflags_sources(namespace=["google", "gflags...
function parameter types, take both iterators by value. * Code-space savings and perhaps some modest performance improvements in * RepeatedPtrField. * Eliminate nullptr check from every tag parse. * Remove unused _$name$cached_byte_size fields. * Serialize extension ranges together when not ...
I've kept the default namespace to google. You can still change with with the appropriate flag to the configure script (./configure --helpto see the flags). If you have feedback as to whether the default namespace should change to gflags, which would be a non-backwards-compatible change...
In particular, I've kept the code in the namespace google, though in a future version it should be renamed to gflags. I've also kept the /usr/local/include/google/ subdirectory as synonym of /usr/local/include/gflags/, though the former name has been obsolete for some time now. 18 ...
In particular, I've kept the code in the namespace google, though in a future version it should be renamed to gflags. I've also kept the /usr/local/include/google/ subdirectory as synonym of /usr/local/include/gflags/, though the former name has been obsolete for some time now. 18 ...
I've kept the default namespace to google. You can still change with with the appropriate flag to the configure script (./configure --helpto see the flags). If you have feedback as to whether the default namespace should change to gflags, which would be a non-backwards-compatible change...
To use gflags in aBazelproject, map it in as an external dependency by editing your WORKSPACE file: git_repository( name = "com_github_gflags_gflags", commit = "<INSERT COMMIT SHA HERE>", remote = "https://github.com/gflags/gflags.git", ) ...
Merged 239: Use GFLAGS_NAMESPACE instead of "gflags" in test executable. Merged 237: Removed unused functions; fixes compilation with -Werror compiler option. Merged 232: Fix typo in Bazel's BUILD definition Merged 230: Remove using ::fLS::clstring. Merged 221: Add convenience 'uninstall' ...