<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/11/2014 14:15, Cory Quammen
wrote:<br>
</div>
<blockquote
cite="mid:CAB5Fpx7SK6gJ6=92=SJg2Bp8zzwGxq-+WzVw+nmbKenVEYBUVw@mail.gmail.com"
type="cite">
<div dir="ltr">Mike,
<div><br>
</div>
<div>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.</div>
</div>
</blockquote>
Indeed, and I think the syntax is VAR=value as in:<br>
<br>
PATH=c:\Qt\5.3\msvc2012\bin<br>
<br>
Simples especially if you don't pollute your standard PATH with Qt
or any other Framework/Library on startup/login!<br>
<blockquote
cite="mid:CAB5Fpx7SK6gJ6=92=SJg2Bp8zzwGxq-+WzVw+nmbKenVEYBUVw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Hope that helps,</div>
<div>Cory</div>
</div>
</blockquote>
Regards<br>
Bill.<br>
<blockquote
cite="mid:CAB5Fpx7SK6gJ6=92=SJg2Bp8zzwGxq-+WzVw+nmbKenVEYBUVw@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Nov 1, 2014 at 9:54 AM, Michael
Jackson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">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".<br>
<br>
Looking forward to the answer<br>
Mike Jackson<br>
<div class="HOEnZb">
<div class="h5"><br>
On Oct 31, 2014, at 3:51 PM, Bill Somerville <<a
moz-do-not-send="true"
href="mailto:bill@classdesign.com">bill@classdesign.com</a>>
wrote:<br>
<br>
> On 31/10/2014 19:42, Michael Jackson wrote:<br>
>> 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:<br>
>><br>
>> CMP_COPY_QT4_RUNTIME_LIBRARIES(
"QtCore;QtGui;QtNetwork")<br>
> This seems an awful lot of messing around when <a
moz-do-not-send="true" href="http://qt-project.org"
target="_blank">qt-project.org</a> 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..<br>
><br>
> 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.<br>
><br>
> Regards<br>
> Bill.<br>
> --<br>
><br>
> Powered by <a moz-do-not-send="true"
href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Please keep messages on-topic and check the CMake
FAQ at: <a moz-do-not-send="true"
href="http://www.cmake.org/Wiki/CMake_FAQ"
target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
><br>
> Kitware offers various services to support the
CMake community. For more information on each offering,
please visit:<br>
><br>
> CMake Support: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/support.html"
target="_blank">http://cmake.org/cmake/help/support.html</a><br>
> CMake Consulting: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/consulting.html"
target="_blank">http://cmake.org/cmake/help/consulting.html</a><br>
> CMake Training Courses: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/training.html"
target="_blank">http://cmake.org/cmake/help/training.html</a><br>
><br>
> Visit other Kitware open-source projects at <a
moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html"
target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a moz-do-not-send="true"
href="http://public.kitware.com/mailman/listinfo/cmake"
target="_blank">http://public.kitware.com/mailman/listinfo/cmake</a><br>
<br>
--<br>
<br>
Powered by <a moz-do-not-send="true"
href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ
at: <a moz-do-not-send="true"
href="http://www.cmake.org/Wiki/CMake_FAQ"
target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Kitware offers various services to support the CMake
community. For more information on each offering, please
visit:<br>
<br>
CMake Support: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/support.html"
target="_blank">http://cmake.org/cmake/help/support.html</a><br>
CMake Consulting: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/consulting.html"
target="_blank">http://cmake.org/cmake/help/consulting.html</a><br>
CMake Training Courses: <a moz-do-not-send="true"
href="http://cmake.org/cmake/help/training.html"
target="_blank">http://cmake.org/cmake/help/training.html</a><br>
<br>
Visit other Kitware open-source projects at <a
moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html"
target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a moz-do-not-send="true"
href="http://public.kitware.com/mailman/listinfo/cmake"
target="_blank">http://public.kitware.com/mailman/listinfo/cmake</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>