<div dir="ltr">set(deepPublicHeaders fooDeepPublic.h fooDeepPublic1.h fooDeepPublic2.h ..........)<br>set_property(SOURCE ${deepPublicHeaders}<br>
PROPERTY MACOSX_PACKAGE_LOCATION Headers/Deep<br>
)<br>
<br>...should work, too. One call per list of headers with a unique folder name shouldn't be *too* verbose.<br><br><br><div class="gmail_quote">On Wed, Aug 6, 2008 at 4:42 PM, Mike Jackson <span dir="ltr"><<a href="mailto:mike.jackson@imts.us">mike.jackson@imts.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am starting to explore the Framework creation from CMake 2.6. In my first attempt things generally were created correctly except for the Headers folder. All my includes are in a flat hierarchy. I need my Headers to retain their folder layout like they do when creating a normal dylib installation.<br>
<br>
Is this supported? or am I just missing a step maybe?<br>
<br>
I am working from the example in the Test/Frameworks folder and I see this:<br>
set_property(SOURCE fooDeepPublic.h<br>
PROPERTY MACOSX_PACKAGE_LOCATION Headers/Deep<br>
)<br>
<br>
I have like 100 Headers for my project. That is going to get pretty verbose pretty quick if I have to do that for each header..<br>
<br>
-- <br>
Mike Jackson Senior Research Engineer<br>
Innovative Management & Technology Services<br>
<br>
<br>
<br>
_______________________________________________<br>
CMake mailing list<br>
<a href="mailto:CMake@cmake.org" target="_blank">CMake@cmake.org</a><br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div><br></div>