Bug 930638 – media-libs/opencv-4.8.1-r1 provides no option for building static libs

• Status: UNCONFIRMED
• Product: Gentoo Linux

[Description siefkenj 2024-04-24 18:26:47 UTC]

Building a project like Gyroflow https://github.com/gyroflow/gyroflow requires linking against static libs `libopencv_core.a`, etc. but there is no option (that I can find) in the ebuild to allow building of these static libs.

Reproducible: Always

[Comment 1 Mike Gilbert 2024-04-24 19:30:59 UTC]

Why can't Gyroflow use the shared libraries?

[Comment 2 siefkenj 2024-04-24 19:45:04 UTC]

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.

[Comment 3 David Seifert 2024-04-24 21:04:57 UTC]

(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.

[Comment 4 siefkenj 2024-04-24 21:56:17 UTC]

There is a similar option `USE=static-libs` provided by `libpng`.

[Comment 5 Paul Zander 2024-04-26 17:03:08 UTC]

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.