Le mar. 9 juil. 2019 à 13:24, hex <hex...@gmail.com> a écrit : > Now that I look at it it seems very obvious. I still have doubts, though: > > I guess I am seeing the contents of a build directory as somewhat > volatile. For most files I want that, to either clean the project or > override the files. > > But what about files I want to archive, such as a tarball or zipped > documentation: does it make sense to place them into the build directory? > The files belong to the project, though are not source controlled but > aren't install targets either. > How would CMake know that these tarballs are in a somewhat final version that you want to archive as opposed to a state where they haven't passed the most basic tests yet? I would implement this outside CMake: wherever is the information that guides the decision to archive. When that decision is made then some script would simply "exfiltrate" the tarballs and whatever else from the build/ directory before it gets cleaned. Sounds like something CI does every day.
This being said, CPack seems to have a ton of documented and undocumented (read: Stackoverflow) options, hopefully some of them do what you want. Marc
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
