<div class="gmail_quote"><div>Hi,</div><div><br></div><div>Thanks for you replies,</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>
> In my case the output is the ZIP file. So the zip file is produced by the<br>
> top level target, and I don't want/need a separate target for it.<br>
<br>
</div>Yes but CMake's jobs is to build libraries and executables not "bundle"<br>
which is more the CPack's job, however I understand your point.<br>
<br>
An extra target may be a small price to pay, no?<br></blockquote><div><br></div><div>Well I'd rather have a solution without CPack, CPack being a package creator, whereas my bundle is a development item.</div><div>If all fails I could make the extra target, but again, the zip file in my case is equivalent to a library.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
<br>
</div>Yes sure, sometimes file dependencies are needed.<br>
<br>
By the way I see you custom-commands in order to create a bundle on MacOS?<br>
Did you try try CPack MacOSX bundle generator?<br>
<a href="http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#Bundle_.28OSX_only.29" target="_blank">http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#Bundle_.28OSX_only.29</a><br>
<br></blockquote><div><br></div><div>My "bundles" don't have anything to do with MacOS bundles, the name is a coincidence. Some background might be helpful now.. </div><div><br></div><div>I am using CMake to build Apache Celix, which is a project in the Apache Incubator. Apache Celix is an implementation of the OSGi specification in C. I am not sure if you are familiar with OSGi, but it provides a modular system for Java in which new functionality can be added/removed/updated at runtime. In Java OSGi a bundle is a regular Jar file with additional information in the Manifest file.</div>
<div>For Celix we use a similar solution (since a jar file is actually a zip file..) where the library is packed in a zip file together with the manifest file. One bundle contains always one library, this is why I see the Celix bundles as top level artifacts, and not the library. As such, from the Celix point of view it makes sense to have one target for creating a Bundle.</div>
<div><br></div><div>More information can be found at: <a href="http://incubator.apache.org/celix/">http://incubator.apache.org/celix/</a></div><div>And specifically on the build files: <a href="http://incubator.apache.org/celix/documentation/buildingandrunning.html">http://incubator.apache.org/celix/documentation/buildingandrunning.html</a></div>
<div><br></div><div>I hope this makes all a little bit clearer, I understand I am using a rather specific solution, but the flexibility of CMake has really helped my achieving what I wanted (until now?). This way fits the modular development needed in an OSGi based environment.</div>
<div><br></div></div><div><br></div>-- <br>Met vriendelijke groet,<br><br>Alexander Broekhuis<br>