aboutsummaryrefslogtreecommitdiff
path: root/vsprojects
diff options
context:
space:
mode:
authorkenton@google.com <kenton@google.com@630680e5-0e50-0410-840e-4b1c322b438d>2008-10-21 17:18:26 +0000
committerkenton@google.com <kenton@google.com@630680e5-0e50-0410-840e-4b1c322b438d>2008-10-21 17:18:26 +0000
commit580cf3c47cb153693480b5f51a7ddcb06251de89 (patch)
tree4302247fe3436f4d099c40e43ab6891694a2f394 /vsprojects
parent3bdc135653c17bdfa23c9089f7b41572b56decf3 (diff)
downloadprotobuf-580cf3c47cb153693480b5f51a7ddcb06251de89.tar.gz
protobuf-580cf3c47cb153693480b5f51a7ddcb06251de89.tar.bz2
protobuf-580cf3c47cb153693480b5f51a7ddcb06251de89.zip
Update MSVC installation instructions for static linking change.
Diffstat (limited to 'vsprojects')
-rw-r--r--vsprojects/readme.txt13
1 files changed, 6 insertions, 7 deletions
diff --git a/vsprojects/readme.txt b/vsprojects/readme.txt
index a0f5bc86..b4c8962f 100644
--- a/vsprojects/readme.txt
+++ b/vsprojects/readme.txt
@@ -14,15 +14,14 @@ Compiling and Installing
"include" directory (under the top-level package directory).
6) Copy the contents of the include directory to wherever you want to put
headers.
-7) Copy protoc.exe and the two DLLs (libprotobuf and libprotoc) wherever you
- put build tools.
-8) Copy libprotobuf.{lib,dll} and libprotoc.{lib,dll} wherever you put
- libraries.
+7) Copy protoc.exe wherever you put build tools (probably somewhere in your
+ PATH).
+8) Copy libprotobuf.lib and libprotoc.lib wherever you put libraries.
* To avoid conflicts between the MSVC debug and release runtime libraries, when
- compiling a debug build of your application, you must link against a debug
- build of libprotobuf.dll. Similarly, release builds must link against
- release DLLs.
+ compiling a debug build of your application, you may need to link against a
+ debug build of libprotobuf.lib. Similarly, release builds should link against
+ release libs.
DLLs vs. static linking
=======================