-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CMake options to install the documentation, benchmarks and examples #1144
Comments
From a personal experience, I can say that depending on the installation workflow, I dont know enough about the documentation and examples to comment about that part. |
Thanks @lahwaacz for the report. I think installing documentation might be a good idea. In line with the usual linux packages, it probably should go into |
What might be interesting (comparing it to the CUDA samples) is installing the source code of the examples, so people can see how to use CMake etc. correctly (also connected to #1152, we don't seem to test out-of-source builds ATM) |
During ISC23 conference we had several discussions with Ginkgo developers about the ways Ginkgo installation/packaging can be improved, especially when preparing modules for the HPC centers. As promised at ISC23, I will state below the things we do at Huawei Munich Research Center when installing Ginkgo release 1.5 module using Easybuild. Note that we heavily use benchmarks, while documentation and examples are not so important for us.
After that we simply use I hope that this is useful for you. |
If we want to approach this, we probably want to use separate CMake install components |
CMake options to install the documentation, benchmarks and examples would be useful for packaging. I guess the benchmarks and examples shouldn't go directly into
bin/
as they don't have a common prefix, so the install paths should be configurable. For example, installing the built examples (and source code) to/usr/share/doc/ginkgo-hpc-git/examples/
would make sense.The text was updated successfully, but these errors were encountered: