spirv-std incompatible with shipped glam version

[MasterOktagon]

I have added the spirv-builder crate to my project, like described in the book. Then I created a workspace subcrate and added the spriv-std as a dependency. Due to limitations I need to work with the 2024 edition of rust, so I chose to use the 0.10.0-alpha.1 version of both. When compiling the minimal shader example from the examples folder I got following errors from the Spirv builder (from multiple source locations):

warning: vulkanotest2@0.1.0: error[E0432]: unresolved import `glam::UVec2`
warning: vulkanotest2@0.1.0:   --> ~/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/spirv-std-0.10.0-alpha.1/src/arch.rs:11:5
warning: vulkanotest2@0.1.0:    |
warning: vulkanotest2@0.1.0: 11 | use glam::UVec2;
warning: vulkanotest2@0.1.0:    |     ^^^^^^^^^^^ no `UVec2` in the root
warning: vulkanotest2@0.1.0:    |
warning: vulkanotest2@0.1.0: help: a similar name exists in the module
warning: vulkanotest2@0.1.0:    |
warning: vulkanotest2@0.1.0: 11 - use glam::UVec2;
warning: vulkanotest2@0.1.0: 11 + use glam::Vec2;
warning: vulkanotest2@0.1.0:    |
warning: vulkanotest2@0.1.0: 

my shader Cargo.toml has following dependencies:

[dependencies]
bytemuck = { version = "1.25.0", features = ["derive"] }
spirv-std = { version = "0.10.0-alpha.1", features = ["bytemuck"] }

Is this a known error from the alpha version or just me missing something?

[SiebenCorgie]

Could you checkout the glam version that is included by spirv-std (i.e cargo tree)?

I found that for some reason sometimes glam 0.33 is chosen, which produces the same error for me. Now the strange part, even if you pin the glam version in your Cargo.toml to 0.32, it continues to use 0.33. Deleting target/ and Cargo.lock doesn't work as well (they regenerate with glam-0.33 :/ )

For now you could try the template. If that compiles (standalone) you could copy over the content of you shader and effectively use the working Cargo.lock

I suspect the underlying issue is glam-0.33 breaking compatibility. spirv-std uses version = ">=0.30.8", so it'll happily use 0.33.

[paul-fornage]

I've been investigating the same thing.

This repo has a Cargo.lock that currently (and for 0.10.0-alpha) stops the issue, locking glam at 0.31.0? from memory? (<0.33)

• Downstream crates do not inherit the Cargo.lock though, so while the example might build fine cloning locally, it won't work in real projects. This could explain why it went undetected.
• glam 0.33.0 feature gated the structs in those errors, and it released 5 days ago, so spirv-std breaks when compiling.
• I was able to fix it by pinning the glam version to <0.33
• The Cargo.toml in this workspace only uses >=0.30.8, which is satisfied by 0.33, and reading the cargo version resolution docs, I would expect it to pick 0.33.
  • They also recommend against unbounded minimum versions: "Avoid overly broad version requirements. For example, >=2.0.0 can pull in any SemVer-incompatible version, like version 5.0.0, which can result in broken builds in the future." src

[paul-fornage]

For anyone encountering this now, I did cargo update -p glam@0.33.0 --precise 0.32.1, which moves the glam at 0.33.0 from the current lock file to 0.32.1

You can also check where it's coming from, in my case (with Khal) it was actually used twice, complicating things.
cargo tree -i glam If that says 'more than one version', You can use cargo tree | grep "glam" -C 3 --group-separator=...

Although right now the only breaking version is 0.33.0, so you can pretty safely just move all glam at 0.33.0 down to 0.32.1 with that first command.

Spent a long time digging into this, not sure why lol, but I'll help however I can.

[MasterOktagon]

It looks like it compiles when I add:

glam = { version = "0.33.0", default-features=false, features=["u32", "i32", "f64"] }

probably because of the feature gates.

Still have to fix the issues in my Rendering pipeline before I can check for sure though