Yes, these instructions are correct for this.

Okay, thank you. I will get back to you at the end of the day with a report.
If you want me to test something on this version, please let me know, I will be happy to do so.

I had done that before ^^
Then, with
"cargo r --jobs 1"
it compiles in 46 minutes. On the same machine that compiled in 15 minutes (without --jobs 1).
(less than 2 minutes when everything was fine)

I come back to the initial question: do you have any advice to avoid this behavior?

No idea ?

Note that we've optimized a bit the size of the generated code in Slint 1.7 and it should reduce a lot the compilation time. Maybe you can give it a try and see if it helped in your case.

Unfortunately, the problem persists.

A simple automatic “cargo check” uses all the computer's resources when certain portions of code in .slint files are active.

By removing a large part of the code, step by step, I've been able to identify certain parts that have a strong influence on compilation time AND resources used (all resources).

However, I don't see anything shocking in these blocks of code.

Currently, I'm trying to split the code into several files and distribute the “data” differently to see if this will have a positive impact. But that's not the case at the moment.

Thx for the answer.

Why not the problem with external libraries?

Because i tried also with Slint alone, with a light main.rs /cargo.toml.

cargo-features = ["edition2024"]

[package]
name = "my-gui"
version = "0.1.0"
edition = "2024"
build = "build.rs" 

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
#otherext- = { path = "../otherext" }
itertools = "0.11.0"
tokio = { version = "1.29.0", features = ["full"] }
indexmap = { version = "1.9.1", features = ["serde-1"] }
image = "0.24.7"
slint = "1.6.0"

[build-dependencies]
slint-build = "1.6.0"

[patch.crates-io]
slint = { git = "https://github.com/slint-ui/slint" }
slint-build = { git = "https://github.com/slint-ui/slint" }


[profile.dev]
#incremental = false

Also tested on 2021 editions and with/without "incremental = false" Should I use this param ?.

build.rs:

fn main() { 
    slint_build::compile("ui/main.slint").unwrap();      
}

Where are those messages so that we can understand your problems in more details?

Examples:
#4670
#4082

Would you share more details about your machine? probably you're using docker for development and you're creating an image from scratch every time you're compiling your code!

I am not Docker user.
Computer: Apple MacBook Air M2 -> 8Go of memory.
I remind you that all worked fine on the same machine recently.

I don't recommend using the slint! macro

I work only with .slint files.

You'd shoot your foot with a gun if you put everything in a single file. I don't recommend using the slint! macro, and instead write several slint and rust files. Sometimes you may need to split your project into multiple crates to improve compilation time.

I meant that the majority of callbacks are in the same .slint file.