aboutsummaryrefslogtreecommitdiff
path: root/vsprojects
diff options
context:
space:
mode:
authorFeng Xiao <xfxyjwf@gmail.com>2014-12-11 15:36:08 -0800
committerFeng Xiao <xfxyjwf@gmail.com>2014-12-11 15:36:08 -0800
commit78c8200655d38a88b09a748b04cf46646b89be00 (patch)
tree75dc9676e19a6a2ebc2f076e9e92c74383a5f4c5 /vsprojects
parent5fd12b84dad423b0482f663a844b44ab1f6fc5f6 (diff)
downloadprotobuf-78c8200655d38a88b09a748b04cf46646b89be00.tar.gz
protobuf-78c8200655d38a88b09a748b04cf46646b89be00.tar.bz2
protobuf-78c8200655d38a88b09a748b04cf46646b89be00.zip
Describe how to get gtest source for Visual Studio users.
Diffstat (limited to 'vsprojects')
-rw-r--r--vsprojects/readme.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/vsprojects/readme.txt b/vsprojects/readme.txt
index 288345ad..ad342497 100644
--- a/vsprojects/readme.txt
+++ b/vsprojects/readme.txt
@@ -6,6 +6,13 @@ accessible to those who primarily work with MSVC.
Compiling and Installing
========================
+0) Check whether a gtest directory exists in the upper level directory. If
+ you checkout the code from github via "git clone", this gtest directory
+ won't exist and you won't be able to build the tests described below. To
+ avoid this problem consider downloading one of the release tar balls which
+ contains gtest already and copying the gest directory from there to your
+ protobuf directory:
+ https://github.com/google/protobuf/releases
1) Open protobuf.sln in Microsoft Visual Studio.
2) Choose "Debug" or "Release" configuration as desired.*
3) From the Build menu, choose "Build Solution". Wait for compiling to finish.