Closed AaronErhardt closed 1 year ago
I would also suggest documenting how cargo doc should be ran in the gir book if possible
So sadly it will require to add a --feature
argument when running cargo doc
. Not much we can do about it... Really annoyed that cargo
still doesn't allow to have doc
profile for that.
So sadly it will require to add a
--feature
argument when runningcargo doc
. Not much we can do about it... Really annoyed thatcargo
still doesn't allow to havedoc
profile for that.
why a --feature is needed? i thought everything would be handled by the RUSTFLAGS?
Sorry, you're right. Wrote too quickly. RUSTFLAGS
is what I meant.
And generator.py
would set that accordingly before calling cargo doc
.
Speaking of generator.py
, I haven't changed anything on this file so far. As far as I understand it doesn't run cargo doc
but expects the user to do so after following all required steps. Should I change something about that?
Everything else should be in place by now, I've pushed an update for the book earlier today.
Oh right. But we set RUSTFLAGS
for that already anyway so adding just one more thing is not a problem. Currently we have to set RUSTFLAGS=-Z unstable-options
at least.
Is there still anything missing in this PR?
@AaronErhardt Once merged, will you create PRs for gtk-rs-core and gtk4-rs at least to update accordingly?
Sure
Great, then let's get this in :) I can take care of gstreamer-rs once the others are in.
Fixes #1454
I think this should be all from the gir side. I've tested this branch on gtk4-rs and everything looked and worked great so far.
Let me know if I should submit PRs for various gtk-rs crates once this is merged.