[CMake] Copying DLLs to output directory

[Bill Somerville]

On 01/11/2014 14:15, Cory Quammen wrote:
> Mike,
>
> You can modify or override the PATH variable in Visual Studio by 
> pulling up the properties for the startup project and going to 
> Configuration Properties -> Debugging, and add an entry for your 
> preferred PATH under the "Environment" setting.  By default, this will 
> merge your PATH with the PATH currently defined for Visual Studio, so 
> if you have a different Qt in your system PATH, you'll want to change 
> "Merge Environment" to No. Note that if you do this, you'll need to 
> add SystemRoot=C:\Windows to your path as well.
Indeed, and I think the syntax is VAR=value as in:

PATH=c:\Qt\5.3\msvc2012\bin

Simples especially if you don't pollute your standard PATH with Qt or 
any other Framework/Library on startup/login!
>
> Hope that helps,
> Cory
Regards
Bill.
>
> On Sat, Nov 1, 2014 at 9:54 AM, Michael Jackson 
> <mike.jackson at bluequartz.net <mailto:mike.jackson at bluequartz.net>> wrote:
>
>     The thing I could never figure out is how to set the PATH for the
>     Visual Studio Project/Solution. That is what I need. If I only had
>     a single version of Qt on my system it would be very straight
>     forward. Just set the PATH environment variable using the standard
>     windows mechanism for doing that and you are set. Alas, that isn't
>     the case. I have at least 4 different versions of Qt on my system
>     at any one time. So tell me how to, in the CMake file, to tell the
>     Visual Studio generated solution to add
>     C:/Developer/x64/Qt-4.8.6/bin to my PATH and I would gladly rip
>     out all my code. I also need a mechanism to "install" all those
>     DLL's into an redistributable package (which my scripts ensure).
>     Maybe I am just that far behind the times. One of those "if it
>     aint broke don't fix it".
>
>     Looking forward to the answer
>     Mike Jackson
>
>     On Oct 31, 2014, at 3:51 PM, Bill Somerville <bill at classdesign.com
>     <mailto:bill at classdesign.com>> wrote:
>
>     > On 31/10/2014 19:42, Michael Jackson wrote:
>     >> Never said it was pretty, but here is the code I use for Qt4
>     based projects. I think I had to revamp a lot of this for Qt5. I
>     call it like so:
>     >>
>     >> CMP_COPY_QT4_RUNTIME_LIBRARIES( "QtCore;QtGui;QtNetwork")
>     > This seems an awful lot of messing around when qt-project.org
>     <http://qt-project.org> already dump all the debug and release
>     libraries into the installation bin directory so all you need is
>     to ensure that the installation bin directory is on your PATH when
>     you run or debug executables, just like you have to to build using
>     the tools like moc, qmake, dumpcpp, qrc, etc..
>     >
>     > IMHO put he Qt bin directory on PATH for debugging and use
>     BundleUtils FixupBundle to make deployable kits. No need to do any
>     manual or scripted copying of libraries at all.
>     >
>     > Regards
>     > Bill.
>     > --
>     >
>     > Powered by www.kitware.com <http://www.kitware.com>
>     >
>     > Please keep messages on-topic and check the CMake FAQ at:
>     http://www.cmake.org/Wiki/CMake_FAQ
>     >
>     > Kitware offers various services to support the CMake community.
>     For more information on each offering, please visit:
>     >
>     > CMake Support: http://cmake.org/cmake/help/support.html
>     > CMake Consulting: http://cmake.org/cmake/help/consulting.html
>     > CMake Training Courses: http://cmake.org/cmake/help/training.html
>     >
>     > Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>     >
>     > Follow this link to subscribe/unsubscribe:
>     > http://public.kitware.com/mailman/listinfo/cmake
>
>     --
>
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Please keep messages on-topic and check the CMake FAQ at:
>     http://www.cmake.org/Wiki/CMake_FAQ
>
>     Kitware offers various services to support the CMake community.
>     For more information on each offering, please visit:
>
>     CMake Support: http://cmake.org/cmake/help/support.html
>     CMake Consulting: http://cmake.org/cmake/help/consulting.html
>     CMake Training Courses: http://cmake.org/cmake/help/training.html
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/cmake
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20141101/036848e9/attachment.html>