This partially simplifies the local native vec testing, more work to be done

[benwtrent]

This changes the work flow a bit:

To build and copy, you simply need to do:

# indicate that we are using local build
export LOCAL_VEC_BINARY_OS=darwin
# get to the build dir
cd libs/simdvec/native
# build it and copy it
JAVA_HOME=$JAVA21_HOME ./gradlew buildSharedLibraryAndCopy
# do what you want, it will now use the locally built value

[elasticsearchmachine]

Pinging @elastic/es-search-relevance (Team:Search Relevance)

[rjernst]

@mark-vieira is there a more canonical way to wire this for local building over to libs/native?

[mark-vieira]

The more idiomatic way would probably be to use composite builds here. If we configured this project to publish the zip as an artifact, configure it with the same maven coordinates as the binary artifact, then in theory we could just use --include-build libs/simdvec/native to get the same behavior.

[benwtrent]

I don't know what composite builds are :/

My end goal is to provide simplified mechanisms not only for local testing but to unlock us writing up some buildkite jobs to build and benchmark native code changes (will be in subsequent PRs).

[mark-vieira]

If this unblocks you for now, seems fine to me. We can always improve this. @elastic/es-delivery should have some eyes on this though.