Ah, yes. If only we could add dependencies and pre-/post-build
commands to built-in CMake targets...
http://www.cmake.org/Bug/view.php?id=8438
Absent that, the best I can think of is to just write a custom command
that renames ${CMAKE_BINARY_DIR}/your_package.extension. (I don't know
of a way to q
CPack allows me to configure the basename of the package, but I would like
to be able to change the extension used. I dug around the CPack sources and
it looks like the file extension is baked into the 'virtual const char*
GetOutputExtension() { return ".sh"; }' function. It doesn't look like I
c
