Build error: "Could not detect OpenCV version" with OpenCV 4.13.0 on Windows 11

[DM10cn]

Environment

• Operating system: Windows 11 Pro 25H2 (Build 26200.7840)
• OpenCV Version: 4.13.0 (Official binary distribution)
• Rust version: rustc 1.93.1 (01f6ddf75 2026-02-11)
• LLVM/Clang version: 22.1.0

Description of the issue

I am encountering a build failure with the opencv crate (v0.92.3). Despite manually configuring all necessary environment variables, the build script fails with:
Could not detect OpenCV version from include_paths.

I have confirmed that:

1. opencv_version command works in PowerShell (returns 4.13.0).
2. The path C:\opencv\build\include\opencv2\core\version.hpp is present and accessible.
3. Environment variables are set in both System Env and .cargo/config.toml.

Current Configuration (.cargo/config.toml)

[env]
OPENCV_VERSION = "4.13.0"
OPENCV_INCLUDE_PATHS = "C:\\opencv\\build\\include"
OPENCV_LINK_PATHS = "C:\\opencv\\build\\x64\\vc16\\lib"
OPENCV_LINK_LIBS = "opencv_world4130"
LIBCLANG_PATH = "C:\\APP\\LLVM\\bin"

build_log.txt

Additional Context
It seems the build script's regex/probing logic might be incompatible with the header format in OpenCV 4.13.0 on Windows, or it's failing to prioritize the manually provided OPENCV_VERSION variable.

[twistedfall]

Check item 4 in the troubleshooting guide, that should be the cause in this case

[DM10cn]

On Windows, you're getting the (exit code: 0xc0000135, STATUS_DLL_NOT_FOUND) error when running the compiled binary.

Thanks for the pointer! However, I think there might be a misunderstanding. I haven't reached the execution stage yet; the error occurs during compile time (specifically during cargo build).

My build fails with:
Could not detect OpenCV version from include_paths

I have already verified:

• System PATH: Both C:\opencv\build\x64\vc16\bin and C:\APP\LLVM\bin are added.
• Functionality: The opencv_version command works in PowerShell and returns 4.13.0.
• Manual Config: I've set OPENCV_VERSION = "4.13.0" in .cargo/config.toml, but the script seems to ignore it.

Is it possible the build script's discovery logic has a regex compatibility issue with OpenCV 4.13.0 headers?

[twistedfall]

I don't seem to be able to find this error message in the attached build log, are you sure you attached the right one? In your case it can't run the build script, so setting up the PATH to clang.dll should help.

[DM10cn]

Thanks for the suggestion! It's late night here and I'm away from my PC. I will re-verify my PATH for clang.dll and provide an update tomorrow morning. 🌙

[DM10cn]

Hi @twistedfall,

I have performed a deep clean by manually deleting the target directory and ensuring that cargo is performing a full rebuild (no "fresh" crates in the logs, as verified by Updating crates.io index).

Despite having the environment variables correctly set (as shown in the screenshot below), the binding generator still produces incomplete bindings, resulting in 110+ "method not found" errors in core.rs.

1. Environment Variables Verification

I have confirmed the paths and underscored names. OPENCV_INCLUDE_PATHS points directly to the opencv2 folder's parent.

---

2. Full Clean Build Log (build_log3.txt)

Since the verbose log is quite large, I have attached it as a file below. It contains the full trace of the binding generation process from a completely clean state.

build_log3.txt

---

3. Summary of Symptoms

Basic types like Vector, RotatedRect, and Mat seem to be missing their generated methods. Please let me know if there's any silent failure during the header parsing phase. Thanks!

[twistedfall]

Can you check the 0.98.2 version of the crate, it fixed the incompatibility with clang-22?