Hi The intent is not for end users to build their own camel distribution. The source code is built and released to maven central as JARs, where end users will consume the releases.
If there are odd combinations of osx and cpu arch where some camel components cannot build special code like protobuf then "so be it". However your work to try to make the source build and skip that "odd combo" for this particular situation is appreciated, and if you can help find to get the PR working then that would be good. On Thu, May 16, 2024 at 8:17 PM 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! > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
