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

WASM fix #57

Merged
merged 3 commits into from
Jun 12, 2024
Merged

WASM fix #57

merged 3 commits into from
Jun 12, 2024

Conversation

aevyrie
Copy link
Owner

@aevyrie aevyrie commented Jun 12, 2024

Some edits on top of #56

Fixes #54

justim and others added 2 commits April 5, 2024 14:58
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 merged commit 8989c30 into main Jun 12, 2024
6 checks passed
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