Keith Smiley
Keith Smiley
With `cc_sysroot` it's valid to provide just something like this: ```bzl cc_sysroot( name = "sysroot", sysroot = "@sdk//:dir", ) ``` Without actually propagating the files to the actions that rely...
When trying to write a toolchain with the new rule based mechanism, on macOS we likely need some feature like this: ```bzl cc_args( name = "apple_sysroot", actions = [ "@rules_cc//cc/toolchains/actions:compile_actions",...
Fixes https://github.com/aspect-build/rules_py/issues/461
### What happened? This is a new version of https://github.com/aspect-build/rules_py/issues/426 It seems like this is somehow rules_py specific. It works fine with py_test from rules_python, or a brand new test...
### What happened? Using rules_python's py_binary like this: ```bzl py_binary( name = "upstream_py_binary", srcs = ["say.py"], main = "say.py", ) py_binary( name = "upstream_py_binary2", srcs = ["say.py"], main = "say.py",...
This mirrors rules_python to ensure that users can use `execpath` with a py_binary target. Fixes https://github.com/aspect-build/rules_py/issues/455
In rules_python you can specify a file from another package like: ```bzl main = "//path/to:file.py", ``` This didn't work in rules_py since it was taking the main as a string...
Using a config_setting based on cpu is deprecated
This was only used to fix the install_name of shared libraries, which is now obsolete since they are set correctly by the crosstool with `-install_name`.
For some complex configurations uv recommends using `extras` to install different versions of the same dependency: https://github.com/astral-sh/uv/blob/dc39d6622be268318acfb43a758c6ea688b722ea/docs/guides/integration/pytorch.md#configuring-accelerators-with-optional-dependencies In this examples those extras markers are encoded in the uv.lock, and it...