Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Windows/mingw installation problem

It seems that on Windows (mingw), instead of being installed into $(CMAKE_INSTALL_PREFIX)/lib libraries end up in machine+architecture dependent folder, e.g. if CMAKE_INSTALL_PREFIX is "C:/prj/INSTALL", I see:

-- Installing: C:/prj/INSTALL/i386-w64-mingw32/x86/mingw/lib/libopencv_core310.dll.a -- Installing: C:/prj/INSTALL/i386-w64-mingw32/x86/mingw/bin/libopencv_core310.dll

Additionally, Python2 module instead of being created in $(CMAKE_INSTALL_PREFIX)/lib/Python2.7/site-packages like happens on, say, OSX, ends up being installed into Python's installation folder:

-- Installing: C:/Python27/Lib/site-packages/cv2.pyd

Is there a way to make both behaviors consistently respecting CMAKE_INSTALL_PREFIX across multiple OSs?

Windows/mingw installation problem

It seems that on Windows (mingw), instead of being installed into $(CMAKE_INSTALL_PREFIX)/lib libraries end up in machine+architecture dependent folder, e.g. if CMAKE_INSTALL_PREFIX is "C:/prj/INSTALL", I see:

-- Installing: C:/prj/INSTALL/i386-w64-mingw32/x86/mingw/lib/libopencv_core310.dll.a
-- Installing: C:/prj/INSTALL/i386-w64-mingw32/x86/mingw/bin/libopencv_core310.dll

C:/prj/INSTALL/i386-w64-mingw32/x86/mingw/bin/libopencv_core310.dll

Additionally, Python2 module instead of being created in $(CMAKE_INSTALL_PREFIX)/lib/Python2.7/site-packages like happens on, say, OSX, ends up being installed into Python's installation folder:

-- Installing: C:/Python27/Lib/site-packages/cv2.pyd

C:/Python27/Lib/site-packages/cv2.pyd

Is there a way to make both behaviors consistently respecting CMAKE_INSTALL_PREFIX across multiple OSs?