README.txt 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. Protocol Buffers - Google's data interchange format
  2. Copyright 2008 Google Inc.
  3. http://code.google.com/apis/protocolbuffers/
  4. C++ Installation - Unix
  5. =======================
  6. To build and install the C++ Protocol Buffer runtime and the Protocol
  7. Buffer compiler (protoc) execute the following:
  8. $ ./configure
  9. $ make
  10. $ make check
  11. $ make install
  12. If "make check" fails, you can still install, but it is likely that
  13. some features of this library will not work correctly on your system.
  14. Proceed at your own risk.
  15. "make install" may require superuser privileges.
  16. For advanced usage information on configure and make, see INSTALL.txt.
  17. ** Hint on install location **
  18. By default, the package will be installed to /usr/local. However,
  19. on many platforms, /usr/local/lib is not part of LD_LIBRARY_PATH.
  20. You can add it, but it may be easier to just install to /usr
  21. instead. To do this, invoke configure as follows:
  22. ./configure --prefix=/usr
  23. If you already built the package with a different prefix, make sure
  24. to run "make clean" before building again.
  25. ** Note for Solaris users **
  26. Solaris 10 x86 has a bug that will make linking fail, complaining
  27. about libstdc++.la being invalid. We have included a work-around
  28. in this package. To use the work-around, run configure as follows:
  29. ./configure LDFLAGS=-L$PWD/src/solaris
  30. See src/solaris/libstdc++.la for more info on this bug.
  31. ** Note for HP C++ Tru64 users **
  32. To compile invoke configure as follows:
  33. ./configure CXXFLAGS="-O -std ansi -ieee -D__USE_STD_IOSTREAM"
  34. Also, you will need to use gmake instead of make.
  35. C++ Installation - Windows
  36. ==========================
  37. If you are using Micosoft Visual C++, see vsprojects/readme.txt.
  38. If you are using Cygwin or MinGW, follow the Unix installation
  39. instructions, above.
  40. Binary Compatibility Warning
  41. ============================
  42. Due to the nature of C++, it is unlikely that any two versions of the
  43. Protocol Buffers C++ runtime libraries will have compatible ABIs.
  44. That is, if you linked an executable against an older version of
  45. libprotobuf, it is unlikely to work with a newer version without
  46. re-compiling. This problem, when it occurs, will normally be detected
  47. immediately on startup of your app. Still, you may want to consider
  48. using static linkage. You can configure this package to install
  49. static libraries only using:
  50. ./configure --disable-shared
  51. Java and Python Installation
  52. ============================
  53. The Java and Python runtime libraries for Protocol Buffers are located
  54. in the java and python directories. See the README file in each
  55. directory for more information on how to compile and install them.
  56. Note that both of them require you to first install the Protocol
  57. Buffer compiler (protoc), which is part of the C++ package.
  58. Usage
  59. =====
  60. The complete documentation for Protocol Buffers is available via the
  61. web at:
  62. http://code.google.com/apis/protocolbuffers/