fix: only generate linkage if CARGO_WORKSPACE_DIR is available #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RenderlingPaths
This makes the CARGO_WORKSPACE_DIR env var optional.
Without this env var we can't compile shaders or generate linkage.
Neither of those things should happen when cargo builds this library as a dependency, so this is fine.
Note that calling
cargo xtask compile-shaders
orcargo xtask generate-linkage
will err if CARGO_WORKSPACE_DIR is not available, but the env var is always available inside renderling's source tree. Outside the source tree the xtask program won't be available, so the situation where xtask cannot build shaders or generate linkage is unreachable.Dependencies
This also updates dependencies.
I've pinned
wgpu
to23.0
instead of trackingmain
.I've pinned
spirv-std
to a specific rev to fixglam
mismatches.Fixes #153.