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

0.20 backports #1624

Merged
merged 7 commits into from
Dec 16, 2024
Merged

0.20 backports #1624

merged 7 commits into from
Dec 16, 2024

Conversation

sdroege
Copy link
Member

@sdroege sdroege commented Dec 16, 2024

No description provided.

bilelmoussaoui and others added 7 commits December 16, 2024 18:38
In commit c6ba79e ("generator.py: Use cargo run instead of guessing
path") the `cargo build` command on the default (hardcoded) `"gir"`
directory was replaced with a single `cargo run` for correctly finding
the right executable.

This isn't an issue given that `cargo run` also builds the tool, and
above all makes it easier / more correct to find the binary as the
primary reason for that commit, but it does make us lose the build log
as a progress indicator (thanks to `--quiet` and capturing `stderr`).
In addition, it causes the first `` => Looking in path `xxx` `` item
to take a very long time without aforementioned progres indication,
making the user wonder what is going on.

By building `gir` again with a separate `cargo build` invocation before
running, this issue is alleviated somewhat.
@sdroege sdroege merged commit 1d9ae47 into gtk-rs:0.20 Dec 16, 2024
7 checks passed
@sdroege sdroege deleted the 0.20-backports branch December 16, 2024 16:49
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.

4 participants