mlpack / opencv namespace ambiguity? about mlpack

[rcurtin]

Inside of the mlpack namespace there is mlpack::cv namespace defined for compatibility reasons (so that mlpack3 and older code will work even though mlpack classes now live in a flat namespace). The file that defines this reverse-compatibility namespace is only included by mlpack.hpp. So, one way around this is that you can include only the headers that you need, as described in the first bullet point here. Then the cv namespace will not be defined at all.

Alternately, the StackOverflow post you found is right: to avoid ambiguity, you can avoid using namespace declarations and simply be explicit about the classes; e.g., cv::Mat instead of Mat.

Also, Visual Studio is not always the best compiler to use; sometimes it complains and has compilation problems where g++ or clang would not. So, if moving to a Linux or OS X development system is a possibility, that may also save you some headaches.

[IgorWojas]

@rcurtin Thank you. I menaged to workaround the problem somehow. There must be something wrong with my opencv install/build.

[shrit]

Closing this issue since it is resolved