ker please (
https://gitlab.kitware.com/cmake/cmake/issues )
On Wed, May 22, 2019 at 9:44 AM Niels Dekker wrote:
Previous versions of CMake GUI (prior to CMake 3.14) always displayed
the name of the selected platform (typically "Win32" or "Win64") with
the current generator, for e
ossible to get the VS platform name back onto the CMake GUI
main window?
Kind regards, Niels
--
Niels Dekker
Scientific programmer
LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake
ject
file (also with the INTERPROCEDURAL_OPTIMIZATION_RELEASE line
commented out).
I have just spent some time trying to debug it, but I don’t have a
full copy of Visual Studio. I have this information from CDB.exe. Is
that more use?
--
Niels Dekker
Scientific programmer
LKEB, Leiden Unive
OOST_ROOT="C:\Libraries\boost_1_66_0" ../
However this works fine:
cmake -Ax64 -G"Visual Studio 15 2017" -DHDE_CREATE_DOCS=%MAKE_DOCS%
-DBOOST_ROOT="C:\Libraries\boost_1_66_0" ../
Any ideas? I don’t have a debugger on Windows to look at it at the
moment.
--
Niels De
pplication, after enabling IPO.
Note that my request to enable IPO "by default" for Release
configurations has been rejected, at least for the time being:
https://gitlab.kitware.com/cmake/cmake/issues/17720 So for now, users
have to explicitly switch on this option.
Kind r
:04:52 +0100
From: Niels Dekker
Thank you for your encouraging replies, Johannes and Cristian.
In the meantime I created "default" Visual C++ projects on Visual
Studio 2008, Visual Studio 2010, Visual Studio 2013, Visual Studio
2015 and Visual Studio 2017 (from within the IDE, without us
in CMake would be great. Fewer target specifics to worry
about…
FROM: Cristian Adam
SENT: Wednesday, January 24, 2018 21:42
TO: Niels Dekker
CC: cmake
SUBJECT: Re: [CMake] Link Time Code Generation (LTGC) by default, for
Release configurations of Visual Studio projects?
Hi,
I had a quick
quot; "user32.lib" "gdi32.lib" "winspool.lib"
"shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "comdlg32.lib"
"advapi32.lib"
/IMPLIB:"F:/X/Bin/vc141-64/MyProject/Release/MyExecutable.lib"
/MACHINE:X64 /INCREMENTAL:NO
that doing so disables all warnings in a project. If you
want to disable only warnings from header files, you can do #pragma
warning(push, 0) before the #include statement, and #pragma
warning(pop) afterwards. But of course, that's just Visual C++, not CMake!
Good luck!
Niels
--
Niels
Thanks to both Rolf Eike Beer and Petr Kmoch for showing me that the
variable is documented as "CMAKE__COMPILER_VERSION". :-)
Kind regards, Niels
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers vari
ake_Useful_Variables ?
Kind regards, Niels
--
Niels Dekker
Scientific programmer at LKEB
Leiden University Medical Center
--
Powered by 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
On May 10 2014, Iulian-Nicu Şerbănoiu wrote:
Isn't it better to use vsvars32.bat? (or vsvars64.bat? - don't have
a 64 bit windows)
vcvarsall.bat supports both 32-bits and 64-bits, as it may calls either
vcvars32.bat or vcvars64.bat (depending on its optional argument, see
http://msdn.microsof
On 5/9/2014 11:58 AM, David Cole wrote:
If you use get_filename_component in conjunction with paths that contain
".." or Windows-style component separators ("\"), you can always clean
up the resulting string with the "ABSOLUTE" argument to
get_filename_component. It will collapse any "/../" or "/
Thanks for suggesting CMAKE_CXX_COMPILER, David. Cool! Indeed, the
following appears to work fine, as I tested with CMake 2.8.12.2 (for
both Visual C++ 2008 and Visual C++ 2013):
get_filename_component(MY_COMPILER_DIR
${CMAKE_CXX_COMPILER} DIRECTORY)
find_file(MY_VCVARSALL_BAT vcvarsall
Thanks for your suggestions, J Decker and David. I find both approaches
(using registry entry paths as hints to find_program or using
$ENV{VS110COMNTOOLS}) quite interesting. However, I'd rather not have to
write such code for each compiler version separately, in my CMakeLists.
Also I have the
eft
undocumented intentionally, as it appears to be an internal variable:
0008065: CMAKE_LINKER not mentioned on --help-variables
http://www.cmake.org/Bug/view.php?id=8065
Closed as "won't fix"
Does that mean we should not use ${CMAKE_LINKER}? If so, do you have
another sug
ks to marco1475 (at
https://cmaketools.codeplex.com/workitem/2) and Marek Vojtko for
mentioning this option :-)
Kind regards, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
Please keep mes
?
Kind regards, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by 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
://cmaketools.codeplex.com
Thanks, David. Would you advise users of RC3 of CMake Tools for Visual
Studio to upgrade to the final version?
Kind regards, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
Please
e defined!"
#endif
Kind regards,
Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://w
t via drive 'V:', instead of drive 'D:'. And guess
what, Visual Studio 2010 allows viewing the C/C++ properties of
individual source files!
HTH, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
P
ill did so already:
0012324: FindDCMTK: Does not fully support DCMTK 3.6.0
http://public.kitware.com/Bug/view.php?id=12324
Kind regards, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
V
ually I guess
you don't want your application to depend on the PATH at the end user
machine. However, I haven't yet tried to build an "isolated application"
according to your reference [3]
(http://msdn.microsoft.com/en-us/library/aa375190%28VS.85%29.aspx). Would
you recommend
add 'subst B: D:\' to my system startup :-)
Kind regards,
Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/o
s) of the path
names of the source files. So I guess one might work around this issue by
mapping a new drive letter to the build/bin directory, even while this
directory might be located at the same physical drive as the source files.
Right?
Kind regards,
Niels
--
Niels Dekker
http://www.xs4a
work on your VS10 installation!
- Original Message -
From: "Niels Dekker - address until 2014"
To: cmake at cmake.org
Sent: Thursday, November 10, 2011 17:29
Subject: Re: [CMake] Visual Studio 10 property pages for single source file
gone with CMake 2.8.5 and 2.8.6
highly appreciated, of course :-)
Kind regards,
Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource
path names *without* drive letter! Would it be possible for CMake to write
the source file names *without* the drive letter, when it generates Visual
Studio 10 vcxproj files? (Especially when the generated vcxproj files are
located at the same drive as the source files.)
Kind regards,
Niel
itweb?p=cmake.git;h=25116a3c
Thank you, Brad!
Kind regards,
Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opens
hose annoying "D9035" compiler warnings
("option 'nologo-' has been deprecated"). :-)
Kind regards,
Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
Powered by www.kitware.com
Visit other Kitwa
http://public.kitware.com/Bug/view.php?id=12323 ("FindDCMTK cannot find
all includes for MSVC build of DCMTK", by Dan Thill) See also my note:
http://public.kitware.com/Bug/bug_relationship_graph.php?bug_id=12323#bugnotes
Kind regards, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/
ful!
FYI, I'm using cmake-gui 2.8.5.
Kind regards,
Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
___
Powered by www.kitware.com
Visit other Kitware open-source pr
32 matches
Mail list logo