Hi!
My problem is that I use OpenCV for other things besides just Card IO. If you're in my shoes, and you've updated OpenCV to 3.0 or above, you'll have to waive bye-bye to Card.IO because the old version of OpenCV packaged in your .a files conflicts when trying to use OpenCV functions, such as image functions.
It is my conclusion that Card IO is currently incompatible with projects using OpenCV 3.0 or above.
I have been and really want to continue to use Card IO for my project! However, I have not been able to figure out a way around this. Is it possible to get a version of your library with OpenCV dependency removed from your lib file? Since you've prepackaged everything in the lib file... I can't do anything to fix. Your libCardIO.a references your pre-packaged libopencv_core.a and libopencv_imgproc.a files from within. If you have OpenCV installed through Cocoa Pods, or, as I have by directly linking the OpenCV framework file, the next time using an OpenCV method EXC_BAD_ACCESS is the result. Tested over, and over, and over, and know this to be the case... because I really need CardIO in my project. HoweverI also really need OpenCV 3.0+. These days, there are modules that require OpenCV 3.0, and so any of those also automatically conflict with Card.IO too. I loved using CardIO!
Hi! My problem is that I use OpenCV for other things besides just Card IO. If you're in my shoes, and you've updated OpenCV to 3.0 or above, you'll have to waive bye-bye to Card.IO because the old version of OpenCV packaged in your .a files conflicts when trying to use OpenCV functions, such as image functions.
It is my conclusion that Card IO is currently incompatible with projects using OpenCV 3.0 or above.
I have been and really want to continue to use Card IO for my project! However, I have not been able to figure out a way around this. Is it possible to get a version of your library with OpenCV dependency removed from your lib file? Since you've prepackaged everything in the lib file... I can't do anything to fix. Your
libCardIO.areferences your pre-packagedlibopencv_core.aandlibopencv_imgproc.afiles from within. If you have OpenCV installed through Cocoa Pods, or, as I have by directly linking the OpenCV framework file, the next time using an OpenCV method EXC_BAD_ACCESS is the result. Tested over, and over, and over, and know this to be the case... because I really need CardIO in my project. HoweverI also really need OpenCV 3.0+. These days, there are modules that require OpenCV 3.0, and so any of those also automatically conflict with Card.IO too. I loved using CardIO!