You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an MNN_DEPEND cmake variable, however, cmake variable is not visible to parent scope. So the super-project cannot get the correct MNN library path and compile flags.
The ideal solution is that the CMakeLists.txt of MNN adds a library target (named "mnn" or something else), and this target depends on vulkan, opengl and so on. So that users can simply depend on target "mnn" without concern about all the dependencies and compile flags.
What's more, I believe MNN should export a target (on make install or cmake -P cmake_install.cmake) as all modern cmake files do.
The text was updated successfully, but these errors were encountered:
There is an
MNN_DEPEND
cmake variable, however, cmake variable is not visible to parent scope. So the super-project cannot get the correct MNN library path and compile flags.The ideal solution is that the CMakeLists.txt of MNN adds a library target (named "mnn" or something else), and this target depends on vulkan, opengl and so on. So that users can simply depend on target "mnn" without concern about all the dependencies and compile flags.
What's more, I believe MNN should export a target (on
make install
orcmake -P cmake_install.cmake
) as all modern cmake files do.The text was updated successfully, but these errors were encountered: