langfingaz/anki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
ed9476c856
anki/cargo/remote/BUILD.futures-util-0.3.21.bazel

129 lines
2.9 KiB
Plaintext
Raw Normal View History

initial Bazel conversion Running and testing should be working on the three platforms, but there's still a fair bit that needs to be done: - Wheel building + testing in a venv still needs to be implemented. - Python requirements still need to be compiled with piptool and pinned; need to compile on all platforms then merge - Cargo deps in cargo/ and rslib/ need to be cleaned up, and ideally unified into one place - Currently using rustls to work around openssl compilation issues on Linux, but this will break corporate proxies with custom SSL authorities; need to conditionally use openssl or use https://github.com/seanmonstar/reqwest/pull/1058 - Makefiles and docs still need cleaning up - It may make sense to reparent ts/* to the top level, as we don't nest the other modules under a specific language. - rspy and pylib must always be updated in lock-step, so merging rspy into pylib as a private module would simplify things. - Merging desktop-ftl and mobile-ftl into the core ftl would make managing and updating translations easier. - Obsolete scripts need removing. - And probably more.
2020-11-01 05:26:58 +01:00
"""
@generated
cargo-raze crate build file.
DO NOT EDIT! Replaced on runs of cargo-raze
"""
update to the latest rules_rust + security framework update
2021-03-27 09:39:02 +01:00
# buildifier: disable=load
load("@bazel_skylib//lib:selects.bzl", "selects")
initial Bazel conversion Running and testing should be working on the three platforms, but there's still a fair bit that needs to be done: - Wheel building + testing in a venv still needs to be implemented. - Python requirements still need to be compiled with piptool and pinned; need to compile on all platforms then merge - Cargo deps in cargo/ and rslib/ need to be cleaned up, and ideally unified into one place - Currently using rustls to work around openssl compilation issues on Linux, but this will break corporate proxies with custom SSL authorities; need to conditionally use openssl or use https://github.com/seanmonstar/reqwest/pull/1058 - Makefiles and docs still need cleaning up - It may make sense to reparent ts/* to the top level, as we don't nest the other modules under a specific language. - rspy and pylib must always be updated in lock-step, so merging rspy into pylib as a private module would simplify things. - Merging desktop-ftl and mobile-ftl into the core ftl would make managing and updating translations easier. - Obsolete scripts need removing. - And probably more.
2020-11-01 05:26:58 +01:00
# buildifier: disable=load
load(
update Rust deps with cargo-raze 0.13.0
2021-10-26 00:16:40 +02:00
"@rules_rust//rust:defs.bzl",
initial Bazel conversion Running and testing should be working on the three platforms, but there's still a fair bit that needs to be done: - Wheel building + testing in a venv still needs to be implemented. - Python requirements still need to be compiled with piptool and pinned; need to compile on all platforms then merge - Cargo deps in cargo/ and rslib/ need to be cleaned up, and ideally unified into one place - Currently using rustls to work around openssl compilation issues on Linux, but this will break corporate proxies with custom SSL authorities; need to conditionally use openssl or use https://github.com/seanmonstar/reqwest/pull/1058 - Makefiles and docs still need cleaning up - It may make sense to reparent ts/* to the top level, as we don't nest the other modules under a specific language. - rspy and pylib must always be updated in lock-step, so merging rspy into pylib as a private module would simplify things. - Merging desktop-ftl and mobile-ftl into the core ftl would make managing and updating translations easier. - Obsolete scripts need removing. - And probably more.
2020-11-01 05:26:58 +01:00
"rust_binary",
"rust_library",
update Rust deps with cargo-raze 0.13.0
2021-10-26 00:16:40 +02:00
"rust_proc_macro",
initial Bazel conversion Running and testing should be working on the three platforms, but there's still a fair bit that needs to be done: - Wheel building + testing in a venv still needs to be implemented. - Python requirements still need to be compiled with piptool and pinned; need to compile on all platforms then merge - Cargo deps in cargo/ and rslib/ need to be cleaned up, and ideally unified into one place - Currently using rustls to work around openssl compilation issues on Linux, but this will break corporate proxies with custom SSL authorities; need to conditionally use openssl or use https://github.com/seanmonstar/reqwest/pull/1058 - Makefiles and docs still need cleaning up - It may make sense to reparent ts/* to the top level, as we don't nest the other modules under a specific language. - rspy and pylib must always be updated in lock-step, so merging rspy into pylib as a private module would simplify things. - Merging desktop-ftl and mobile-ftl into the core ftl would make managing and updating translations easier. - Obsolete scripts need removing. - And probably more.
2020-11-01 05:26:58 +01:00
"rust_test",
)
package(default_visibility = [
# Public for visibility by "@raze__crate__version//" targets.
#
# Prefer access through "//cargo", which limits external
# visibility to explicit Cargo.toml dependencies.
"//visibility:public",
])
licenses([
"notice", # MIT from expression "MIT OR Apache-2.0"
])
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
# Generated Targets
update Rust deps
2021-06-16 08:10:57 +02:00
# buildifier: disable=out-of-order-load
# buildifier: disable=load-on-top
load(
"@rules_rust//cargo:cargo_build_script.bzl",
"cargo_build_script",
)
cargo_build_script(
name = "futures_util_build_script",
srcs = glob(["**/*.rs"]),
build_script_env = {
},
crate_features = [
"alloc",
"async-await",
"async-await-macro",
"channel",
"default",
"futures-channel",
"futures-io",
"futures-macro",
"futures-sink",
"io",
"memchr",
"sink",
"slab",
"std",
],
crate_root = "build.rs",
data = glob(["**"]),
edition = "2018",
rustc_flags = [
"--cap-lints=allow",
],
tags = [
"cargo-raze",
"manual",
],
Update Rust deps; pin Tokio Tokio has had to be pinned, because the 1.17 release introduces a dependency on windows_sys, which fails to build on Windows on Bazel. The issue appears to be the build script of a subcrate - it is using CARGO_MANIFEST_DIR to update the linking path so windows.lib can be found (it's contained in that crate), but the path is set incorrectly. https://github.com/microsoft/windows-rs/blob/dfc25285a289847ad88cbd206d169f7697be0dd4/crates/targets/x86_64_msvc/build.rs One way we might be able to work around it is to add to the link path in our own build script.
2022-02-25 07:30:59 +01:00
version = "0.3.21",
update Rust deps
2021-06-16 08:10:57 +02:00
visibility = ["//visibility:private"],
deps = [
],
)
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
Update Rust deps; pin Tokio Tokio has had to be pinned, because the 1.17 release introduces a dependency on windows_sys, which fails to build on Windows on Bazel. The issue appears to be the build script of a subcrate - it is using CARGO_MANIFEST_DIR to update the linking path so windows.lib can be found (it's contained in that crate), but the path is set incorrectly. https://github.com/microsoft/windows-rs/blob/dfc25285a289847ad88cbd206d169f7697be0dd4/crates/targets/x86_64_msvc/build.rs One way we might be able to work around it is to add to the link path in our own build script.
2022-02-25 07:30:59 +01:00
# Unsupported target "flatten_unordered" with type "bench" omitted
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
# Unsupported target "futures_unordered" with type "bench" omitted
initial Bazel conversion Running and testing should be working on the three platforms, but there's still a fair bit that needs to be done: - Wheel building + testing in a venv still needs to be implemented. - Python requirements still need to be compiled with piptool and pinned; need to compile on all platforms then merge - Cargo deps in cargo/ and rslib/ need to be cleaned up, and ideally unified into one place - Currently using rustls to work around openssl compilation issues on Linux, but this will break corporate proxies with custom SSL authorities; need to conditionally use openssl or use https://github.com/seanmonstar/reqwest/pull/1058 - Makefiles and docs still need cleaning up - It may make sense to reparent ts/* to the top level, as we don't nest the other modules under a specific language. - rspy and pylib must always be updated in lock-step, so merging rspy into pylib as a private module would simplify things. - Merging desktop-ftl and mobile-ftl into the core ftl would make managing and updating translations easier. - Obsolete scripts need removing. - And probably more.
2020-11-01 05:26:58 +01:00
rust_library(
name = "futures_util",
srcs = glob(["**/*.rs"]),
crate_features = [
"alloc",
"async-await",
"async-await-macro",
"channel",
"default",
"futures-channel",
"futures-io",
"futures-macro",
"futures-sink",
"io",
"memchr",
"sink",
"slab",
"std",
],
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
crate_root = "src/lib.rs",
update to latest cargo-raze
2020-12-15 11:28:10 +01:00
data = [],
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
edition = "2018",
proc_macro_deps = [
Update Rust deps; pin Tokio Tokio has had to be pinned, because the 1.17 release introduces a dependency on windows_sys, which fails to build on Windows on Bazel. The issue appears to be the build script of a subcrate - it is using CARGO_MANIFEST_DIR to update the linking path so windows.lib can be found (it's contained in that crate), but the path is set incorrectly. https://github.com/microsoft/windows-rs/blob/dfc25285a289847ad88cbd206d169f7697be0dd4/crates/targets/x86_64_msvc/build.rs One way we might be able to work around it is to add to the link path in our own build script.
2022-02-25 07:30:59 +01:00
"@raze__futures_macro__0_3_21//:futures_macro",
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
],
rustc_flags = [
"--cap-lints=allow",
],
tags = [
"cargo-raze",
rebuild Rust build files with cargo-raze 0.14.1 Tags are now sorted; updating this before a crate update.
2022-01-15 05:33:53 +01:00
"crate-name=futures-util",
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
"manual",
],
Update Rust deps; pin Tokio Tokio has had to be pinned, because the 1.17 release introduces a dependency on windows_sys, which fails to build on Windows on Bazel. The issue appears to be the build script of a subcrate - it is using CARGO_MANIFEST_DIR to update the linking path so windows.lib can be found (it's contained in that crate), but the path is set incorrectly. https://github.com/microsoft/windows-rs/blob/dfc25285a289847ad88cbd206d169f7697be0dd4/crates/targets/x86_64_msvc/build.rs One way we might be able to work around it is to add to the link path in our own build script.
2022-02-25 07:30:59 +01:00
version = "0.3.21",
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
# buildifier: leave-alone
deps = [
update Rust deps
2021-06-16 08:10:57 +02:00
":futures_util_build_script",
Update Rust deps; pin Tokio Tokio has had to be pinned, because the 1.17 release introduces a dependency on windows_sys, which fails to build on Windows on Bazel. The issue appears to be the build script of a subcrate - it is using CARGO_MANIFEST_DIR to update the linking path so windows.lib can be found (it's contained in that crate), but the path is set incorrectly. https://github.com/microsoft/windows-rs/blob/dfc25285a289847ad88cbd206d169f7697be0dd4/crates/targets/x86_64_msvc/build.rs One way we might be able to work around it is to add to the link path in our own build script.
2022-02-25 07:30:59 +01:00
"@raze__futures_channel__0_3_21//:futures_channel",
"@raze__futures_core__0_3_21//:futures_core",
"@raze__futures_io__0_3_21//:futures_io",
"@raze__futures_sink__0_3_21//:futures_sink",
"@raze__futures_task__0_3_21//:futures_task",
update Rust deps
2021-10-02 12:42:03 +02:00
"@raze__memchr__2_4_1//:memchr",
update Rust deps
2022-01-15 05:59:43 +01:00
"@raze__pin_project_lite__0_2_8//:pin_project_lite",
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
"@raze__pin_utils__0_1_0//:pin_utils",
update Rust deps with cargo-raze 0.13.0
2021-10-26 00:16:40 +02:00
"@raze__slab__0_4_5//:slab",
update to cargo-raze 0.7.0 + latest deps Gives us wildcard entries in raze.toml, and solves warnings about unrecognized "raze" entries.
2020-11-10 00:47:24 +01:00
],
initial Bazel conversion Running and testing should be working on the three platforms, but there's still a fair bit that needs to be done: - Wheel building + testing in a venv still needs to be implemented. - Python requirements still need to be compiled with piptool and pinned; need to compile on all platforms then merge - Cargo deps in cargo/ and rslib/ need to be cleaned up, and ideally unified into one place - Currently using rustls to work around openssl compilation issues on Linux, but this will break corporate proxies with custom SSL authorities; need to conditionally use openssl or use https://github.com/seanmonstar/reqwest/pull/1058 - Makefiles and docs still need cleaning up - It may make sense to reparent ts/* to the top level, as we don't nest the other modules under a specific language. - rspy and pylib must always be updated in lock-step, so merging rspy into pylib as a private module would simplify things. - Merging desktop-ftl and mobile-ftl into the core ftl would make managing and updating translations easier. - Obsolete scripts need removing. - And probably more.
2020-11-01 05:26:58 +01:00
)
Reference in New Issue Copy Permalink