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
Especially the non-developer (i.e. end-user) type users have difficulties with correctly install all required packages, in the correct order and version numebrs. In addition to basis_find_package it would be great to have basis_install_package. :)
The text was updated successfully, but these errors were encountered:
What you are looking for should be related to #514 and #274. Personally I prefer the super-build approach because during CMake configuration there shouldn't be any build or installation steps taking place. While this feature is not readily available in BASIS yet, you could write a single CMakeLists.txt for the superbuild of all dependencies + your software.
See the documentation for two variants of the super-build approach, one that firstly installs BASIS via bootstrapping at configure time and other dependencies using a super-build, and the second where all dependencies incl. BASIS are part of the super-build. For the latter there is an example CMakeLists.txt I have written for another project which uses BASIS as well. Note that this CMakeLists.txt can be located anywhere but is not the top-level or any other CMakeLists.txt of your actual project with the dependencies. In the DRAMMS project, I have put it in a folder named build.
Especially the non-developer (i.e. end-user) type users have difficulties with correctly install all required packages, in the correct order and version numebrs. In addition to basis_find_package it would be great to have basis_install_package. :)
The text was updated successfully, but these errors were encountered: