<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
By the way did you suppress the INSTALL rule concerning the MANIFEST<br>
you may have had before?<br></blockquote><div><br></div><div>Yes, this is what I tried. CMake seems to make an intermediate directory which is zipped. So the order of the INSTALL/CPACK_INSTALLED_DIRECTORIES doesn't seem to have an impact.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
I bet the safest way to build your jar may be to craft the appropriate<br>
'jar' whatever command<br>
wrapped-up in a CMake custom command/target<br>
(see add_custom_command add_custom_targt)<br>
may be something that would<br>
<br>
1) call cpack -G ZIP in order to have the clean zip file<br>
2) jar xvf your_package.zip<br>
3) jar cvf your_package.jar<br>
<br>
or use any custom option for jar in step 3.<br>
<br>
This is clearly doable with a CMake scripts.<br></blockquote><div><br></div><div>Thanks for the hints, I have now solved it this way. I was hoping it would be simple to add a new generator to CPack.</div><div><br></div></div>
<div><br></div>-- <br>Met vriendelijke groet,<br><br>Alexander Broekhuis<br>