How to deal with packages cointaining rust parts?
by Julian Sikorski
Hello,
I looked into updating libopenraw to 0.3.5 yesterday, in order to
possibly enable packaging miniaturo [1], a drop-in replacement for the
unmaintained raw-thumbnailer [2].
During the build process, libopenraw tries do download mp4parse and
mp4parse_capi, which works if --enable-network is passed to mock. For a
proper update I assume these dependencies would need to be packaged
first. mp4_parse even used to have a fedora package at some point in the
past [3].
The question is: what would the proper way of packaging the updated
libopenraw? How to tell it to use the system versions of the libs? The
guidelines appear to be focused on pure rust packages. And, even more
importantly: would miniaturo be even allowed to be packaged? There
appears to be no package at crates.io. Thanks for the input.
Best regards,
Julian
[1] https://github.com/dbrgn/miniaturo
[2]
https://gitlab.freedesktop.org/libopenraw/libopenraw/-/issues/14#note_189...
[3] https://src.fedoraproject.org/rpms/rust-mp4parse
11 months, 4 weeks
Can the native rust-* packages be used for cross-compilation? (Use of undeclared crate or module `winapi`)
by Sandro Mani
Hi
I'm trying to update mingw-librsvg2 to version 2.56.0 [1], and am stuck
at the following issue:
error[E0433]: failed to resolve: use of undeclared crate or module `winapi`
--> /usr/share/cargo/registry/gio-sys-0.17.4/src/manual.rs:13:63
|
13 | pub const G_SOCKET_FAMILY_INVALID: super::GSocketFamily = winapi::shared::ws2def::AF_UNSPEC;
| ^^^^^^ use of undeclared crate or module `winapi`
I've build rust-winapi and manually added the BR rust-winapi-devel to mingw-librsvg2.spec, but this did not help.
I suspect that here gio-sys is a "native" build which cannot be used for cross-compiling to Windows? Do I have to build a "mingw-rust-gio-sys"?
I'm not really familiar with rust so any pointers are appreciated.
Thanks
Sandro
[1] https://copr.fedorainfracloud.org/coprs/smani/mingw-librsvg2/
1 year
