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
{{ message }}
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.
Ok, an update, we probably shouldn't write our own FindXXX.cmake
Do not write find modules for packages that themselves build with CMake. Instead provide a CMake
package configuration file with the package itself. See our tutorials on CMake Packages.
But, instead just create a package config
Not exactly. I think @breznak is suggesting we provide a generic CMake module so that consumers of nupic.core can integrate it easily into their own CMake builds. 👍 from me.
Bump. Is anyone linking their 3rd party (cmake based) app to nupic.core?
Ok, an update, we probably shouldn't write our own FindXXX.cmake
Do not write find modules for packages that themselves build with CMake. Instead provide a CMake package configuration file with the package itself. See our tutorials on CMake Packages.
so nupic.core libraries can be easily detected & included by 3rd party C++ programs.
https://cmake.org/Wiki/CMake:How_To_Find_LibrariesEDIt: reference of others
https://github.com/numenta/nupic.core/blob/master/CMakeLists.txt
https://cmake.org/Wiki/CMake/Tutorials/Packaging
https://cmake.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file
The desired result is:
We can call
find_package(NupicCore)
in an external cmake repo and use the includes/libraries/binaries/flags from this project.The text was updated successfully, but these errors were encountered: