Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
P
protobuf
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
protobuf
Commits
24e2d8c2
Commit
24e2d8c2
authored
Oct 16, 2015
by
Leif Gruenwoldt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos in cmake README.md
parent
d8a926eb
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
11 deletions
+11
-11
README.md
cmake/README.md
+11
-11
No files found.
cmake/README.md
View file @
24e2d8c2
...
...
@@ -28,11 +28,11 @@ Create a folder where protobuf headers/libraries/binaries will be installed afte
C:\Path\to>mkdir install
If
*cmake*
co
omand is not avaliable from
*Command Prom
t*
, add it to system
*PATH*
variable:
If
*cmake*
co
mmand is not avaliable from
*Command Promp
t*
, add it to system
*PATH*
variable:
C:\Path\to>set PATH=%PATH%;C:\Program Files (x86)\CMake\bin
If
*git*
co
omand is not avaliable from
*Command Prom
t*
, add it to system
*PATH*
variable:
If
*git*
co
mmand is not avaliable from
*Command Promp
t*
, add it to system
*PATH*
variable:
C:\Path\to>set PATH=%PATH%;C:\Program Files\Git\cmd
...
...
@@ -64,7 +64,7 @@ You can download gmock as follows:
C:\Path\to\protobuf>git clone -b release-1.7.0 https://github.com/google/googlemock.git gmock
Then go to
*gmock*
folder and down
d
load gtest:
Then go to
*gmock*
folder and download gtest:
C:\Path\to\protobuf>cd gmock
C:\Path\to\protobuf\gmock>git clone -b release-1.7.0 https://github.com/google/googletest.git gtest
...
...
@@ -123,15 +123,15 @@ It will generate *nmake* *Makefile* in current directory.
To create
*Visual Studio*
solution file:
C:\Path\to\protobuf\cmake>mkdir solution & cd solution
C:\Path\to\protobuf\cmake\solution>cmake -G "Visual Studio 12 2013 Win64" ^
C:\Path\to\protobuf\cmake
\build
>mkdir solution & cd solution
C:\Path\to\protobuf\cmake\
build\
solution>cmake -G "Visual Studio 12 2013 Win64" ^
-DCMAKE_INSTALL_PREFIX=../../../../install ^
../..
It will generate
*Visual Studio
n
*
solution file
*protobuf.sln*
in current directory.
It will generate
*Visual Studio*
solution file
*protobuf.sln*
in current directory.
If the
*gmock*
directory does not exist, and you do not want to build protobuf unit tests,
you need to add
*cmake*
command argument
`-D
protobuf_BUILD_TESTS
=OFF`
to disable testing.
you need to add
*cmake*
command argument
`-D
BUILD_TESTING
=OFF`
to disable testing.
Compiling
=========
...
...
@@ -146,13 +146,13 @@ or
And wait for the compilation to finish.
Y
ou prefer to use the IDE:
If y
ou prefer to use the IDE:
*
Open the generated protobuf.sln file in Microsoft Visual Studio.
*
Choose "Debug" or "Release" configuration as desired.
*
From the Build menu, choose "Build Solution".
wait for the compilation to finish.
And
wait for the compilation to finish.
Testing
=======
...
...
@@ -163,7 +163,7 @@ To run unit-tests:
or
C:\Path\to\protobuf\cmake\build\debug>nmake
check
C:\Path\to\protobuf\cmake\build\debug>nmake check
You can also build project
*check*
from Visual Studio solution.
Yes, it may sound strange, but it works.
...
...
@@ -211,7 +211,7 @@ To install protobuf to the specified *install* folder:
or
C:\Path\to\protobuf\cmake\build\debug>nmake
install
C:\Path\to\protobuf\cmake\build\debug>nmake install
You can also build project
*INSTALL*
from Visual Studio solution.
It sounds not so strange and it works.
...
...
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