Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
G
gflags
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
gflags
Commits
84ab9523
Commit
84ab9523
authored
Nov 25, 2016
by
Andreas Schuh
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: Update use of gflags with Bazel documentation
parent
b872d6b5
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
4 deletions
+4
-4
INSTALL.md
INSTALL.md
+3
-3
doc
doc
+1
-1
No files found.
INSTALL.md
View file @
84ab9523
...
...
@@ -73,14 +73,14 @@ To use gflags in a Bazel project, map it in as an external dependency by editing
your WORKSPACE file:
git_repository(
name = "
gflags_git
",
commit = "
", # Use the current HEAD commit
name = "
com_github_gflags_gflags
",
commit = "
<INSERT COMMIT SHA HERE>",
remote = "https://github.com/gflags/gflags.git",
)
bind(
name = "gflags",
actual = "@
gflags_git
//:gflags",
actual = "@
com_github_gflags_gflags
//:gflags",
)
You can then add
`//external:gflags`
to the
`deps`
section of a
`cc_binary`
or
...
...
doc
@
78c66b37
Subproject commit
ea1cc83b50dc44df1f38891d9c95e99e2f127a80
Subproject commit
78c66b37266707a3cf2904c3891b08cddae8d83e
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment