New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate the pre-built protoc like maven repo #16582
Comments
@hlopko Could you give some advice please? Thank you very much. |
Is it intentional that you're linking to release / documentation from v3.7.1? This is a very old release, and you should probably move to a supported protobuf version instead: https://protobuf.dev/support/version-support/ Can you elaborate more on why you need to manually generate our prebuilts? Using the artifacts published to maven is recommended. We generate these artifacts via internally using the |
Thank you for your patience and timely response!
It seems that the latest version is also not released for RISC-V, so I had to follow the prompts and build manually. |
What language does this apply to?
If it's a proto syntax change, is it for proto2 or proto3?
If it's about generated code change, what programming language?
Describe the problem you are trying to solve.
Similar to this question:
#14402
I want to manually generate the following files by myself:
https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/3.7.1/protoc-3.7.1-linux-x86_64.exe
I followed this documentation:
https://github.com/protocolbuffers/protobuf/blob/v3.7.1/src/README.md
And with the
./configure --disable-shared
parameter, theprotoc
file size generated bymake install
is 67MB, which is much larger than the exe file on maven repo.I would like to ask how to manually generate the pre-built files in the maven repo?
Thanks a lot!
Describe the solution you'd like
Manually generate the following files by myself:
https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/3.7.1/protoc-3.7.1-linux-x86_64.exe
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: