Protocol Buffers - Google's data interchange format (grpc依赖)
https://developers.google.com/protocol-buffers/
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
77 lines
3.8 KiB
77 lines
3.8 KiB
17 years ago
|
This directory contains project files for compiling Protocol Buffers using
|
||
|
|
MSVC. This is not the recommended way to do Protocol Buffer development --
|
||
|
|
we prefer to develop under a Unix-like environment -- but it may be more
|
||
|
|
accessible to those who primarily work with MSVC.
|
||
|
|
|
||
|
|
Compiling and Installing
|
||
|
|
========================
|
||
|
|
|
||
|
|
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.
|
||
|
|
4) From a command shell, run tests.exe and check that all tests pass.
|
||
|
|
5) Run extract_includes.bat to copy all the public headers into a separate
|
||
|
|
"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.
|
||
|
|
|
||
|
|
* 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.
|
||
|
|
|
||
|
|
DLLs and Distribution
|
||
|
|
=====================
|
||
|
|
|
||
|
|
When distributing your software to end users, we strongly recommend that you
|
||
|
|
do NOT install libprotobuf.dll or libprotoc.dll to any shared location.
|
||
|
|
Instead, keep these libraries next to your binaries, in your application's
|
||
|
|
own install directory. C++ makes it very difficult to maintain binary
|
||
|
|
compatibility between releases, so it is likely that future versions of these
|
||
|
|
libraries will *not* be usable as drop-in replacements. The only reason we
|
||
|
|
provide these libraries as DLLs rather than static libs is so that a program
|
||
|
|
which is itself split into multiple DLLs can safely pass protocol buffer
|
||
|
|
objects between them.
|
||
|
|
|
||
|
|
If your project is itself a DLL intended for use by third-party software, we
|
||
|
|
recommend that you do NOT expose protocol buffer objects in your library's
|
||
|
|
public interface, and that you statically link protocol buffers into your
|
||
|
|
library.
|
||
|
|
|
||
|
|
TODO(kenton): This sounds kind of scary. Maybe we should only provide static
|
||
|
|
libraries?
|
||
|
|
|
||
|
|
Notes on Compiler Warnings
|
||
|
|
==========================
|
||
|
|
|
||
|
|
The following warnings have been disabled while building the protobuf libraries
|
||
|
|
and compiler. You may have to disable some of them in your own project as
|
||
|
|
well, or live with them.
|
||
|
|
|
||
|
|
C4018 - 'expression' : signed/unsigned mismatch
|
||
|
|
C4146 - unary minus operator applied to unsigned type, result still unsigned
|
||
|
|
C4244 - Conversion from 'type1' to 'type2', possible loss of data.
|
||
|
|
C4251 - 'identifier' : class 'type' needs to have dll-interface to be used by
|
||
|
|
clients of class 'type2'
|
||
|
|
C4267 - Conversion from 'size_t' to 'type', possible loss of data.
|
||
|
|
C4305 - 'identifier' : truncation from 'type1' to 'type2'
|
||
|
|
C4355 - 'this' : used in base member initializer list
|
||
|
|
C4800 - 'type' : forcing value to bool 'true' or 'false' (performance warning)
|
||
|
|
C4996 - 'function': was declared deprecated
|
||
|
|
|
||
|
|
C4251 is of particular note. The protocol buffer library uses templates in
|
||
|
|
its public interfaces. MSVC does not provide any reasonable way to export
|
||
|
|
template classes from a DLL. However, in practice, it appears that exporting
|
||
|
|
templates is not necessary anyway. Since the complete definition of any
|
||
|
|
template is available in the header files, anyone importing the DLL will just
|
||
|
|
end up compiling instances of the templates into their own binary. The
|
||
|
|
Protocol Buffer implementation does not rely on static template members being
|
||
|
|
unique, so there should be no problem with this, but MSVC prints warning
|
||
|
|
nevertheless. So, we disable it. Unfortunately, this warning will also be
|
||
|
|
produced when compiling code which merely uses protocol buffers, meaning you
|
||
|
|
may have to disable it in your code too.
|