On Dec 21, 2010, at 11:45 AM, Mike McQuaid wrote:
On 21 December 2010 16:41, Clinton Stimpson <[email protected]>
wrote:
Would you prefer having a set of variables that point to the dlls,
or would
you rather have a function that takes a list of Qt modules and
copies the
necessary plugins for those Qt modules to a certain location?
It seems the latter is more desirable, and probably doesn't depend
on the
former. If the latter, should it also do a qt.conf file as well?
I think both would be useful. The latter could be in a BundleUtilities
equivalent specialised for Qt applications (something I'd love to help
develop) and is basically what macdeployqt does.
I think it would be good to be able to be pretty automated (e.g.
plugins for each modules) but there's also a good use-case for
providing full plugin paths through the FindQt4.cmake module, in my
opinion. You could just add a mapping on top of that of what plugins
"belong" to what modules.
--
Mike McQuaid
http://mikemcquaid.com
I would like to have variables to the DLLs also (actually ALL the
DLLs, not just the plugins) because under certain use cases those are
needed. Here is my use case.
Setup: Windows 7 x64 with Qt 4.6.x built as BOTH 32 and 64 bit and
installed into separate directories so that I can NOT put the Qt dirs
on the normal PATH variable which means when I go to debug in Visual
Studio I get complaints from VS that it can not find QtCore4.dll. So I
have CMake copy rules to copy the correct Qt libraries into the build
directory. Having the CMAKE variables to where the DLLs are located
would alleviate me from having to maintain that code. Just my 2 cents.
Oh, and if someone else has a "better" way of setting this up I am
open to all comments (off list if needed.)
___________________________________________________________
Mike Jackson www.bluequartz.net
Principal Software Engineer [email protected]
BlueQuartz Software Dayton, Ohio
_______________________________________________
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
