Probably what is going to happen is there will be "special" case copies from frameworks into bundles. In this case, copying the qt_menu.nib and any qt.conf is probably specific to QtGui.framework. At this point I there is probably 2 things that need to happen.
A bug report for the QtGui resources not being copied into ParaView and CMake A feature request to enhance the copying of Frameworks to include/exclude any of the directories within a framework. The first one should be quick to solve for someone on the ParaView/Cmake teams since it is the same code. The second one may be tougher because besides the couple of "well known" directories inside frameworks, a developer can pretty much put anything inside a framework. I'll leave it up to the CMake developers to come up with something if anything is really deemed needed. Of course my frustration is really ONLY valid if building CMake against Qt 4.5 is an Officially sanctioned/supported platform. If Qt 4.5 is Officially supported then CMake 2.8 is Broken and needs an update ASAP to bring it up to par. Period. If Qt 4.4 is the ONLY version sanctioned by CMake then nothing is really broken and the problem is my own. Same thing goes for ParaView as it suffers the same problem. _________________________________________________________ Mike Jackson mike.jack...@bluequartz.net On Sat, Dec 5, 2009 at 1:42 AM, Michael Wild <them...@gmail.com> wrote: > Yes, that is the only reason. They are bulky and useless, at least in the > case of CMake. > > Come to think of it, however, it could be useful if CMake offered the > possibility to install the various parts as different COMPONENTS. E.g., for > ParaView it would make sense to install the Qt headers as part of a "dev" > component. > > Michael > > On 4. Dec, 2009, at 23:26 , Clinton Stimpson wrote: > >> On Friday 04 December 2009 03:19:24 pm David Cole wrote: >>> >>> Do you have a good idea for how to implement "everything except the >>> headers"...? >> >> Maybe something like: >> install(DIRECTORY ... REGEX Headers EXCLUDE) >> >>> >>> There's already some pretty gnarly CMake script code in the fixup_bundle >>> routines. I'd like to keep it as simple and understandable as possible. >>> >>> I'm assuming your reason for not wanting the headers in there is simply >>> "they're useless and they take up unnecessary space" -- is there another >>> reason or is that it? >> >> Closed source packages may not want headers included in the frameworks. >> >> Clint >> > > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
