Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add wasm32 workaround for missing pipelined_rendering #56

Conversation

justim
Copy link
Contributor

@justim justim commented Apr 5, 2024

The pipelined_rendering export is no longer available in Bevy since version 0.12 in wasm32 builds; it can no longer be used to select the right subapp.

Add a dummy version of the AppLabel that targets the pipelined_rendering subapp. Using a dummy app label allows to keep the same code to get the right subapp to apply the framepace resources and systems.

Fixes #54.

The `pipelined_rendering` export is no longer available in Bevy since
version 0.12 in wasm32 builds; it can no longer be used to select the
right subapp.

Add a dummy version of the `AppLabel` that targets the
`pipelined_rendering` subapp. Using a dummy app label allows to keep the
same code to get the right subapp to apply the framepace resources and
systems.
@aevyrie aevyrie mentioned this pull request Jun 12, 2024
@aevyrie
Copy link
Owner

aevyrie commented Jun 12, 2024

Unable to push to this branch, so created a branch on top of this in #57

@aevyrie aevyrie closed this Jun 12, 2024
@justim
Copy link
Contributor Author

justim commented Jun 12, 2024

Thanks! 🚀

@justim justim deleted the wasm32-rendered-pipeline-workaround branch June 12, 2024 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to build for wasm target on bevy 0.13 that does not export pipelined_rendering module
2 participants