-
Notifications
You must be signed in to change notification settings - Fork 17
Linking fails against bevy when using dynamic linking #84
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
Comments
Looks like the issue is that bevy_vello unconditionally pulls in image/jpeg via vello_svg. Enabling bevy/jpeg seems to cause the same issue. Arguably this isn't a bevy_vello issue at its core, but maybe it would be possible to add a feature flag for JPEG support? |
Bevy already has a corresponding issue: bevyengine/bevy#14117. |
Hm, interesting find. I'll keep an eye on the bevy issue, because whether or not we fix it I think depends on bevy fixing it first. |
zune-image has fixed it in 0.5.x (etemesi254/zune-image#187), but there seems to be ~no movement in the issue towards backporting it. Personally I was able to get around it with acceptable performance by switching to static linking with Mold. |
I don't think this issue tracks anything useful on our side. We can't fix this until Bevy updates to the latest version of Zune, and we won't need to do anything to fix it when they do. Feel free to re-open if you disagree. |
I guess I'd mostly consider it to be a documentation issue. "This is why it's currently broken, it's not on us but here's how you can work around it." |
I'll defer to @simbleau here |
The following Cargo.toml (Cargo.lock):
fails to compile with:
Removing the bevy/dynamic_linking feature makes it build fine (Cargo.lock):
The text was updated successfully, but these errors were encountered: