You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These 2 dependencies are not added to the resulting bazel file, generating the error no such target '@@crate_index//:phf_codegen-0.7.24': target 'phf_codegen-0.7.24' not declared in package
It was working well in 0.56.0 and started failing in 0.57.0
After debugging I realized the version 0.5.6 keeps the build_deps with full names "phf_codegen": Label("@crate_index__phf_codegen-0.7.24//:phf_codegen") however the new versions include them as "phf_codegen": Label("//:phf_codegen-0.7.24"), but the alias is not created in the main BUILD.bazel file. The change was introduced here 5e90483#diff-a165d4fcf7bc187750bb12572611029ff1522d224f1b4cc96483e6184e254c52
The text was updated successfully, but these errors were encountered:
When using build dependencies inside a Cargo.toml in a workspace, the rendered BUILD.bazel in crates_index does not include the build dependencies
I have the following build dependencies
These 2 dependencies are not added to the resulting bazel file, generating the error
no such target '@@crate_index//:phf_codegen-0.7.24': target 'phf_codegen-0.7.24' not declared in package
It was working well in 0.56.0 and started failing in 0.57.0
After debugging I realized the version 0.5.6 keeps the build_deps with full names
"phf_codegen": Label("@crate_index__phf_codegen-0.7.24//:phf_codegen")
however the new versions include them as"phf_codegen": Label("//:phf_codegen-0.7.24"),
but the alias is not created in the main BUILD.bazel file. The change was introduced here 5e90483#diff-a165d4fcf7bc187750bb12572611029ff1522d224f1b4cc96483e6184e254c52The text was updated successfully, but these errors were encountered: