On Sat, May 19, 2012 at 2:51 PM, wrote:
> Sorry, but the project is a commercial application.
>
> Did you mean this site?
> http://www.cmake.org/cmake/help/cmake_tutorial.html#s7
>
No, I meant this directory within the CMake source tree:
http://cmake.org/gitweb?p=cmake.git;a=tree;f=Tests/Tutor
I don't know how, but the problem is solved. If I find out the problem I'll
post it on the list.
What i've done was to begin from scratch with the installers CMakeLists.txt and
the custom NSIS template.
Much thanks to Eric and David for the hint with the "--verbose --debug" command
line argume
Sorry, but the project is a commercial application.
Did you mean this site? http://www.cmake.org/cmake/help/cmake_tutorial.html#s7
But there must something in the original *.nsi file, because if I use the
original file then the files get copied (Without changing the CMakeLists.txt
file)
On the
CPack does a "make install" and puts your install tree underneath
_CPack_Packages.
THEN, it calls NSIS with the *.nsi script, and packages that up into an
installer.
There is nothing in the *.nsi file that copies anything into
_CPack_Packages. That happens before makensis is ever called.
Please
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.
>> 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
2012/5/9 :
>>> 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
>
>
>> 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 a
2012/5/9 :
[...]
>
> If I run the INSTALL target under VS then the files are correctly copied to
> C:\Program Files\MyProject
> But only the PACKAGE target under VS doesn't work, and I get the message
> from the last email I sent.
>> So, my custom CPackConfig.cmake.in and my NSIS.template.in see
2012/5/9 David Cole :
> What do your install commands look like?
>
> You're not trying to install files into absolute paths on Windows, are you?
This can be checked easily by running:
cpack --debug -G NSIS
then you should get message like:
Got some ABSOLUTE DESTINATION FILES: ...
This can be f
The install command looks something likemacro(InstallTarget TARGET) INSTALL(TARGETS ${TARGET}
BUNDLE DESTINATION .
RUNTIME DESTINATION .ARCHIVE DESTINATION .LIBRARY DESTINATION .
)endmacro(InstallTarget)...InstallTarget(MyApp)..InstallTarget(MyLib)Other files
What do your install commands look like?
You're not trying to install files into absolute paths on Windows, are
you? (i.e. -- all things should be installed underneath
CMAKE_INSTALL_PREFIX in a normal 'make install' tree in order to work
well on Windows with the NSIS generator.)
On Wed, May 9,
Hello Eric,I've found the problem, it was my mistake. A few lines later i overwrote the CPACK_MODULE_PATH setting. [RESOLVED]
But what I didn't understand was the fact that it would work on Windows 7 with the same settings.So, my custom CPackConfig.cmake.in and my NSIS.template.in seems to work, b
It is only a copy from the original. It doesn't work in windows xp in general.
Best Regards
Am 08.05.2012 um 13:51 schrieb Eric Noulard :
> 2012/5/8 :
>> There is no difference with your command. It still uses the NSIS.template.in
>> file from the CMake installation.
>
> Are there any differe
2012/5/8 :
> There is no difference with your command. It still uses the NSIS.template.in
> file from the CMake installation.
Are there any difference between the 2 CPackConfig.cmake files ?
WinXP failing case vs Win7 working case?
Does the ${CMAKE_SOURCE_DIR}/cmake/NSIS.template.in file has an
There is no difference with your command. It still uses the NSIS.template.in
file from the CMake installation.
Yes I tried the configurations in new build directories such as build1 ...
buildn.
Am 08.05.2012 um 11:52 schrieb Eric Noulard :
> 2012/5/8 :
>> I use CMake 2.8.7 from the zip archi
2012/5/8 :
> I use CMake 2.8.7 from the zip archive.
> Out of source builds are the defaults, so yes I use out of source builds.
Good.
But did you try with fresh new (empty) build tree AND fresh new
checked-out source tree?
> I tried CMP0017 with NEW and with OLD, but there is no difference, no
2012/5/8 :
> Hello,
>
> I had a custom NSIS template under ${CMAKE_SOURCE_DIR}/cmake
>
> Then I added those path to CMAKE_MODULE_PATH. But my custom template gets
> never called.
> If I run cpack --verbose I can see that cpack uses the template from the
> CMake installation.
Which version of CM
Hello,
I had a custom NSIS template under ${CMAKE_SOURCE_DIR}/cmake
Then I added those path to CMAKE_MODULE_PATH. But my custom template gets never
called.
If I run cpack --verbose I can see that cpack uses the template from the CMake
installation.
The strange thing is, that it would work on W
19 matches
Mail list logo
