Hello Eric, hello David, sorry for the long response time.
I noticed that the custom CPackConfig is not necessary if I use variable names beginning with CPACK_. So first I removed the custom file. Then the main problem... I don't use a changed NSIS.template.in file from the CMake installation. I use a NSIS script from a college and tried to use it under CPack. This means than I used CPACK variable names instead of hard coded values. However I'm a NSIS novice, so it seems that in a CPACK variable and/or in the original NSIS.template.in file are some commands which I didn't find. The only one I need is the command which copies the necessary files into the temporary CPack directory (_CPack_Packges). Which CPack variable and/or NSIS commands from the original template file are required to solve this? Thanks in advance Best Regards Am 09.05.2012 um 20:45 schrieb "NoRulez" <noru...@me.com>: > >> By the way could you try 2.8.8 instead of 2.8.7 ? > Yes, I will try it tomorrow (I read the changelog > http://www.cmake.org/files/v2.8/CMakeChangeLog-2.8.8 but I can't find any > details where this behavior may be fixed) > Because on our Buildserver CMake 2.8.7 is installed and if no relevant > changes are made in 2.8.8, then I would be happy if I could retain the CMake > 2.8.7 installation (Never change a running system ;-)) > > But I will try 2.8.8 on the workstation and send you the output from 2.8.7 > ("--verbose --debug"). > > Best Regards > > Am 09. Mai 2012 um 11:31 schrieb Eric Noulard <eric.noul...@gmail.com>: > >> 2012/5/9 <noru...@me.com>: >> >>> Is it the case? Is there any file in _CPack_Packages\win32\NSIS\MyProject >> >>> ? >> > No, there aren't any files >> > >> > >> >>> Could you copy/paste the exact message you get and may be running cpack >> >>> on the command line with ---verbose and --debug. >> > Sure, but I can only do so tomorrow >> > >> > >> >>> Nope normally you don't but what are you doing in your >> >>> "CPackConfig.cmake.in" ? >> > I only set the CPACK variables and additional variables which are used in >> > the NSIS.template.in file. >> > Because if I don't use the custom CPackConfig.cmake.in file then the >> > variables in the NSIS.template.in files aren't resolved. >> >> Please send us those files. >> As usual the devil may be in the details. >> >> >>> And do you have any INSTALL(CODE or INSTALL(SCRIPTS in your project? >> > Yes, i use this for the BundleUtilities like in the BundleUtilities example >> > >> > INSTALL(CODE " >> > file(GLOB_RECURSE SHARED_LIBS >> > \"\${CMAKE_INSTALL_PREFIX}/*${CMAKE_SHARED_LIBRARY_SUFFIX}\") >> > include(BundleUtilities) >> > fixup_bundle(\"${APPS}\" \"\${SHARED_LIBS}\" \"${DIRS}\") >> > " COMPONENT Runtime) >> >> I'm not a BundleUtilities user but code like that may break with CPack >> because >> CPack may internally use DESTDIR to do its local installation so that >> one should usually write: >> >> $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX} >> rather than >> ${CMAKE_INSTALL_PREFIX} >> >> however since you have NO file at all in the local CPack install dir, >> the problem is elsewhere. >> >> By the way could you try 2.8.8 instead of 2.8.7 ? >> >> -- >> Erk >> Le gouvernement représentatif n'est pas la démocratie -- >> http://www.le-message.org > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake
-- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
