I know it's 2 months later now, but this has been bugging me hanging around my inbox waiting for me to get back to it... :-)<br><br>This *does* work for me on a Windows machine using CMake 2.4.5 and NSIS v2.14.<br><br>
Here are the exact steps I took, and my results, based on a CMake source tree updated today and using a pre-installed binary of CMake 2.4.5 to drive the build:<br>-1- Copied the "CMake/Tests/Tutorial/Step5" directory to a new folder called "Step6"
<br>-2- Added a copy of "CMake/Modules/NSIS.template.in" to "Step6"<br>-3- Modified my <a href="http://NSIS.template.in">NSIS.template.in</a> to have some extra comments at the top of it<br>-4- Modified the Step6/CMakeLists.txt file by adding the following lines at the bottom:
<br> set(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}" ${CMAKE_MODULE_PATH})<br><div><span class="gmail_quote"> include(CPack)<br>-5- Configured, built ALL, built PACKAGE<br><br>-6- Results: I know it used *my* copy of the
<a href="http://NSIS.template.in">NSIS.template.in</a> file because I inspected "_CPack_Packages/win32/NSIS/project.nsi" after building the PACKAGE target and my comments from bullet point -3- above were in there...
<br><br>Now. This is not to say that you can use any old <a href="http://NSIS.template.in">NSIS.template.in</a> file and get it to work properly. You do have to produce an output file that's named as CPack expects it to be named so that the rest of the packaging process works. If all you want to do is rename your output file, though, you can simply set the variable CPACK_OUTPUT_FILE_NAME before including CPack in your
CMakeLists.txt file.<br><br>I would recommend that you start with the <a href="http://NSIS.template.in">NSIS.template.in</a> file that CMake provides and edit it very carefully, only adding things to it. You can change/remove things from it if you're sure they're not needed by the rest of the packaging process that CPack performs. If you are still having problems getting this to work and you're using CMake
2.4.5 or greater, I would definitely be interested to hear back from you again. (With detailed steps on what you are doing and exactly what is failing.) This should work...<br><br><br>HTH,<br>David Cole<br><br><br>On 11/13/06,
<b class="gmail_sendername">wedekind</b> <<a href="mailto:wedekind@caesar.de">wedekind@caesar.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello David<br><br>> You should be able to use your own <a href="http://NSIS.template.in">NSIS.template.in</a> file if you name it<br>> exactly the same as CMake's copy and then add the directory containing<br>> your own copy of it to CMAKE_MODULE_PATH.
<br>><br>> For example, if your copy is in a subdirectory of your source directory<br>> named "Templates," you could do this...:<br>> SET(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/Templates"
<br>> ${CMAKE_MODULE_PATH})<br>> ... prior to including the CPack file in your CMakeLists.<br>><br>> Let me know if this doesn't work. I haven't tried it myself with this<br>> particular file, but it should work...
<br><br>Unfortunately this does not work for me :( I have set the CMAKE_MODULE_PATH<br>like you have described but CMake obviously chooses its own<br><a href="http://NSIS.template.in">NSIS.template.in</a>.<br><br>Why does overwriting the module path like this does not work? I have done it
<br>in my "root" CMakeLists.txt before including CPack.<br><br>Should CMake/CPack be expanded here?<br><br>Cheers<br><br>Marco<br><br><br></blockquote></div><br>