Rust-GPU / Rust-GPU/rust-gpu.github.io
Guide doesn't seem to work
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- MDX
- Sterne
- 16
- Forks
- 8
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Apologies in advance for a mess of an issue, I'm struggling to get started with rust-gpu and running in to different issues with the docs.
I tried to follow https://rust-gpu.github.io/rust-gpu/book/writing-shader-crates.html but something seems off there and I'm not sure what, been struggling with it for hours.
First error I get is
error: failed to run custom build command for `rustc_codegen_spirv v0.9.0`
Caused by:
process didn't exit successfully: `[path]/builder/target/debug/build/rustc_codegen_spirv-ffa44511fcb54869/build-script-build` (exit status: 1)
--- stdout
cargo:rerun-if-env-changed=RUSTGPU_SKIP_TOOLCHAIN_CHECK
--- stderr
error: wrong toolchain detected (found commit hash `be19eda0dc4c22c5cf5f1b48fd163acf9bd4b0a6`, expected `1a5f8bce74ee432f7cc3aa131bc3d6920e06de10`).
Make sure your `rust-toolchain.toml` file contains the following:
-------------
[toolchain]
channel = "nightly-2023-05-27"
components = ["rust-src", "rustc-dev", "llvm-tools-preview"]
-------------
So I updated channel to "nightly-2023-05-27" instead of the one suggested in the docs, but then I get:
error: failed to parse lock file at: [path]/builder/Cargo.lock
Caused by:
lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?
Changing Cargo.lock version to 3 gives:
error: failed to run custom build command for `builder v0.1.0 ([path]/builder)`
Caused by:
process didn't exit successfully: `[path]/builder/target/debug/build/builder-ab9d01841427145d/build-script-build` (exit status: 1)
--- stdout
cargo:rerun-if-env-changed=RUSTGPU_CODEGEN_ARGS
cargo:rerun-if-env-changed=RUSTGPU_RUSTFLAGS
--- stderr
error: failed to parse lock file at: [path]/shader/Cargo.lock
Caused by:
lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?
Error: BuildFailed
I tried to play with some more settings, and kept bumping in to
error: missing libm intrinsic _RNvMNtNtNtCsbtJY5FUAdnQ_4libm4math7support3bigNtB2_4u2566signed, which is math::support::big::u256::signed
error: missing libm intrinsic _RNvXs2_NtNtNtCsbtJY5FUAdnQ_4libm4math7support3bigNtB5_4u256NtNtNtCsktVOBji75Go_4core3ops5arith3Add3add, which is <math::support::big::u256 as core::ops::Add>::add
error: missing libm intrinsic _RNvXs3_NtNtNtCsbtJY5FUAdnQ_4libm4math7support3bigNtB5_4u256INtNtNtCsktVOBji75Go_4core3ops3bit3ShrmE3shr, which is <math::support::big::u256 as core::ops::Shr<u32>>::shr
error: missing libm intrinsic _RNvXs4_NtNtNtCsbtJY5FUAdnQ_4libm4math7support3bigoNtNtB7_10int_traits4HInt5widen, which is math::support::big::<impl math::support::int_traits::HInt for u128>::widen
error: missing libm intrinsic _RNvXs4_NtNtNtCsbtJY5FUAdnQ_4libm4math7support3bigoNtNtB7_10int_traits4HInt10zero_widen, which is math::support::big::<impl math::support::int_traits::HInt for u128>::zero_widen
...
Again, apologies for this mess. I honestly can't figure out what the root cause is and how to get around it.
Any pointers?
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit dem Leitfaden writing-shader-crates unter der verlinkten URL und vergleiche seine Anweisungen mit den gemeldeten Fehlern bei der rustc_codegen_spirv-Toolchain und in Cargo.lock. Als abgeschlossen gilt die Aufgabe, wenn der Leitfaden ein reproduzierbares Setup beschreibt, das die gemeldeten Fehler vermeidet, oder die erforderlichen Versionen und Einschränkungen klar dokumentiert.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust
- Bereich
- documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100