From e3ded2c2c696f962c1203bdfaf5f8752b97486a6 Mon Sep 17 00:00:00 2001
From: David Raila <raila@illinois.edu>
Date: Tue, 21 Oct 2008 17:18:26 +0000
Subject: [PATCH] Update MSVC installation instructions for static linking
change.
---
vsprojects/readme.txt | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/vsprojects/readme.txt b/vsprojects/readme.txt
index a0f5bc8..b4c8962 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
=======================
--
GitLab