github-mirror/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell.git synced 2024-12-13 09:24:03 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
30ae715183
fish-shell/fish-rust/Cargo.toml

71 lines
2.5 KiB
TOML
Raw Normal View History

Initial Rust commit
2023-01-15 06:56:24 +08:00
[package]
name = "fish-rust"
version = "0.1.0"
edition = "2021"
Run rustfmt and clippy in CI (#9616) * Add machine-readable MSRV to Cargo.toml * Fix clippy warnings * CI: add rustfmt and clippy checks
2023-02-27 03:20:20 +08:00
rust-version = "1.67"
Initial Rust commit
2023-01-15 06:56:24 +08:00
[dependencies]
widestring-suffix = { path = "./widestring-suffix/" }
Use the rust-pcre2 crate for regex This adds support for our (forked) rust-pcre2 crate.
2023-03-26 06:57:20 +08:00
pcre2 = { git = "https://github.com/fish-shell/rust-pcre2", branch = "master", default-features = false, features = ["utf32"] }
Add our fast-float crate This adds a dependency on https://github.com/fish-shell/fast-float-rust which is our forked fast-float crate for parsing.
2023-03-27 04:37:38 +08:00
fast-float = { git = "https://github.com/fish-shell/fast-float-rust", branch="fish" }
Use hexponent to implement hex float parsing in wcstod This teaches wcstod to parse hex floats like 0x1.5p3 via a forked version of hexponent. This support is necessary for printf.
2023-04-02 09:26:20 +08:00
hexponent = { git = "https://github.com/fish-shell/hexponent", branch="fish" }
Replace the printf implementation The existing printf implementation is too buggy to back the printf builtin. Switch to the new implementation based on printf-compat.
2023-03-06 11:52:14 +08:00
printf-compat = { git = "https://github.com/fish-shell/printf-compat.git", branch="fish" }
Initial Rust commit
2023-01-15 06:56:24 +08:00
autocxx = "0.23.1"
builtins: Rewrite `pwd` in Rust Closes #9625.
2023-03-01 13:05:27 +08:00
bitflags = "1.3.2"
Initial Rust commit
2023-01-15 06:56:24 +08:00
cxx = "1.0"
errno = "0.2.8"
Add an FFI test facility This allow testing Rust functions (from fish_tests.cpp) which need to cross the FFI. See the example in smoke.rs.
2023-01-16 06:56:04 +08:00
inventory = { version = "0.3.3", optional = true}
Env stubs for path port
2023-04-20 00:35:33 +08:00
lazy_static = "1.4.0"
Initial Rust commit
2023-01-15 06:56:24 +08:00
libc = "0.2.137"
Cargo.toml: sort dependencies
2023-03-26 23:24:35 +08:00
lru = "0.10.0"
Introduce wcstring_list_ffi_t wcstring_list_ffi_t is an autocxx-friendly type for passing lists of strings from C++ to Rust.
2023-04-11 03:19:36 +08:00
moveit = "0.5.1"
Fix linking errors under FreeBSD The nix crate had all its default features enabled, which included features that are not present under BSD. We should only enable the select subset of crate features that we know are available cross-platform (or else use conditional targeting in Cargo.toml to only enable Linux-only features when compiling for Linux targets). For now, it seems we can just use the nix crate with all features disabled as it still builds under Linux and FreeBSD in this state.
2023-02-03 03:10:15 +08:00
nix = { version = "0.25.0", default-features = false, features = [] }
Initial Rust commit
2023-01-15 06:56:24 +08:00
num-traits = "0.2.15"
Use once_cell instead of lazy_static lazy_static has better ergonomics at the call/access sites (it returns a reference to the type directly, whereas with once_cell we get a static Lazy<T> that we must dereference instead) but the once_cell api is slated for integration into the standard library [0] and has been the "preferred" way to declare static global variables w/ deferred initialization. It's also less opaque and easier to comprehend how it works, I guess? (Both `once_cell` and `lazy_static` are already in our dependency tree, so this should have no detrimental effect on build times. It actually negligibly *improves* build times by not using macros, reducing the amount of expansion the compiler has to do by a miniscule amount.) [0]: https://github.com/rust-lang/rust/issues/74465
2023-02-06 07:53:48 +08:00
once_cell = "1.17.0"
Port random to rust
2023-02-19 05:06:05 +08:00
rand = { version = "0.8.5", features = ["small_rng"] }
Initial Rust commit
2023-01-15 06:56:24 +08:00
unixstring = "0.2.7"
widestring = "1.0.2"
[build-dependencies]
autocxx-build = "0.23.1"
Port common.{h,cpp} to Rust Most of it is duplicated, hence untested. Functions like mbrtowc are not exposed by the libc crate, so declare them ourselves. Since we don't know the definition of C macros, add two big hacks to make this work: 1. Replace MB_LEN_MAX and mbstate_t with values (resp types) that should be large enough for any implementation. 2. Detect the definition of MB_CUR_MAX in the build script. This requires more changes for each new libc. We could also use this approach for 1. Additionally, this commit brings a small behavior change to read_unquoted_escape(): we cannot decode surrogate code points like \UDE01 into a Rust char, so use � (\UFFFD, replacement character) instead. Previously, we added such code points to a wcstring; looks like they were ignored when printed.
2023-03-26 23:23:05 +08:00
cc = { git = "https://github.com/mqudsi/cc-rs", branch = "fish" }
Point fish autocxx and similar dependencies at new fish-shell location These crates have been moved into fish-shell org; update Cargo.toml to reflect that.
2023-03-10 13:01:49 +08:00
cxx-build = { git = "https://github.com/fish-shell/cxx", branch = "fish" }
cxx-gen = { git = "https://github.com/fish-shell/cxx", branch = "fish" }
Initial Rust commit
2023-01-15 06:56:24 +08:00
miette = { version = "5", features = ["fancy"] }
[lib]
Add BSD feature This should be used in lieu of manually targeting individual operating systems when using features shared by all BSD families. e.g. instead of #[cfg(any(target_os = "freebsd", target_os = "dragonflybsd", ...))] fn foo() { } you would use #[cfg(feature = "bsd")] fn foo() { } This feature is automatically detected at build-time (see build.rs changes) and should *not* be enabled manually. Additionally, this feature may not be used to conditionally require any other dependency, as that isn't supported for auto-enabled features.
2023-03-20 06:50:32 +08:00
crate-type = ["staticlib"]
Initial Rust commit
2023-01-15 06:56:24 +08:00
Add an FFI test facility This allow testing Rust functions (from fish_tests.cpp) which need to cross the FFI. See the example in smoke.rs.
2023-01-16 06:56:04 +08:00
[features]
# The fish-ffi-tests feature causes tests to be built which need to use the FFI.
# These tests are run by fish_tests().
default = ["fish-ffi-tests"]
fish-ffi-tests = ["inventory"]
Add BSD feature This should be used in lieu of manually targeting individual operating systems when using features shared by all BSD families. e.g. instead of #[cfg(any(target_os = "freebsd", target_os = "dragonflybsd", ...))] fn foo() { } you would use #[cfg(feature = "bsd")] fn foo() { } This feature is automatically detected at build-time (see build.rs changes) and should *not* be enabled manually. Additionally, this feature may not be used to conditionally require any other dependency, as that isn't supported for auto-enabled features.
2023-03-20 06:50:32 +08:00
# The following features are auto-detected by the build-script and should not be enabled manually.
bsd = []
Initial Rust commit
2023-01-15 06:56:24 +08:00
[patch.crates-io]
Fix rust-invoked build of c/cpp sources under FreeBSD Due to an upstream issue with cc-rs [0], the rust-generated C++ interface would fail to compile. A PR has been opened to patch the issue upstream [1], but in the meantime `Cargo.toml` has been patched to use a fork of cc-rs with the relevant fixes. [0]: https://github.com/rust-lang/cc-rs/issues/463 [1]: https://github.com/rust-lang/cc-rs/pull/785
2023-02-03 03:04:16 +08:00
cc = { git = "https://github.com/mqudsi/cc-rs", branch = "fish" }
Point fish autocxx and similar dependencies at new fish-shell location These crates have been moved into fish-shell org; update Cargo.toml to reflect that.
2023-03-10 13:01:49 +08:00
cxx = { git = "https://github.com/fish-shell/cxx", branch = "fish" }
cxx-gen = { git = "https://github.com/fish-shell/cxx", branch = "fish" }
autocxx = { git = "https://github.com/fish-shell/autocxx", branch = "fish" }
autocxx-build = { git = "https://github.com/fish-shell/autocxx", branch = "fish" }
autocxx-bindgen = { git = "https://github.com/fish-shell/autocxx-bindgen", branch = "fish" }
Initial Rust commit
2023-01-15 06:56:24 +08:00
Point fish autocxx and similar dependencies at new fish-shell location These crates have been moved into fish-shell org; update Cargo.toml to reflect that.
2023-03-10 13:01:49 +08:00
[patch.'https://github.com/fish-shell/cxx']
Fix rust-invoked build of c/cpp sources under FreeBSD Due to an upstream issue with cc-rs [0], the rust-generated C++ interface would fail to compile. A PR has been opened to patch the issue upstream [1], but in the meantime `Cargo.toml` has been patched to use a fork of cc-rs with the relevant fixes. [0]: https://github.com/rust-lang/cc-rs/issues/463 [1]: https://github.com/rust-lang/cc-rs/pull/785
2023-02-03 03:04:16 +08:00
cc = { git = "https://github.com/mqudsi/cc-rs", branch = "fish" }
Point fish autocxx and similar dependencies at new fish-shell location These crates have been moved into fish-shell org; update Cargo.toml to reflect that.
2023-03-10 13:01:49 +08:00
[patch.'https://github.com/fish-shell/autocxx']
Fix rust-invoked build of c/cpp sources under FreeBSD Due to an upstream issue with cc-rs [0], the rust-generated C++ interface would fail to compile. A PR has been opened to patch the issue upstream [1], but in the meantime `Cargo.toml` has been patched to use a fork of cc-rs with the relevant fixes. [0]: https://github.com/rust-lang/cc-rs/issues/463 [1]: https://github.com/rust-lang/cc-rs/pull/785
2023-02-03 03:04:16 +08:00
cc = { git = "https://github.com/mqudsi/cc-rs", branch = "fish" }
Initial Rust commit
2023-01-15 06:56:24 +08:00
#cxx = { path = "../../cxx" }
#cxx-gen = { path="../../cxx/gen/lib" }
#autocxx = { path = "../../autocxx" }
#autocxx-build = { path = "../../autocxx/gen/build" }
#autocxx-bindgen = { path = "../../autocxx-bindgen" }
Enable rust overflow checks in release mode, at least for now We want to try and catch as much unexpected/non-deterministic behavior as we can. We could run the CI explicitly in debug mode, but I think it makes sense to always have overflow checks on in both debug/release modes everywhere, at least for the duration of the codebase transition.
2023-02-21 03:11:29 +08:00
[profile.release]
overflow-checks = true
Reference in New Issue Copy Permalink