-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Build Rust stuff offline #593
Conversation
cargo-c works fine, but gst-plugin-gtk4 does not See https://github.com/flathub/io.gitlab.daikhan.stable for existing manifest
I will give up on that, 2h was my personal limit I wanted to spend on it. |
|
> Make sure to override CARGO_HOME env variable to point it to /run/build/$module-name/cargo where $module-name is the flatpak module name, quickstart in this example. https://github.com/flatpak/flatpak-builder-tools/tree/de56f4702638739f930f4afa648686f12ac4d724/cargo
I'll rename ours to gst-plugin-gtk4 too - do some cleanup and merge if you don't mind Good idea. Two things that come to mind:
The cargo lock file can be created by checking out the tag locally and running cargo update |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot!
I upgraded cargo-c to the latest release.
I didn't setup x-checker-data because I don't like auto-updates, specially without tests.
We can consider later.
Co-authored-by: Sonny Piers <[email protected]>
Fixes #591
cargo-c works fine, but gst-plugin-gtk4 does not
See https://github.com/flathub/io.gitlab.daikhan.stable for existing manifest
See https://github.com/flatpak/flatpak-builder-tools/tree/master/cargo for tool to generate cargo sources