You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@fury.apache.org by "chaokunyang (via GitHub)" <gi...@apache.org> on 2025/06/02 16:12:39 UTC
[I] [Python][C++] Upgrade bazel 6 to bazel 8 [fury]
chaokunyang opened a new issue, #2279:
URL: https://github.com/apache/fury/issues/2279
### Feature Request
Upgrade bazel 6 to bazel 8 to use bazel module to manage dependencies.
### Is your feature request related to a problem? Please describe
_No response_
### Describe the solution you'd like
_No response_
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
--
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: commits-unsubscribe@fury.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fury.apache.org
For additional commands, e-mail: commits-help@fury.apache.org
Re: [I] [Python][C++] Upgrade bazel 6 to bazel 8 [fory]
Posted by "chaokunyang (via GitHub)" <gi...@apache.org>.
chaokunyang commented on issue #2279:
URL: https://github.com/apache/fory/issues/2279#issuecomment-2952795295
We will use bazel module in the long run. But we can do it step by step. We could first use `--enable_workspace` to upgrade to bazel 8 first, then switch to bazel module in another PR.
And simdutf.h didn't provide bazel support, fory just use its source file and create a cc_library rule for it:
```bazel
# WORKSPACFE
http_archive(
name = "simdutf",
urls = ["https://github.com/simdutf/simdutf/releases/download/v6.1.2/singleheader.zip"],
sha256 = "41bb25074fe1e917e96e539c7a87c502e530d88746d7c25d06fb55a28b884340",
build_file = "//cpp/fory/thirdparty:BUILD",
)
# BUILD
cc_library(
name = "simdutf",
srcs = ["simdutf.cpp"],
hdrs = ["simdutf.h"],
includes = ["."],
visibility = ["//visibility:public"],
)
```
--
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: commits-unsubscribe@fory.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fory.apache.org
For additional commands, e-mail: commits-help@fory.apache.org
Re: [I] [Python][C++] Upgrade bazel 6 to bazel 8 [fury]
Posted by "chaokunyang (via GitHub)" <gi...@apache.org>.
chaokunyang commented on issue #2279:
URL: https://github.com/apache/fury/issues/2279#issuecomment-2933758088
https://github.com/grpc/grpc/pull/38254 This can be taken as a reference
--
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: commits-unsubscribe@fury.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fury.apache.org
For additional commands, e-mail: commits-help@fury.apache.org
Re: [I] [Python][C++] Upgrade bazel 6 to bazel 8 [fory]
Posted by "chaokunyang (via GitHub)" <gi...@apache.org>.
chaokunyang closed issue #2279: [Python][C++] Upgrade bazel 6 to bazel 8
URL: https://github.com/apache/fory/issues/2279
--
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: commits-unsubscribe@fory.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fory.apache.org
For additional commands, e-mail: commits-help@fory.apache.org
Re: [I] [Python][C++] Upgrade bazel 6 to bazel 8 [fury]
Posted by "XueSongTap (via GitHub)" <gi...@apache.org>.
XueSongTap commented on issue #2279:
URL: https://github.com/apache/fury/issues/2279#issuecomment-2933738460
Can I work on this?
--
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: commits-unsubscribe@fury.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fury.apache.org
For additional commands, e-mail: commits-help@fury.apache.org
Re: [I] [Python][C++] Upgrade bazel 6 to bazel 8 [fury]
Posted by "chaokunyang (via GitHub)" <gi...@apache.org>.
chaokunyang commented on issue #2279:
URL: https://github.com/apache/fury/issues/2279#issuecomment-2933752774
> Can I work on this?
Sure, welcome!
--
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: commits-unsubscribe@fury.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fury.apache.org
For additional commands, e-mail: commits-help@fury.apache.org
Re: [I] [Python][C++] Upgrade bazel 6 to bazel 8 [fory]
Posted by "XueSongTap (via GitHub)" <gi...@apache.org>.
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: commits-unsubscribe@fory.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fory.apache.org
For additional commands, e-mail: commits-help@fory.apache.org