-
Notifications
You must be signed in to change notification settings - Fork 89
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
Disabling optimizations for specific packages in Cargo.toml? #83
Comments
Adding
in |
As far as optimizations are concerned I'd think the I suggest dropping the In case you want to avoid modifying Also, please, next time specify at least your linux distro. |
Hmm, to me it looks like the |
@adundovi I think this should probably be an issue on the size optimizations plugin, as Perseus itself is agnostic about how you perform optimizations. I could also create another plugin, but I think the simplest thing is just to patch the size optimizations plugin to perform that workaround. |
@arctic-hen7 thanks for the feedback. Are the perseus plugins listed somewhere? |
Yes! See the Plugins section on the website. (At the moment there's only one...) |
This prevents the infinite compiling problem described [here](framesurge/perseus#83).
Okay, the size optimizations plugin now has this patch inbuilt unless the |
Hi @arctic-hen7, thank you for the plugin and for including the workaround in the plugin by default. May I just note that I have to change the prescribed line on how to use the plugin into: plugins: Plugins::new().plugin(|| perseus_size_opt(), SizeOpts::default()) since otherwise, I cannot compile:
|
Ah! Yes, sorry, that's an issue in the docs for the plugin. You don't need a closure, just use |
Eh, yes, you're right, and it makes perfect sense. (me embarrassed) |
Hmm, does not work after |
Have you run |
No, I forgot. Afterward, it worked. Thank you. |
No problem! |
Describe the bug
I've encountered the following bug in Rust, i.e., when building a package with
perseus build
(orserve
ortest
), the "Building your app to Wasm..." step never ends (finally being killed by the OOM killer). It only happens for the--release
target of wasm32, not for x86_64 and wasm32 without--release
.A workaround for this bug is to disable optimizations for
fluent-bundle
.How do I specify
opt-level = 0
for thefluent-bundle
package inCargo.toml
so thatperseus-cli
picks it up and builds the package with the option present? I tried just putting in Cargo.toml, but it didn't work. It would be great to see in Perseus' docs how to do this...Environment:
The text was updated successfully, but these errors were encountered: