It appears to be so -- the install directives execute in incident order, at least from within a single CMakeLists.txt file.
The solution ended up being INSTALL(CODE "execute_process(COMMAND ...)"). Feels like a bit of a hack, but the install works on two different platforms -- I'm satisfied for now. Thanks again for the help! CR On Mon, Jul 10, 2017 at 6:25 PM, Michael Ellery <mellery...@gmail.com> wrote: > > > On Jul 10, 2017, at 11:19 AM, Christopher E Robison < > cerobi...@utexas.edu> wrote: > > > Can I specify somehow that this install command must be executed after > the INSTALL(DIRECTORY ...) command has completed? > > I *believe* the install directives are executed in the order they are > encountered in the processing of CMakeLists files, so putting the custom > step as the last item in your top level CMake file might do the trick. > > >
-- 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: http://public.kitware.com/mailman/listinfo/cmake
