Add fs mount for backend build step to allow for building frontend an… #10
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.
…d other parts of code
Before this, only things in the
<plugin root>/backend/
could be accessed by the custom backend build step. This opens that up to anything in<plugin root>/
while maintaining the original mounts for backwards compatibility. I assume the original intent of restricting it to only the backend folder was to limit it's usage to backend compilation, but I don't really see the merit to that when it could also be used for other compile-time tasks like code generation and building frontend dependencies.This enables the latest version of Fantastic (and future USDPL v0.11+ plugins) to generate it's frontend WebAssembly at compile time. For reference: docker build script for Fantastic v0.5.0.
(This is not pressure, just information: lack of this functionality is blocking Fantastic v0.5.0 from being released onto the Decky store)