Repository navigation
add docs for static build on macOS(static=libtegra_hal,tbb,static=ittnotify,framework=OpenCL,z is required) #694
Description
I tried to link opencv statically & it decided to link against dylibs, anyway. to get the errors I deleted the dylibs from my system & figured out by the missing symbols whats actually required which are these libs/framekworks static=libtegra_hal,tbb,static=ittnotify,framework=OpenCL,z
export OPENCV_LINK_LIBS=+static=opencv_core,static=opencv_imgproc,static=opencv_calib3d,static=libtegra_hal,tbb,static=ittnotify,framework=OpenCL,z
Activity
twistedfall commentedon Sep 22, 2025
These kind of things are extremely system-dependent (OS, system capabilities like CUDA, how OpenCV was installed, what features was OpenCV built with, what features does your crate use), so they have little value as a general advice. Usually they are resolved automatically when you use an OpenCV detection tool like
cmake,pkg-configorvcpkg, but when you need to set up the detection manually via environment vars you'll need to go through the process of finding out what your situation exactly needs. With static linking the order of the link libs also matters, leaf libs go first, root libs go last.frederik-uni commentedon Sep 22, 2025
@twistedfall im so sorry I didn’t mean windows, but macOS. A hint for the prebuilt binaries would’ve been nice. Maybe as a hint what features require which libs
[-]add docs for static build on windows(static=libtegra_hal,tbb,static=ittnotify,framework=OpenCL,z is required)[/-][+]add docs for static build on macOS(static=libtegra_hal,tbb,static=ittnotify,framework=OpenCL,z is required)[/+]