Conversation
| + set(OPENCV_DLLVERSION "") | ||
| set(OPENCV_DEBUG_POSTFIX d) | ||
| - ocv_update(OPENCV_DLLVERSION "${OPENCV_VERSION_MAJOR}${OPENCV_VERSION_MINOR}${OPENCV_VERSION_PATCH}") | ||
| + ocv_update(OPENCV_DLLVERSION "") |
There was a problem hiding this comment.
Variables that are defined using ocv_update can be modified setting them through vcpkg_configure_cmake instead of patching them in the source code
There was a problem hiding this comment.
In SOURCE/cmake/OpenCVVersion.cmake:
SET(OPENCV_VERSION_FILE "${CMAKE_CURRENT_SOURCE_DIR}/modules/core/include/opencv2/core/version.hpp")
file(STRINGS "${OPENCV_VERSION_FILE}" OPENCV_VERSION_PARTS REGEX "#define CV_VERSION_[A-Z]+[ ]+" )
string(REGEX REPLACE ".+CV_VERSION_MAJOR[ ]+([0-9]+).*" "\\1" OPENCV_VERSION_MAJOR "${OPENCV_VERSION_PARTS}")
string(REGEX REPLACE ".+CV_VERSION_MINOR[ ]+([0-9]+).*" "\\1" OPENCV_VERSION_MINOR "${OPENCV_VERSION_PARTS}")
string(REGEX REPLACE ".+CV_VERSION_REVISION[ ]+([0-9]+).*" "\\1" OPENCV_VERSION_PATCH "${OPENCV_VERSION_PARTS}")
string(REGEX REPLACE ".+CV_VERSION_STATUS[ ]+\"([^\"]*)\".*" "\\1" OPENCV_VERSION_STATUS "${OPENCV_VERSION_PARTS}")
We cannot pass OPENCV_VERSION MAJOR into vcpkg_configure_cmake because it will be overwritten here.
There was a problem hiding this comment.
Sorry I don't understand. I was telling you to pass value from the port file because it is much easier to maintain, instead of patching source code. Those variables became managed through ocv_update exactly because we were patching them (they were not supposed to be modified by users in the beginning), in order to ease our work here :)
There was a problem hiding this comment.
Pass OPENCV_DLLVERSION="" from the portfile :)
| opencl:x64-uwp=fail | ||
| opencolorio:x64-linux=ignore | ||
| opencsg:x64-uwp=fail | ||
| opencv3:arm64-windows = skip |
There was a problem hiding this comment.
They are skipped because they conflict with opencv/opencv4.
There was a problem hiding this comment.
If you want to use CI to test opencv3 you have to skip opencv4, but I am not sure that you would trigger an automatic removal in the installed folder in this way... So I fear that it's impossible to test opencv3 in CI
There was a problem hiding this comment.
If CI cannot test these features, I worry that this PR will last a long time.
There was a problem hiding this comment.
Once this PR is done, I will revert these changes.
|
@Neumann-A When I build I cannot find |
This file should not exist at all. Delete the And I don't understand why it even exists since qt5-base has the line: |
|
@Neumann-A I guess my installed/x86-windows is not clean. |
|
@cenit Nope, I found it was added in this release. |
|
It looks like we only have problems with static builds. |
I hope it works. Because when I try to pass |
|
you have to pass them with the proper quotation sintax. The opencv4 port should contain an example :) |
and proper escaping syntax if you want to pass a list of elements (7 or 9 backslashes needed for passing a list)..... all due to |
|
Since Opencv3 is updated to 3.4.10, I think this PR is no longer available. |
Update opencv3 to 3.4.8.
Related: #8641.