<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=FR link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Right, as mentionned by Craig Scott, a script might do the trick ? Just a cmake-gui.bat that calls cmake-gui.exe should work.</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>De : </b><a href="mailto:robert.maynard@kitware.com">Robert Maynard</a><br><b>Envoyé le :</b>lundi 14 août 2017 15:24<br><b>À : </b><a href="mailto:craig.scott@crascit.com">Craig Scott</a><br><b>Cc : </b><a href="mailto:lectem@gmail.com">Clément Gregoire</a>; <a href="mailto:cmake@cmake.org">CMake</a><br><b>Objet :</b>Re: [CMake] cmake-gui on windows and qt5 dlls</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>More importantly symlinks are restricted to administrator accounts</p><p class=MsoNormal>only in Windows Vista/7/8. Windows 10 with Developer Mode activated</p><p class=MsoNormal>allows none-elevated accounts to create symlinks.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This is important as CMake does ship non-installer windows binaries.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On Mon, Aug 14, 2017 at 9:00 AM, Craig Scott <craig.scott@crascit.com> wrote:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> On Mon, Aug 14, 2017 at 9:05 PM, Clément Gregoire <lectem@gmail.com> wrote:</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> Wouldn't it be possible to move it to a subfolder with the DLLs and put a</p><p class=MsoNormal>>> link next to cmake and ccmake? Executables look for DLLs in their directory</p><p class=MsoNormal>>> and it wouldn't pollute the PATH</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Symlinks are available on NTFS filesystems from Vista onwards. If the user</p><p class=MsoNormal>> installed CMake on, say, a FAT filesystem instead or on an old XP box (CMake</p><p class=MsoNormal>> appears to still try to support that), then symlinks wouldn't be available</p><p class=MsoNormal>> from what I can make out. One could potentially use a forwarding script of</p><p class=MsoNormal>> some kind though to achieve essentially the same thing.</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>>> I personally like to be able to launch it through the command line, it is</p><p class=MsoNormal>>> faster than looking for it and then browse for the folder.</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> Le lun. 14 août 2017 à 11:48, Craig Scott <craig.scott@crascit.com> a</p><p class=MsoNormal>>> écrit :</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> This is a common problem, not just with CMake. I'm wondering if there's</p><p class=MsoNormal>>>> any real need for cmake-gui to be on the PATH at all, since it will usually</p><p class=MsoNormal>>>> be invoked by a desktop or menu icon. At the moment though, it is in the</p><p class=MsoNormal>>>> same directory as the cmake and ccmake executables which have a much</p><p class=MsoNormal>>>> stronger case for being on the PATH. There's a reasonable argument that</p><p class=MsoNormal>>>> cmake-gui should be in a different directory, then it wouldn't be an issue</p><p class=MsoNormal>>>> if shared Qt libs were used rather than static. I'll bring this up on the</p><p class=MsoNormal>>>> developer mailing list and see what discussions yield.</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> On Mon, Aug 14, 2017 at 6:22 PM, Christian Ehrlicher</p><p class=MsoNormal>>>> <Ch.Ehrlicher@gmx.de> wrote:</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> Hi,</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> I recently upgraded from cmake 3.3 to 3.9 on windows and got some</p><p class=MsoNormal>>>>> problems during my build because it looks like the pre-compile binaries for</p><p class=MsoNormal>>>>> windows are now shipping Qt5 - dlls instead static compile libs (since 3.5</p><p class=MsoNormal>>>>> afaics).</p><p class=MsoNormal>>>>> The problem is, that I had the path to cmake *before* the path to my own</p><p class=MsoNormal>>>>> Qt5 libaries. So during the build / run of my application, the wrong</p><p class=MsoNormal>>>>> libraries were loaded and I got a symbol lookup error.</p><p class=MsoNormal>>>>> Would it be possible to use the static Qt5 libs instead or maybe prefix</p><p class=MsoNormal>>>>> the Qt5 libs shipped with cmake-gui somehow?</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> Thx,</p><p class=MsoNormal>>>>> Christian</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> --</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> Powered by www.kitware.com</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> Please keep messages on-topic and check the CMake FAQ at:</p><p class=MsoNormal>>>>> http://www.cmake.org/Wiki/CMake_FAQ</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> Kitware offers various services to support the CMake community. For more</p><p class=MsoNormal>>>>> information on each offering, please visit:</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> CMake Support: http://cmake.org/cmake/help/support.html</p><p class=MsoNormal>>>>> CMake Consulting: http://cmake.org/cmake/help/consulting.html</p><p class=MsoNormal>>>>> CMake Training Courses: http://cmake.org/cmake/help/training.html</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> Visit other Kitware open-source projects at</p><p class=MsoNormal>>>>> http://www.kitware.com/opensource/opensource.html</p><p class=MsoNormal>>>>><o:p> </o:p></p><p class=MsoNormal>>>>> Follow this link to subscribe/unsubscribe:</p><p class=MsoNormal>>>>> http://public.kitware.com/mailman/listinfo/cmake</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> --</p><p class=MsoNormal>>>> Craig Scott</p><p class=MsoNormal>>>> Melbourne, Australia</p><p class=MsoNormal>>>> https://crascit.com</p><p class=MsoNormal>>>> --</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> Powered by www.kitware.com</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> Please keep messages on-topic and check the CMake FAQ at:</p><p class=MsoNormal>>>> http://www.cmake.org/Wiki/CMake_FAQ</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> Kitware offers various services to support the CMake community. For more</p><p class=MsoNormal>>>> information on each offering, please visit:</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> CMake Support: http://cmake.org/cmake/help/support.html</p><p class=MsoNormal>>>> CMake Consulting: http://cmake.org/cmake/help/consulting.html</p><p class=MsoNormal>>>> CMake Training Courses: http://cmake.org/cmake/help/training.html</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> Visit other Kitware open-source projects at</p><p class=MsoNormal>>>> http://www.kitware.com/opensource/opensource.html</p><p class=MsoNormal>>>><o:p> </o:p></p><p class=MsoNormal>>>> Follow this link to subscribe/unsubscribe:</p><p class=MsoNormal>>>> http://public.kitware.com/mailman/listinfo/cmake</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> --</p><p class=MsoNormal>> Craig Scott</p><p class=MsoNormal>> Melbourne, Australia</p><p class=MsoNormal>> https://crascit.com</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> --</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Powered by www.kitware.com</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Please keep messages on-topic and check the CMake FAQ at:</p><p class=MsoNormal>> http://www.cmake.org/Wiki/CMake_FAQ</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Kitware offers various services to support the CMake community. For more</p><p class=MsoNormal>> information on each offering, please visit:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> CMake Support: http://cmake.org/cmake/help/support.html</p><p class=MsoNormal>> CMake Consulting: http://cmake.org/cmake/help/consulting.html</p><p class=MsoNormal>> CMake Training Courses: http://cmake.org/cmake/help/training.html</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Visit other Kitware open-source projects at</p><p class=MsoNormal>> http://www.kitware.com/opensource/opensource.html</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Follow this link to subscribe/unsubscribe:</p><p class=MsoNormal>> http://public.kitware.com/mailman/listinfo/cmake</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>