(2) This mailing list entry is similar but also seems to be Linux only.(1) There is a Linux specific solution, using an INSTALL_COMMAND that involves autotools or make install may work but I need to support Windows which won’t have these tools in our case.ExternalProject_Add alone can’t handle the install process automatically and I need to use something in addition to it.The main project does run the external project’s install step, but it can’t find the directory containing the built binary file and I need to specify that somewhere.ExternalProject_Add is not set up to cause the main project to run the External Project’s install step.Here’s my theories as to what’s happening: The executable file does not appear to be copied to anywhere the main project would know about, either. Unfortunately the executable file from the External Project is not getting packaged in by CPack. The ExternalProject_Add command in my main project’s script looks like this: # main project's ExternalProject_Add command # Literally 'SomeDestination', I don't know what directory to put here.

In a sample project I have created an External Project that also uses CMake as its install system, it has an install command that looks like this: # External project's install command The default install step builds the install target of the external project The external project’s install rules are not part of the main project’s install rules, so if anything from the external project should be installed as part of the main build, these need to be specified in the main build as additional install() commands. The documentation for ExternalProject mentions this: I am looking to have CMake clone and build a git repository as an ExternalProject, then package in the resulting binary files with the main project.

Cmake install porefic