'make install' builds 'myprog', then it disappears, then CMake reports an error that it cannot find it ("file INSTALL cannot find "path_to_build_directory/bin/myprog"").
Seems like a bug/oversight. Possibly CMake is trying to move the file to where it already exists, destroying it in the process.
And since someone will be horrified at what I'm doing with paths, the reason is that I've got subprojects that generate hundreds of libraries and multiple executables, and I'd like to avoid both of the following:
- Forcing developers to run 'make install' instead of 'make' before they can run
- Setting up massive PATH and LD_LIBRARY_PATH variables so that everything can be found when it's scattered all over the build tree
I suppose my current setup will work fine as long as nobody uses 'make install', but I was hoping to leverage that to help with release packaging.