diff options
author | kenton@google.com <kenton@google.com@630680e5-0e50-0410-840e-4b1c322b438d> | 2009-05-06 17:49:37 +0000 |
---|---|---|
committer | kenton@google.com <kenton@google.com@630680e5-0e50-0410-840e-4b1c322b438d> | 2009-05-06 17:49:37 +0000 |
commit | 9824eda6b558cd88c63064017593521ecad2029f (patch) | |
tree | 51283c7de8f20ac7f54331296c8743fd5ab62b8c /README.txt | |
parent | 42c81e1a764d565823c203e9e07376379639ffa7 (diff) | |
download | protobuf-9824eda6b558cd88c63064017593521ecad2029f.tar.gz protobuf-9824eda6b558cd88c63064017593521ecad2029f.tar.bz2 protobuf-9824eda6b558cd88c63064017593521ecad2029f.zip |
enable cross-compiling
Diffstat (limited to 'README.txt')
-rw-r--r-- | README.txt | 23 |
1 files changed, 23 insertions, 0 deletions
@@ -33,6 +33,29 @@ For advanced usage information on configure and make, see INSTALL.txt. If you already built the package with a different prefix, make sure to run "make clean" before building again. +** Note for cross-compiling ** + + The makefiles normally invoke the protoc executable that they just + built in order to build tests. When cross-compiling, the protoc + executable may not be executable on the host machine. In this case, + you must build a copy of protoc for the host machine first, then use + the --with-protoc option to tell configure to use it instead. For + example: + + ./configure --with-protoc=protoc + + This will use the installed protoc (found in your $PATH) instead of + trying to execute the one built during the build process. You can + also use an executable that hasn't been installed. For example, if + you built the protobuf package for your host machine in ../host, + you might do: + + ./configure --with-protoc=../host/src/protoc + + Either way, you must make sure that the protoc executable you use + has the same version as the protobuf source code you are trying to + use it with. + ** Note for Solaris users ** Solaris 10 x86 has a bug that will make linking fail, complaining |