<div class="gmail_quote">On Fri, Jun 18, 2010 at 1:01 PM, Tyler Roscoe <span dir="ltr"><<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Jun 18, 2010 at 06:30:25PM +0200, Eric Noulard wrote:<br>
> 2010/6/18 Tyler Roscoe <<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>>:<br>
> > 1. I want to change where "make package" deposits the packages it<br>
> > creates. Is there a way to do this -- some cpack variable I haven't<br>
> > found?<br>
><br>
> No variable I am aware of.<br>
> However you may create a custom target which call make package and then<br>
> move the file, provided you know the name of the generated file ....<br>
<br>
</div>The frustrating part here is that I can't add_dependencies or post-build<br>
custom_commands to the PACKAGE target because it is a "magic" CMake<br>
target. I suppose I can look into writing a custom_command that runs<br>
cpack with appropriate arguments, but I hoped to avoid this step.<br></blockquote><div><br></div><div>But you could make a "build-products-done" custom target, and then use add_dependencies with that and all the other "real" CMake targets that you have to make it go last after all the real stuff is built.</div>
<div><br></div><div>Then you can add another custom target to do as much 'make package' type stuff as you want and make it depend on the "build-products-done" custom target...</div><div><br></div><div>Because to do what you want, you want multiple make package steps anyhow, right?</div>
<div><br></div><div><br></div><div>HTH,</div><div>David</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> > but how do I calculate "some_extension"? Is there some mapping between package type<br>
> > (TGZ, ZIP, NSIS) and the extension it ends up with (.tar.gz, .zip,<br>
> > .exe)?<br>
><br>
> Concerning the extension, it is fixed in the C++ code of the generator<br>
> in the GetOutputExtension method:<br>
<br>
</div>Yeah, I was afraid of this. Looks like I'll need to maintain my own<br>
mapping of cpack generator types -> extensions on disk.<br>
<br>
Thanks for your help, Eric.<br>
<font color="#888888"><br>
tyler<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br>