HI all,
package is a builtin target unless things have changed you cannot depend on
a builtin target.
https://gitlab.kitware.com/cmake/cmake/issues/8438
https://cmake.org/Bug/view.php?id=8438
Personnally I would explicitely call CPack in my custom target in order to
be sure that the zip is
> Do you have any special reason why your rename target depends on PACKAGE,
is this the target which cpack is using?
I think so ...
2016-08-26 20:01 GMT+02:00 tonka3...@gmail.com :
> Hey Kristian,
>
> Thx for your answer. Iv've already done this like in your solution. I
Hey Kristian,
Thx for your answer. Iv've already done this like in your solution. I have a
seperated target which depends on my create zip target and use ${CMAKE_COMMAND}
-e copy to copy the file to my target directory (so the solution is platform
independent), and leaf the original zip in the
Hey,
you're working on Windows, right?
I think you can do that if you create an additional target and call that
target. So let's say, you have this 'hello.cpp', and you generate with
CMake a solution. This is an example of a CMakeLists.txt
> cmake_minimum_required(VERSION 3.4)
>
Hey everybody,
I try to rename the fileextension of my cpack zip file. So i use cpack -G ZIP
to create the package and get my zip file. Now i need to rename these
fileextension to another name, like microsoft did it with with docx word
format, where the file is a zip file, but has the docx