Rust-GPU / Rust-GPU/rust-gpu.github.io

Guide doesn't seem to work

Ouverte
#90 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Langage dominant
MDX
Étoiles
16
Forks
8
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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?

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par le guide writing-shader-crates à l’URL indiquée et comparez ses instructions avec les erreurs signalées concernant la toolchain rustc_codegen_spirv et Cargo.lock. Le travail est terminé lorsque le guide fournit une configuration reproductible qui évite les erreurs signalées ou documente clairement les versions et limitations requises.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
rust
Domaine
documentation
Type d'issue
Documentation
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.