search

Jay-Zeng / monav

Automatically exported from code.google.com/p/monav
0 stars 0 forks source link

Unable to compile preprocessor with protobuf 2.4.0a #45

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Try to compile the preprocessor
2.
3.

Expected output: preprocessor binary

What do I see:
../osmimporter/protobuff definitions/fileformat.pb.h:17:2: error: #error This 
file was generated by an older version of protoc which is
../osmimporter/protobuff definitions/fileformat.pb.h:18:2: error: #error 
incompatible with your Protocol Buffer headers. Please
../osmimporter/protobuff definitions/fileformat.pb.h:19:2: error: #error 
regenerate this file with a newer version of protoc.

What version of the product are you using? On what operating system?
SVN r480

Please provide any additional information below.

I'm trying to make a PKGBUILD for Arch Linux so that people can try the latest 
version in trunk easily, however Arch Linux currently offers Protobuf 2.4.0a 
which breaks compilation. Changing fileformat.pb.h definitions manually to 
allow this version produces a working executable though.

Original issue reported on code.google.com by kam1k...@gmail.com on 11 Apr 2011 at 3:11

GoogleCodeExporter commented 9 years ago 
Forgot to mention, OS is Arch Linux amd64.

Original comment by kam1k...@gmail.com on 11 Apr 2011 at 3:13

GoogleCodeExporter commented 9 years ago 
Yeah, I noticed that on Arch Linux already. Do you know whether 2.4.0a is an 
early alpha and they will be backwards compatible in the final version, or if 
2.4.0 will also break compatibility?

Original comment by veaac.fd...@gmail.com on 11 Apr 2011 at 3:21

GoogleCodeExporter commented 9 years ago 
Not sure about it being alpha or not, but it defines 
GOOGLE_PROTOBUF_MIN_PROTOC_VERSION as being 200400, which leads me to believe 
the API is not entirely backwards compatible.

Original comment by kam1k...@gmail.com on 11 Apr 2011 at 3:28

GoogleCodeExporter commented 9 years ago 
I think I will switch to generating these files on the fly, but it might take 
some days. In the meantime you can generate yourself a 2.4.0a compatible 
version using the .proto files:

   protoc -I=sourceDir --cpp_out=destDir file.proto

Original comment by veaac.fd...@gmail.com on 11 Apr 2011 at 3:55

GoogleCodeExporter commented 9 years ago 
Appears to be working nicely. I'll have to make some tests when I have more 
time to be sure though.

Thanks for the tip :)

Original comment by kam1k...@gmail.com on 11 Apr 2011 at 4:54

GoogleCodeExporter commented 9 years ago 
Could you try out r509?

Original comment by veaac.fd...@gmail.com on 13 Apr 2011 at 3:19

GoogleCodeExporter commented 9 years ago 
r509 doesn't compile (still complains about the protobuf headers).

However r510 is working fine.

Original comment by kam1k...@gmail.com on 13 Apr 2011 at 3:30

GoogleCodeExporter commented 9 years ago

Original comment by veaac.fd...@gmail.com on 13 Apr 2011 at 3:41