Unlike camel-salesforce, camel-grpc doesn't actually compile any protobuf definitions, so protoc never gets called.
I think that the upshot here is that the Camel build will fail on Windows/ARM, but since the official release isn't built there anyway it's not a major concern. I did file a feature request on the protocolbuffers project to add Windows/ARM support. https://github.com/protocolbuffers/protobuf/issues/16877 For now, I will just add a comment to the camel-salesforce-component POM to let folks know that building it on Windows/ARM is currently not possible. On Fri, May 17, 2024 at 1:05 AM James Netherton <jamesnether...@gmail.com> wrote: > Maybe take a look at camel-grpc to see how protoc is handled for the > various platforms & CPU architectures: > > https://github.com/apache/camel/blob/main/components/camel-grpc/pom.xml > > -- > James > > On Thu, 16 May 2024 at 19:17, Craig Ziesman <czies...@redhat.com> wrote: > > > I opened an issue (https://issues.apache.org/jira/browse/CAMEL-20706) to > > address the fact that the camel-salesforce component build fails on > Windows > > running on ARM. > > > > It turns out that the source builds without errors, but the test build > > fails because the protoc executable is unavailable on Windows/ARM. > > > > I looked through the tooling and it appears that there is no way to > exclude > > a component from a particular Camel distribution based on a specific > > OS/architecture. > > > > Has this come up before? Is this even an issue? Just curious what > everybody > > thinks. > > > > Thanks for listening! > > >
