Hi. I try to make own native opencv package with CoApp PowerShell tools (ver. 1.23.521.0) and get next problem. Standart practice as recommended by creators is include OpenCV modules headers as follow: #include "opencv2/core/types_c.h"
include "opencv2/imgproc/types_c.h". But folder "core", "imgproc" do not have any files and then i write include: { "${ROOTDIR}modules\core\include*_", "${ROOT_DIR}modules\imgproc\include*_"}; after building a package they located in package as one common directory Include without separation to "opencv2\core\" and "Include\opencv2\img_proc\". I think that is wrong decision not to add path folders which have no files. Some problem I have with boost, which recommend use includes as #include "boost/scoped_ptr.hpp" and folder boost have no files. I know a hint to use dummy headers in such empty folders but I think thats not a good way. Best regards, Stanislav.
Hi. I try to make own native opencv package with CoApp PowerShell tools (ver. 1.23.521.0) and get next problem. Standart practice as recommended by creators is include OpenCV modules headers as follow: #include "opencv2/core/types_c.h"
include "opencv2/imgproc/types_c.h". But folder "core", "imgproc" do not have any files and then i write include: { "${ROOTDIR}modules\core\include*_", "${ROOT_DIR}modules\imgproc\include*_"}; after building a package they located in package as one common directory Include without separation to "opencv2\core\" and "Include\opencv2\img_proc\". I think that is wrong decision not to add path folders which have no files. Some problem I have with boost, which recommend use includes as #include "boost/scoped_ptr.hpp" and folder boost have no files. I know a hint to use dummy headers in such empty folders but I think thats not a good way. Best regards, Stanislav.