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