Hi,
My CMake file contains the install comands like this
install(TARGETS MyExe RUNTIME DESTINATION .)
When I use the standard NSIS template, the installer is created with
MyExe. But our project needs a custom NSIS template so I have written
one, and it is generating an installer *without*
2014-03-27 7:08 GMT+01:00 Lloyd lloydkl.t...@gmail.com:
Hi,
My CMake file contains the install comands like this
install(TARGETS MyExe RUNTIME DESTINATION .)
When I use the standard NSIS template, the installer is created with
MyExe. But our project needs a custom NSIS template so I have
I am no NSIS expert so I can't imagine why 'File /r ${INST_DIR}\*.*'
could possibly do ???
About the file command the NSIS documentation says this:
Adds file(s) to be extracted to the current output path ($OUTDIR).
If the /r switch is used, files and directories are added
Solved the problem.
Further verification revealed that, when I build PACKAGE, it generates a
install_manifest.txt file in my build directory. It contains absolute
paths to copy of install files I mentioned using install targets command.
This temporary directory and its files are also created when
