XueSongTap commented on issue #2279: URL: https://github.com/apache/fory/issues/2279#issuecomment-2952747096
hi @chaokunyang While migrating to Bazel 8 (with Bzlmod), I encountered an issue with some third-party dependencies that do not provide a native `MODULE.bazel` file (for example, `simdutf`). It seems there are two possible ways to handle this: 1. Use the legacy `WORKSPACE` mechanism with `http_archive`, and enable it via the `--enable_workspace` flag — but this feels counter to Bazel 8’s push toward fully adopting Bzlmod. 2. Vendor the third-party dependency locally, for example add `simdutf.h` 、`simdutf.cpp`、`MODULE.bazel` and `BUILD` file at `cpp/fory/thirdparty`, and use `local_path_override` to integrate it via Bzlmod. From a long-term maintenance and best practices standpoint, which approach is recommended for projects migrating to Bazel 8+? Would appreciate some guidance — thanks! -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
