Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
yangql
googletest
Commits
b55ac7f3
Commit
b55ac7f3
authored
Aug 30, 2015
by
Billy Donahue
Browse files
readme merging
parent
3f4e79b9
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
6 deletions
+2
-6
README.md
README.md
+2
-6
No files found.
README.md
View file @
b55ac7f3
...
...
@@ -86,7 +86,7 @@ you can also use it with [any C++ testing framework](googlemock/ForDummies.md#Us
If you are new to the project, we suggest that you read the user
documentation in the following order:
*
Learn the
[
basics
](
googletest/docs/Primer
)
of
*
Learn the
[
basics
](
googletest/docs/Primer
.md
)
of
Google Test, if you choose to use Google Mock with it (recommended).
*
Read
[
Google Mock for Dummies
](
googlemock/docs/ForDummies.md
)
.
*
Read the instructions on how to
[
build Google Mock
](
googlemock/README.md
)
.
...
...
@@ -109,11 +109,7 @@ posting a question on the
### Regenerating Source Files ###
Some of Google Test's source files are generated from templates (not
in the C++ sense) using a script. A template file is named FOO.pump,
where FOO is the name of the file it will generate. For example, the
file include/gtest/internal/gtest-type-util.h.pump is used to generate
gtest-type-util.h in the same directory.
in the C++ sense) using a script.
You don't need to worry about regenerating the source files
unless you need to modify them. You would then modify the
corresponding
`.pump`
files and run the '
[
pump.py
](
googletest/scripts/pump.py
)
'
...
...
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