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
Somewhere, probably at the top-level, an Examples directory could be created.
In there a sub directory could contain a small main function along with a CMakeLists.txt file. In that CMakeLists.txt file we should relay on this installation of mx and use find_package( mx ). During continuous integration runs, we should add a step where we make install then cd to the example and build it. If mx installation isn't working, that build should fail. If mx installation is working, that build should succeed.
The text was updated successfully, but these errors were encountered:
On April 4, 2020 at 8:01:56 AM, p-groarke ***@***.***) wrote:
Are you ok with ExternalProject instead of find_package? It tests the same thing, but it makes it more robust on Windows, as windows doesn't have a standardized system library directory.
Yes, basically whatever you are using should be tested so we don’t break it!
Somewhere, probably at the top-level, an Examples directory could be created.
In there a sub directory could contain a small main function along with a CMakeLists.txt file. In that CMakeLists.txt file we should relay on this installation of mx and use
find_package( mx )
. During continuous integration runs, we should add a step where wemake install
then cd to the example and build it. If mx installation isn't working, that build should fail. If mx installation is working, that build should succeed.The text was updated successfully, but these errors were encountered: