Skip to content

Conversation

@cenit
Copy link
Contributor

@cenit cenit commented Jul 9, 2025

Fixes: #46281

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

@cenit
Copy link
Contributor Author

cenit commented Jul 11, 2025

sorry i have been away busy for some time and i cannot understand the new ci testing. Any hint or help on what to do? (feature testing, etc)

@autoantwort
Copy link
Contributor

sorry i have been away busy for some time and i cannot understand the new ci testing. Any hint or help on what to do? (feature testing, etc)

What do you not understand?
The feature test "installs" each feature separately, which should work. It also test the core feature and what happens when you select all features at the same time. You can run the command locally vcpkg x-test-features --failure-logs=logs --ci-feature-baseline=scripts/ci.feature.baseline.txt opencv4, which is an automated way of running vcpkg install opencv4[core], vcpkg install opencv4[core, feature1], vcpkg install opencv4[core, feature2], ... .
In the scripts/ci.feature.baseline.txt you can specify which features are expected to fail (should be none), or which combinations can not be tested together (should be theoretically be none, since they should be additive).

@cenit
Copy link
Contributor Author

cenit commented Jul 18, 2025

ok this should be enough. I will find time to fix the pr asap, i assume the failures are not related to the update itself but something already in the baseline.

@autoantwort
Copy link
Contributor

You can use the feature baseline from #46476 to get a green ci

@cenit
Copy link
Contributor Author

cenit commented Jul 19, 2025

You can use the feature baseline from #46476 to get a green ci

thanks, just merged with your PR. Let's wait for the results!

@cgilles
Copy link

cgilles commented Aug 17, 2025

any progress here to update the OpenCV port to 4.12.0?

@lwqwag
Copy link

lwqwag commented Sep 28, 2025

any update?

@cenit
Copy link
Contributor Author

cenit commented Sep 29, 2025

no sorry i am very busy lately, unable to carry on the work.

@mkreddy477
Copy link

Is it possible to prioritize this or give some tentative date by when we can expect this to be available?
I am requesting this information as there is a CVE in the earlier versions of OpenCV: https://nvd.nist.gov/vuln/detail/CVE-2025-53644

@patrikhuber
Copy link
Contributor

I would also like to upgrade to OpenCV 4.12, because it's the first version that supports a custom log function callback.

This PR is not trivial.... I've also opened an issue in the OpenCV repo to hopefully get some attention from the OpenCV maintainers, and make their build more compatible with vcpkg out of the box - it might help if more people post/upvote it: opencv/opencv#28042

@dg0yt dg0yt mentioned this pull request Dec 6, 2025
@BillyONeal
Copy link
Member

Closing this in favor of @dg0yt 's PR. Thanks for the update and sorry it didn't work out!

@BillyONeal BillyONeal closed this Dec 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[opencv4] update to 4.12

7 participants