You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project opened my mind a lot, it's very helpful for us to use dart:ffi on all platforms.
But after some tests I found the windows' CMakeLists.txt is seems worng when bundle OpenCV library
I am not familiar with CMake syntax but this seems not correct, it's just defined a OpenCV_DLL_NAME= macro and will bundle the whole OpenCV bin folder to the flutter windows build folder with ${_OpenCV_LIB_PATH}/${OpenCV_DLL_NAME}
After some research, I found a better way to bundle the OpenCV dll
get_target_property(OPENCV_DLL_DEBUG opencv_world IMPORTED_LOCATION_DEBUG)
get_target_property(OPENCV_DLL_RELEASE opencv_world IMPORTED_LOCATION_RELEASE)
set(OPENCV_DLL
$<$<CONFIG:Debug>:${OPENCV_DLL_DEBUG}>
$<$<CONFIG:Profile>:${OPENCV_DLL_RELEASE}>
$<$<CONFIG:Release>:${OPENCV_DLL_RELEASE}>
)
# List of absolute paths to libraries that should be bundled with the plugin
set(opencv_bundled_libraries
""
${OPENCV_DLL}
PARENT_SCOPE
)
We can use this to avoid define OpenCV dll name in the CMakeLists.txt
The text was updated successfully, but these errors were encountered:
This project opened my mind a lot, it's very helpful for us to use dart:ffi on all platforms.
But after some tests I found the windows' CMakeLists.txt is seems worng when bundle OpenCV library
I am not familiar with CMake syntax but this seems not correct, it's just defined a
OpenCV_DLL_NAME=
macro and will bundle the whole OpenCV bin folder to the flutter windows build folder with${_OpenCV_LIB_PATH}/${OpenCV_DLL_NAME}
After some research, I found a better way to bundle the OpenCV dll
We can use this to avoid define OpenCV dll name in the CMakeLists.txt
The text was updated successfully, but these errors were encountered: