Commit 580cf3c4 authored by kenton@google.com's avatar kenton@google.com

Update MSVC installation instructions for static linking change.

parent 3bdc1356
...@@ -14,15 +14,14 @@ Compiling and Installing ...@@ -14,15 +14,14 @@ Compiling and Installing
"include" directory (under the top-level package directory). "include" directory (under the top-level package directory).
6) Copy the contents of the include directory to wherever you want to put 6) Copy the contents of the include directory to wherever you want to put
headers. headers.
7) Copy protoc.exe and the two DLLs (libprotobuf and libprotoc) wherever you 7) Copy protoc.exe wherever you put build tools (probably somewhere in your
put build tools. PATH).
8) Copy libprotobuf.{lib,dll} and libprotoc.{lib,dll} wherever you put 8) Copy libprotobuf.lib and libprotoc.lib wherever you put libraries.
libraries.
* To avoid conflicts between the MSVC debug and release runtime libraries, when * 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 compiling a debug build of your application, you may need to link against a
build of libprotobuf.dll. Similarly, release builds must link against debug build of libprotobuf.lib. Similarly, release builds should link against
release DLLs. release libs.
DLLs vs. static linking DLLs vs. static linking
======================= =======================
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment