I was debugging a hard-to-track issue in a build of rego where random files would be missing from the install tree after a call to cmake --install. Ultimately, it turned out to be the following command in the CMakeLists.txt of trieste.
I think it's not a good idea to do that, in particular in situations where the user install into /usr/local. But even for other destinations, trieste should not assume to be the only library in that tree. Is there a particular reason to do that, that I'm missing?
I was debugging a hard-to-track issue in a build of rego where random files would be missing from the install tree after a call to
cmake --install. Ultimately, it turned out to be the following command in theCMakeLists.txtof trieste.https://github.com/microsoft/Trieste/blob/dd7c8e031f630e47bb895ff77cf0eee7d49dace0/CMakeLists.txt#L110
I think it's not a good idea to do that, in particular in situations where the user install into
/usr/local. But even for other destinations, trieste should not assume to be the only library in that tree. Is there a particular reason to do that, that I'm missing?