You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently started using Slint, but I noticed that compilation in debug and especially release mode takes up a very long time, even if only one component is being used.
Is there any way to speed up the compilation process like caching builds like Cargo does?
Or are there any recommendations to consider when structuring a Slint project? Putting everything in one file and using the Slint macro everywhere is clearly no option at as a growing codebase with everything in one file gets really messy after the third component.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
I recently started using Slint, but I noticed that compilation in debug and especially release mode takes up a very long time, even if only one component is being used.
Is there any way to speed up the compilation process like caching builds like Cargo does?
Or are there any recommendations to consider when structuring a Slint project? Putting everything in one file and using the Slint macro everywhere is clearly no option at as a growing codebase with everything in one file gets really messy after the third component.
My
build.rs
:My
src/main.rs
:Beta Was this translation helpful? Give feedback.
All reactions