Hi!, I've successfully build the protoc executable (version 2.5.0) and configured maven to run protoc for me.
This means I've got my local setup working for me; compiling new Java sources for the .proto definition files on the fly. The protoc executable, however, contains some hard-coded absolute paths to locations from my local system. This means that every developer working on the project has to go trough the hassle of compiling the correct version of protoc themselves, which is a nuisance. Not to mention the issues with our Continues Integration tool (travis-ci) which will spawn a fresh VM every run. That would mean that we'd need to configure Travis to compile the protoc executable every time. I'd rather just ship the executable with the project. I'd compile a 64 and 32 bit version, for example, and configure maven to use the correct one. The workaround for now will exist out of checking the compile Java classes into Git; but I really dislike checking generated sources, so I'd rather just ship the executable. Does anyone know of a way to create a portable protoc executable? Kind Regards, Matthias -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/groups/opt_out.
