2016-03-10 13:08:36 -0600 | commented question | unresolved externals after custom build (vs14) As I said, I have a property sheet for the dependencies. I do not use #pragma in my project. I tried to add a #pragma to see what happens, nothing changed. |
2016-03-10 12:51:33 -0600 | received badge | ● Editor (source) |
2016-03-10 12:50:07 -0600 | asked a question | unresolved externals after custom build (vs14) The newest OpenCV comes prebuilt only as 64-bit. I have started with a working MSVS2010/OpenCV 3 rc1 project (32-bit). I am upgrading to VS2015/OpenCV 3.1.0 (32-bit). I successfully built the OpenCV shared libraries using CMake and the vs14 toolkit. So far, so good. Back in my project, I have added the libraries, and they are presumably found. I have even tried to ensure that they are loaded with #pragma in a respective cpp file (to no different effect): pragma comment(lib, "opencv_core310d.lib") ... I get unresolved externals in many of those respective files. For example: With my build of opencv, I can create a new project, add the apparently same configuration (done with importing the same property sheet I made for OpenCV dependencies), and e.g. construct a cv::Exception. That results in no errors. I am adding core, and imgproc among a few others. The linker reports just 39 of those unique unresolved symbols in a sizable project (duplicated for 294 total errors). If I do remove my configuration properties for OpenCV, the number of unresolved symbols jumps to 82 (for 712 errors). I'm at a loss to why this is happening - what is the problem here? |