On 2017-08-14 15:33-0600 d...@ucar.edu wrote:
I have the following situation using cmake
1. Running windows 7
2. Both cygwin and visual studio (VS) community edition (version 14)
installed.
3. I am building with visual studio as my compiler.
4. Cygwin has winsock2.h in /usr/include/w32api
Th
I have the following situation using cmake
1. Running windows 7
2. Both cygwin and visual studio (VS) community edition (version 14)
installed.
3. I am building with visual studio as my compiler.
4. Cygwin has winsock2.h in /usr/include/w32api
The VS community edition does not have winsock2.
Right, as mentionned by Craig Scott, a script might do the trick ? Just a
cmake-gui.bat that calls cmake-gui.exe should work.
De : Robert Maynard
Envoyé le :lundi 14 août 2017 15:24
À : Craig Scott
Cc : Clément Gregoire; CMake
Objet :Re: [CMake] cmake-gui on windows and qt5 dlls
More importantly
14.08.2017, 16:01, "Craig Scott" :
> On Mon, Aug 14, 2017 at 9:05 PM, Clément Gregoire wrote:
>> Wouldn't it be possible to move it to a subfolder with the DLLs and put a
>> link next to cmake and ccmake? Executables look for DLLs in their directory
>> and it wouldn't pollute the PATH
>
> Syml
More importantly symlinks are restricted to administrator accounts
only in Windows Vista/7/8. Windows 10 with Developer Mode activated
allows none-elevated accounts to create symlinks.
This is important as CMake does ship non-installer windows binaries.
On Mon, Aug 14, 2017 at 9:00 AM, Craig Scot
On Mon, Aug 14, 2017 at 9:05 PM, Clément Gregoire wrote:
> Wouldn't it be possible to move it to a subfolder with the DLLs and put a
> link next to cmake and ccmake? Executables look for DLLs in their directory
> and it wouldn't pollute the PATH
>
Symlinks are available on NTFS filesystems from
Wouldn't it be possible to move it to a subfolder with the DLLs and put a
link next to cmake and ccmake? Executables look for DLLs in their directory
and it wouldn't pollute the PATH
I personally like to be able to launch it through the command line, it is
faster than looking for it and then brows
This is a common problem, not just with CMake. I'm wondering if there's any
real need for cmake-gui to be on the PATH at all, since it will usually be
invoked by a desktop or menu icon. At the moment though, it is in the same
directory as the cmake and ccmake executables which have a much stronger
Hi,
I recently upgraded from cmake 3.3 to 3.9 on windows and got some problems during my build because it looks like the pre-compile binaries for windows are now shipping Qt5 - dlls instead static compile libs (since 3.5 afaics).
The problem is, that I had the path to cmake *before* the path t
