[cmake-developers] [CMake 0015663]: externalproject cause make -j build failure the first time
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15663 == Reported By:Laurent Demailly Assigned To: == Project:CMake Issue ID: 15663 Category: CMake Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2015-07-23 13:50 PDT Last Modified: 2015-07-23 13:50 PDT == Summary:externalproject cause make -j build failure the first time Description: the first time someone builds a cmake generated makefile, using -j yields a broken build because somehow the download of the external projects isn't complete the dependencies should be set correctly such as make waits for that target to complete ? https://github.com/facebook/wdt/issues/12 Steps to Reproduce: git clone https://github.com/facebook/wdt.git mkdir build; cd build cmake ../wdt -G Unix Makefiles -DBUILD_TESTING=on make -j this isn't mac specific - same issue with Ubuntu - could be a bug in our cmakelist.txt https://github.com/facebook/wdt/blob/master/CMakeLists.txt#L212 is where we add gmock == Issue History Date ModifiedUsername FieldChange == 2015-07-23 13:50 Laurent DemaillyNew Issue == -- 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 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-developers
Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015
On 23-Jul-15 12:32, Konstantin Podsvirov wrote: Hi dear CMake developers! Meet modern CMake built on MSVC2015 c QtDialog based on Qt 5.5 from today :-) Windows 32bit: http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe Windows 64bit: http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe As always, questions and suggestions are welcome. -- Regards, Konstantin Podsvirov Both versions can't start because dll missing: api-ms-win-crt-runtime-l1-1-0.dll Win 7 x64 Ruslan -- 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 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-developers
[cmake-developers] malware?
hi I downloaded cmake an hour ago from cmake.org http://cmake.org/ and found myself with an unwanted piece of software called “advanced mac cleaner”, an app that was hard to get rid of. I’m not certain it came from your site but it happened at the same time and I can’t think of any other explanation.. The download file from cmake.org http://cmake.org/ (supposedly the latest stable dmg for mac) was much bigger (30MB) than the cmake file I subsequently downloaded from github. -- 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 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-developers
Re: [cmake-developers] malware?
On 24/07/15 07:04, David Powell wrote: hi I downloaded cmake an hour ago from cmake.org http://cmake.org/ and found myself with an unwanted piece of software called “advanced mac cleaner”, an app that was hard to get rid of. I’m not certain it came from your site but it happened at the same time and I can’t think of any other explanation.. The download file from cmake.org http://cmake.org/ (supposedly the latest stable dmg for mac) was much bigger (30MB) than the cmake file I subsequently downloaded from github. I don't know about that, but I just noticed that cmake.org allows HTTP (non-HTTPS) downloads. HTTP has no form of cryptographic authentication or verification, and it's incredibly easy for a MitM to attach malware to your downloads. IMO, the HTTP downloads should be removed ASAP. signature.asc Description: OpenPGP digital signature -- 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 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-developers
[cmake-developers] [ANNOUNCE] CMake 3.3.0 Release
I am proud to announce that CMake 3.3.0 is now available for download at:
http://www.cmake.org/download/
Documentation is available at:
http://www.cmake.org/cmake/help/v3.3
Release notes appear below and are also published at
http://www.cmake.org/cmake/help/v3.3/release/3.3.html
Some of the more significant features of CMake 3.3 are:
* The if() command learned a new IN_LIST operator that evaluates
to true if a given element is contained in a named list.
* The add_dependencies() command learned to allow dependencies to
be added to *interface libraries*. Dependencies added to an
interface library are followed transitively in its place since the
target itself does not build.
* The find_library(), find_path(), and find_file() commands
now search in installation prefixes derived from the PATH
environment variable.
* The LANG_VISIBILITY_PRESET and VISIBILITY_INLINES_HIDDEN
target properties now affect compilation in sources of all target
types. See policy CMP0063.
* A LANG_INCLUDE_WHAT_YOU_USE target property and supporting
CMAKE_LANG_INCLUDE_WHAT_YOU_USE variable were introduced to tell
the *Makefile Generators* and the Ninja generator to run include-
what-you-use along with the compiler for C and CXX languages.
Deprecated and Removed Features:
* The ctest_build() and build_command() commands no longer tell
make tools to ignore errors with the -i option. Previously this
was done for *Makefile Generators* but not others. See policy
CMP0061.
* The Visual Studio 7 generator (.NET 2002) is now deprecated and
will be removed in a future version of CMake.
* The Visual Studio 6 generator is now deprecated and will be
removed in a future version of CMake.
* The add_definitions() command no longer causes a DEFINITIONS
directory property to be populated. See policy CMP0059.
CMake 3.3 Release Notes
***
Changes made since CMake 3.2 include the following.
New Features
Generators
--
* The *Makefile Generators* now add .DELETE_ON_ERROR to the
makefiles that contain the actual build rules for files on disk.
This tells GNU make to remove rule outputs when their recipe
modifies an output but fails.
* The *Visual Studio Generators* learned to support .xaml source
files and automatically associate them with corresponding .h and
.cpp sources.
* A new experimental Green Hills MULTI generator was added on
Windows. Green Hills MULTI is an IDE for embedded real-time
systems.
Commands
* The add_dependencies() command learned to allow dependencies to
be added to *interface libraries*. Dependencies added to an
interface library are followed transitively in its place since the
target itself does not build.
* The execute_process() command learned to support specifying the
same file for OUTPUT_FILE and ERROR_FILE.
* The file(GLOB) and file(GLOB_RECURSE) commands learned a new
LIST_DIRECTORIES bool option to specify whether the glob result
should include directories.
* The find_library(), find_path(), and find_file() commands
now search in installation prefixes derived from the PATH
environment variable.
* The if() command learned a new IN_LIST operator that evaluates
to true if a given element is contained in a named list.
* The install(EXPORT) and export() commands learned to export
targets that populate the INTERFACE_SOURCES target property.
* The install(TARGETS) command learned to support generator
expressions in the DESTINATION value.
Variables
-
* The version of some Fortran compilers is now detected and stored
in the CMAKE_Fortran_COMPILER_VERSION variable.
* The *Visual Studio Generators* learned a new
CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD option to put the
INSTALL target in the default build of a solution (.sln) file.
Properties
--
* A CROSSCOMPILING_EMULATOR target property and supporting
CMAKE_CROSSCOMPILING_EMULATOR variable were introduced to allow
target platform binaries to run on the host during cross compiling.
* A LANG_INCLUDE_WHAT_YOU_USE target property and supporting
CMAKE_LANG_INCLUDE_WHAT_YOU_USE variable were introduced to tell
the *Makefile Generators* and the Ninja generator to run include-
what-you-use along with the compiler for C and CXX languages.
* The LANG_VISIBILITY_PRESET and VISIBILITY_INLINES_HIDDEN
target properties now affect compilation in sources of all target
types. See policy CMP0063.
* The XCODE_ATTRIBUTE_an-attribute target property learned to
support generator expressions.
Modules
---
* The CheckFortranCompilerFlag module was introduced to check
Fortran compiler flags, much like the CheckCCompilerFlag module
already does for C.
* The ExternalData module learned a new ExternalData_NO_SYMLINKS
option to disable use of symbolic links to populate the real data
files and use copies instead.
* The ExternalData module learned a new RECURSE: option in
DATA{} references
Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015
Hi Ruslan and other developers! 23.07.2015, 16:12, Ruslan Baratov ruslan_bara...@yahoo.com: On 23-Jul-15 12:32, Konstantin Podsvirov wrote: Hi dear CMake developers! Meet modern CMake built on MSVC2015 c QtDialog based on Qt 5.5 from today :-) Windows 32bit: http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe Windows 64bit: http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe As always, questions and suggestions are welcome. -- Regards, Konstantin Podsvirov Both versions can't start because dll is missing: api-ms-win-crt-runtime-l1-1-0.dll Win 7 x64 Ruslan To solve the problem quickly, you need to install Visual C++ Redistributable for Visual Studio 2015 from the link below: http://www.microsoft.com/en-us/download/details.aspx?id=48145 Now more interesting :-) Outdoor platforms may not be Universal CRT: http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducing-the-universal-crt.aspx CMake uses the module InstallRequiredSystemLibraries to install dependencies. Who is in charge here on this module? Should this module to install Universal CRT (api-ms-win-crt-runtime-xxx.dll library) for MSVC14 ? -- Regards, Konstantin Podsvirov -- 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 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-developers
Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015
On 07/23/2015 03:47 PM, Konstantin Podsvirov wrote: http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducing-the-universal-crt.aspx CMake uses the module InstallRequiredSystemLibraries to install dependencies. Who is in charge here on this module? Should this module to install Universal CRT (api-ms-win-crt-runtime-xxx.dll library) for MSVC14 ? 6. App-local deployment of the Universal CRT is not supported. I think that means installation should not be handled by InstallRequiredSystemLibraries. You should probably just require users to run Windows Update. Nils -- 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 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-developers
Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015
On 7/23/2015 10:16 AM, Nils Gladitz wrote: 6. App-local deployment of the Universal CRT is not supported. I think that means installation should not be handled by InstallRequiredSystemLibraries. You should probably just require users to run Windows Update. Yuck! That will be a pain. I think we will stay away from this for a while for the CMake distribution. -Bill -- 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 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-developers
[cmake-developers] [CMake 0015660]: Isssue while installing cmake-curses-gui
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15660 == Reported By:vijay Assigned To: == Project:CMake Issue ID: 15660 Category: CCMake Reproducibility:N/A Severity: minor Priority: immediate Status: new == Date Submitted: 2015-07-23 02:33 EDT Last Modified: 2015-07-23 02:33 EDT == Summary:Isssue while installing cmake-curses-gui Description: I've installed cmake 3.2.2 but when i install cmake-curses-gui, it changes my cmake version to 2.8. I need cmake 3x versions including cmake-curses-gui. Help me == Issue History Date ModifiedUsername FieldChange == 2015-07-23 02:33 vijay New Issue == -- 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 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-developers
Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015
-Original Message- From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of Nils Gladitz On 07/23/2015 03:47 PM, Konstantin Podsvirov wrote: http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducing-the-univ ersal-crt.aspx CMake uses the module InstallRequiredSystemLibraries to install dependencies. Who is in charge here on this module? Should this module to install Universal CRT (api-ms-win-crt-runtime-xxx.dll library) for MSVC14 ? 6. App-local deployment of the Universal CRT is not supported. I think that means installation should not be handled by InstallRequiredSystemLibraries. You should probably just require users to run Windows Update. That sounds horrible - asking a user to manually run Windows Update. But Windows Update packages don't have to be installed ONLY by way of visiting Windows Update manually. I have yet to mess with this stuff myself (but will be soon). But in the meantime, FTA: Currently these MSU packages are installed as part of the VCRedist installation. In a future build of Visual Studio 2015, these MSU packages will also be distributed separately as part of the Universal CRT SDK and made available for download on support.microsoft.com. So you get this just by running VCRedist - or, if you don't use VCRedist, you can get this by running the MSU packages directly (once said SDK becomes available - if it isn't already available - the blog is 4 months old). Both can be accomplished as part of a setup program. Unfortunately, I suspect the MSU packages can't be invoked from / nested inside a Windows Installer MSI like how the VC++ merge modules were done (and how we currently do); I plan to hack apart VCRedist to try to see what they are doing... Best regards, James Johnston -- 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 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-developers
Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015
On 23.07.2015 17:24, James Johnston wrote: That sounds horrible - asking a user to manually run Windows Update. But Windows Update packages don't have to be installed ONLY by way of visiting Windows Update manually. The support issue is certainly cumbersome given that users will be told that some DLL that they haven't heard of before is missing rather than that they need to update an operating system component by running windows update. But this will only be an issue for users which don't run windows = 10 or which don't run regular updates (I'd have assumed this comes in through automated updates as well unless disabled?). Given sufficient time this should therefor become a non-issue. I rather think it is nice that this is considered an operating system component rather than a visual studio version specific runtime component (e.g. reduced application installer sizes and centralized updates) but this might work best if you also treat it as such (unless you specifically have to target e.g. outdated/unnetworked machines). Nils -- 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 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-developers
[cmake-developers] [CMake 0015661]: FindPythonInterp will accept python in the path, even though it is the wrong version
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15661
==
Reported By:Paul TBBle Hampson
Assigned To:
==
Project:CMake
Issue ID: 15661
Category: Modules
Reproducibility:always
Severity: major
Priority: normal
Status: new
==
Date Submitted: 2015-07-24 04:07 AEST
Last Modified: 2015-07-24 04:07 AEST
==
Summary:FindPythonInterp will accept python in the path,
even though it is the wrong version
Description:
The command
FIND_PACKAGE(PythonInterp 2.6 REQUIRED)
will discover a Python 3 installation if that is 'python' in the path, in
preference to a Python 2 installation.
Steps to Reproduce:
Call
FIND_PACKAGE(PythonInterp 2.6 REQUIRED)
in a CMake script, when your PATH contains C:\Python34 but both Python 3.4 and
Python 2.7 are installed locally.
Expected result:
-- Found PythonInterp: C:/Python27/python.exe (found suitable version 2.7.9,
minimum required is 2.6)
Actual result:
-- Found PythonInterp: C:/Python34/python.exe (found suitable version 3.4.3,
minimum required is 2.6)
Additional Information:
I haven't diagnosed this yet, but the problem appears to be the following blocks
in FindPythonInterp.cmake:
=
# Search for the current active python version first
list(APPEND _Python_VERSIONS ;)
list(APPEND _Python_VERSIONS ${_PYTHON_FIND_OTHER_VERSIONS})
# Search for newest python version if python executable isn't found
if(NOT PYTHON_EXECUTABLE)
foreach(_CURRENT_VERSION IN LISTS _Python_VERSIONS)
set(_Python_NAMES python${_CURRENT_VERSION})
if(WIN32)
list(APPEND _Python_NAMES python)
endif()
find_program(PYTHON_EXECUTABLE
NAMES ${_Python_NAMES}
PATHS
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\${_CURRENT_VERSION}\\InstallPath]
)
endforeach()
endif()
=
If I'm reading this correctly, it's possible for _Python_VERSIONS to be empty
before this if neither ADDTIONAL_VERSIONS nor PYTHONLIBS_VERSION_STRING (from
FindPythonLibs.cmake) are set.
This means that when the given loop is hit, the first value of _CURRENT_VERSION
is , so 'python' is searched for by find_program. There's also the
WIN32-specific block that explicitly searches for the executable name 'python',
as that's the name of the executable on Windows installations.
If python.exe is in the Path (a non-default but common installer option) then
the first search attempt will discover it and use it.
It might be simplest to split this search, and on Win32 not search the system
path until the registry walk has completed.
I think there's also a couple of other issues here: A per-user install of Python
sets a different registry key, and we don't fail if Python 2 was requested but
Python 3 is found, or vice-versa.
We also don't support py.exe, which as of Python 3.3 supports running python
scripts with arbitrary versions by processing the #! initial line the same way
an executable .py file is handled on POSIX systems.
==
Issue History
Date ModifiedUsername FieldChange
==
2015-07-24 04:07 Paul TBBle HampsonNew Issue
==
--
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 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-developers
[cmake-developers] [CMake 0015662]: CMake looks in the wrong locations for Windows/Windows Phone SDKs with Visual Studio 2015
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15662 == Reported By:D.E. Goodman-Wilson Assigned To: == Project:CMake Issue ID: 15662 Category: CMake Reproducibility:always Severity: major Priority: urgent Status: new == Date Submitted: 2015-07-23 14:20 EDT Last Modified: 2015-07-23 14:20 EDT == Summary:CMake looks in the wrong locations for Windows/Windows Phone SDKs with Visual Studio 2015 Description: With Visual Studio 2015, the locations of the registry keys for the Windows SDK and WIndows Phone SDK have changed, and so the VS 2015 generator—which relies on the VS 2013 registry settings—generates errors wrongly. Steps to Reproduce: On a freshly installed system with no prior installation of Visual Studio 2013, and a fresh installation of Visual Studio 2015 with Windows SDK 8.1 and Windows Phone SDK 8.1 installed, attempt to cmake a project with set(CMAKE_SYSTEM_NAME WindowsPhone) set(CMAKE_SYSTEM_VERSION 8.1) The following error is generated: -- Building for: Visual Studio 14 2015 CMake Error at CMakeLists.txt:2 (project): A Windows Phone component with CMake requires both the Windows Desktop SDK as well as the Windows Phone '8.1' SDK. Please make sure that you have both installed Additional Information: I can't find the new Windows Phone SDK registry keys, but they are not where cmake is expecting them for sure. The new WIndows SDK is now located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v8.1A\InstallationFolder == Issue History Date ModifiedUsername FieldChange == 2015-07-23 14:20 D.E. Goodman-WilsonNew Issue == -- 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 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-developers
Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015
-Original Message- From: Nils Gladitz [mailto:nilsglad...@gmail.com] On 23.07.2015 17:24, James Johnston wrote: That sounds horrible - asking a user to manually run Windows Update. But Windows Update packages don't have to be installed ONLY by way of visiting Windows Update manually. But this will only be an issue for users which don't run windows = 10 or which don't run regular updates (I'd have assumed this comes in through automated updates as well unless disabled?). Depends on if it is an important update or an optional update... Or it may not show at all. E.g. the legacy WinHelp MSU package is not pushed via Windows Update at all, but if you want WinHelp, it's installed via a manually-downloaded MSU package that you have to get from Microsoft.com downloads. I'm curious to find out which method they choose... I rather think it is nice that this is considered an operating system component rather than a visual studio version specific runtime component (e.g. reduced application installer sizes and centralized updates) but this might work best if you also treat it as such (unless you specifically have to target e.g. outdated/unnetworked machines). To me, this is the worst of both worlds. Not only do we STILL have to distribute the version-specific components (which are not part of the universal CRT) as we always have since VS2005, we now have this MSU package IN ADDITION that has to be installed for every configuration except static runtime linking. You still have the burden of redistributing the rest of the unstable VS2015-specific runtime. So it's not like you can wait 10 years for adoption and stop worrying about any VS2015 redistributing runtime files at all. Bonus points if they find a way in Visual Studio 2020 to modify the universal CRT and somehow cause breaking changes with VS2015, even though they promised not to... This was supposedly why the VS2005 CRT newer are side-by-side installed into winsxs - to fix DLL hell from the 1990s... James -- 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 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-developers
Re: [cmake-developers] [CMake] CTest threshold exceeds 1024 bytes
Hi Brad, i've updated the patch with the missing things, but I don't know how to use the -check.cmake scripts to check the length of the output. Maybe you could have a look at it. Best regards Roman Am 22.07.15 um 17:14 schrieb Brad King On 07/21/2015 06:16 PM, Roman Wüger wrote: I've attached a patch which learns CTest to handle it. I hope this patch could be merged. Good start. Please also update Help/manual/ctest.1.rst with documentation for the new options. Also please extend the test suite, likely in Tests/RunCMake/CTestCommandLine, to cover the options. See Tests/RunCMake/README.rst for information about how the existing test works. You could perhaps add a case that uses a -check.cmake script to verify the length of the output in a Test.xml file after running ctest -M Experimental -T Test plus the new options. Thanks, -Brad 0001-ctest-learned-to-limit-the-output-of-passed-and-fail.patch Description: Binary data -- 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 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-developers
[cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015
Hi dear CMake developers! Meet modern CMake built on MSVC2015 c QtDialog based on Qt 5.5 from today :-) Windows 32bit: http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe Windows 64bit: http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe As always, questions and suggestions are welcome. -- Regards, Konstantin Podsvirov -- 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 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-developers
