-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
support for building with MT_StaticRelease
in MSVC
?
#481
Comments
Hmm, the crate doesn't set either of those and dynamic vs static linking depends on how OpenCV was built. Can you post your output of |
|
I don't see any error in this build log, does that mean it built successfully? |
exactly, the program builds fine, the issue happens when i actually run it, the error happens during runtime. |
@twistedfall this is an excerpt from: https://github.com/opencv/opencv/blob/4.8.0/CMakeLists.txt
It seems that, this option is set by default. Does this crate somehow changes this default behaviour? |
When I'm looking at the library configuration:
That looks like OpenCV was installed from chocolatey or the official installer. But from your report it looks like you've made a static built OpenCV yourself. Is it installed into the same path? |
Yes, I used chocolatey, to install OpenCV, set those 3 env variables, and that's it. After these steps, the code compiles, but I instead get this error. To give more context I am using another lib, (
It seems that opencv is not being built using this cmake option. In the |
The crate actually uses |
@twistedfall |
Can you please follow the troubleshooting item 4 here: https://github.com/twistedfall/opencv-rust/blob/master/README.md#troubleshooting ? |
It's great to hear that @CeNiEi! Can you please also test the build on the current |
This is now actually released as part of 0.84.5, so no need to test |
@twistedfall Thanks, for all the help, I have used this features on the |
I am getting the following linking error, while trying to integrate within my app:
It seems that this crate sets the
MD_DynamicRelease
flag while building for msvc. Is it possible to instead setMT_StaticRelease
, using a feature flag or something?The text was updated successfully, but these errors were encountered: