Summary: | media-libs/opencv-4.8.1-r1 provides no option for building static libs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | siefkenj |
Component: | Current packages | Assignee: | Paul Zander <negril.nx+gentoo> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | floppym, proxy-maint, siefkenj, soap |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
siefkenj
2024-04-24 18:26:47 UTC
Why can't Gyroflow use the shared libraries? It is a Rust application that is statically linked. I do not understand the build system well enough to know if that can be changed. (In reply to siefkenj from comment #2) > It is a Rust application that is statically linked. I do not understand the > build system well enough to know if that can be changed. Then I find asking for a static library in a dependency tenuous. There is a similar option `USE=static-libs` provided by `libpng`. libpng supports static libs, opencv does not https://github.com/opencv/opencv/issues/21447. You can pass MYCMAKEARGBS="-DBUILD_SHARED_LIBS=yes" to build static libs, but that will be totally broken and won't get support. I also don't see any viable reason to do that in the ebuild given the scope of breakage. Try to find out how to fix the linkage. You might get help on irc in #gentoo-rust or #gentoo-dev-help. |