mozzis's profile - activity

The warnings are due to a problem with Visual C++ compilation of template members of an exported class. I have no idea whether this is due to a violation of the C++ ISO standard or whether it is in one of those "gray areas." Although best practice is certainly not to have tons of warnings show up in your build output, in this case you can work around this by turning off "OPENCV_WARNINGS_ARE_ERRORS" in the OPENCV node in the CMAKE GUI. The warnings will still show up, but your build will complete anyway (and the result will probably run.)

Thanks, I thought of that. However, our product consists of multiple .Net dlls. Some are in C#. There is really no way to use static native .libs in this situation. In addition, it would greatly inflate both the size of the dlls, and the memory footprint of the runtime image.

Add #include "functions.h" in file with main()

We provide a set of libraries to develop specialized applications for optics. I am using OpenCV for some image processing functions.

The way OpenCV is built, dll names are the same for both 32-bit and 64-bit versions. This makes is necessary to either replicate the dlls to every application folder (making the use of dlls pointless) or switching the system PATH in to select the right "bitness" of dlls for each application. It would be much better if the 64-bit versions had "64" appended to the name (and for consistency, "32" in the name of the 32-bit versions.)

I have had a go at rebuilding the dlls from source, but figuring out how to rename the outputs seems hopeless. All of the dependencies would have to change as well, and though I have encountered CMake-based builds in other projects, this one seems much more complicated than I would have expected. Can someone suggest how to accomplish what I need to do here?