vyasr opened a new issue, #400: URL: https://github.com/apache/arrow-nanoarrow/issues/400
nanoarrow is designed to be a lightweight dependency easily consumed as part of the build process of its dependents. Although primarily designed around vendoring, in practice there are numerous ways in which a consumer might expect to be able to use nanoarrow, including: - Building against a preinstalled (dynamic or static) nanoarrow (#350, #254) - Building against a prebuilt, not installed nanoarrow build directory. - Building against a copy of nanoarrow fetched at build time (#364) - Vendoring the files directly. IIUC in this case the expectation is that the dist/ files are the ones that are meant to be vendored, and those files are produced by building setting the `NANOARROW_BUNDLE` flag on (automated by [this GHA](https://github.com/apache/arrow-nanoarrow/blob/main/.github/workflows/bundle.yaml)). Additionally, users may wish to use dynamic or static nanoarrow libraries. Given this range of use cases, I think it would be very helpful to add explicit testing of usage of nanoarrow in different scenarios. A good way to do this would probably be to add [more examples](https://github.com/apache/arrow-nanoarrow/tree/main/examples) since it looks like those are [also being built in CI](https://github.com/apache/arrow-nanoarrow/blob/main/.github/workflows/examples.yaml). If there is interest in this. I am happy to volunteer my time to contribute some of these and improve nanoarrow's CMake along the way since I know CMake can be a bit tricky to work with. I can open issues and add associated examples + fixes as I find them. Handling this systematically would IMHO be a very useful way to increase consumer confidence in being able to use nanoarrow reliably. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
