-
Notifications
You must be signed in to change notification settings - Fork 132
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
libimagequant_sys: missing shared library #109
Comments
4.x only provides a static library but graphviz needs a shared gd library PR 57395 and ImageOptim/libimagequant#109
+ libimagequant-4.2.0 [ImageOptim/libimagequant#109], py-yubikey-manager-5.1.1, ssh-audit-2.9.0, texlab-5.5.1.
Rust can build a shared library, but the default cd imagequant-sys/
cargo install cargo-c
cargo cinstall # set appropriately --prefix=/usr/bin --destdir=/ |
It seems that the suggested, rust-lang/cargo#5045 (comment) fix to use Like you pointed on the referenced thread, we are interested in building the share object, not to directly install it as with |
Alternatively, modify [lib]
crate-type = ["staticlib", "lib"] to [lib]
crate-type = ["staticlib", "lib", "cdylib"] to get the default Cargo behavior and a dynamic library in |
@kornelski Sorry for nor reporting back earlier, I would say this can be closed now.
This way it now installs the following files:
Unless @0-wiz-0 thinks differently, this is solved. |
Yes, sorry for not giving feedback earlier - |
The rust version is supposed to replace the C version.
Right now, the rust version only provides a static library.
However, this leads to gd's library only existing as a static library and graphviz having problems, because it wants to build a shared object that's loaded at runtime, for which it would need a shared library.
I have no idea how to do this from rust, but librsvg does provide a shared library, and at least big parts of it are in rust (perhaps there's a C wrapper for the shared object, I haven't looked).
Please provide a shared object for libimagequant. Thanks.
The text was updated successfully, but these errors were encountered: