[cmake-developers] Should try_run have a timeout value? [demo CMakeLists.txt in body of email]

# # CMakeLists.txt # # PROBLEM: # # This file demonstrates a problem with CMake 3.0 and Visual Studio # compiler x64 builds... If configured for a build with the x64 # compiler, CMake will hang until user intervention with a # cmTryCompileExec123...789.exe has stopped working # crash dialog. # #

Re: [cmake-developers] Should try_run have a timeout value?

On 06/12/2014 08:59 AM, David Cole wrote: # Should try_run have a timeout value, defaulting to a few seconds (or # something more reasonable than NEVER) or is there a way for CMake to # detect this condition and kill it as an unsuccessful try_run...? # cmake_minimum_required(VERSION

Re: [cmake-developers] Should try_run have a timeout value? [demo CMakeLists.txt in body of email]

Would you also be satisfied if the crash dialog was disabled in the try_run()? That is done for ctest by cmCTest::BlockTestErrorDiagnostics(). Sure, as long as the try_run doesn't hang, and indicates failed run in the run result. I'm easy. D -- Powered by www.kitware.com Please keep

Re: [cmake-developers] Should try_run have a timeout value?

Nice literate programming! Thank you. -- 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

[cmake-developers] [CMake 0014970]: [RFE] Add support for linking object libraries

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14970 == Reported By:Ben Boeckel Assigned To:

[cmake-developers] [CMake 0014971]: FindCUDA causes error with default Clang installation on OSX 10.9.3 (w/patch)

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14971 == Reported By:Adam Strzelecki Assigned To:

[cmake-developers] [CMake 0014972]: Ninja gen generates invalid phony dependencies for source files with in-source build

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14972 == Reported By:Adam Strzelecki Assigned To:

[cmake-developers] [CMake 0014973]: [RFE] Produce shorted output for cmake/ccmake when no arguments specified

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14973 == Reported By:Adam Strzelecki Assigned To:

Re: [CMake] Why simple `cmake` does not launch default generator on current directory?

Because that would create an in-source build, and you almost never want that. One wants to build out of source. Sadly CMake will stumble if you try to create an out-of-source build from a directory that is an in-source build, so not having that default of cmake . actually saves everyone a

Re: [CMake] Feature Request: CMAKE_GENERATOR environment variable for default generator

If you *really* wanna save on typing: alias c=''\''C:/Program Files (x86)/CMake/bin/cmake.exe'\'' -G Ninja' (or the equivalent on your machine...) :-) -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware

Re: [CMake] Feature Request: CMAKE_GENERATOR environment variable for default generator

alias c=''\''C:/Program Files (x86)/CMake/bin/cmake.exe'\'' -G Ninja' Aliasing is kind of solution I use now, since cmake allows -G specified twice. But IMHO environment variable would be nice addition. Btw. not using Windows here ;) Cheers, -- Adam -- Powered by www.kitware.com Please

Re: [CMake] Why simple `cmake` does not launch default generator on current directory?

2014-06-12 12:18 GMT+02:00 Adam Strzelecki o...@java.pl: Because that would create an in-source build, and you almost never want that. One wants to build out of source. Sadly CMake will stumble if you try to create an out-of-source build from a directory that is an in-source build, so not

Re: [CMake] Why is target is not added to default built in Visual Studio?

On 06/11/2014 06:55 PM, Dirk Steenpass wrote: I attach a zipfile to demonstrate my problem. Thank you both for the examples. I've fixed the problem and added a test case: VS: Move VS-only API out of cmGlobalGenerator http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5fba44cf VS: Fix

[CMake] Cmake 3.0 can't break with ctrl-c

I cannot stop my visual studio command line builds with ctrl-C anymore... previously BUILD_COMMAND() would return (msbuild in my case cause I overrode it) but I was able to hit ctrl-C to stop the build; now only ctrl-break works... should check the break handler for cmake... since now it returns

[CMake] Selecing make tool

How do I tell cmake to use 'msbuild' instead of 'devenv' as the build tool? Early in my scripts I used to do this bit # set REAL_CMAKE_PROGRAM to what's in registry for msbuild set( CMAKE_MAKE_PROGRAM ${REAL_CMAKE_MAKE_PROGRAM} ) Do Not use devenv as a side effect for building, it

Re: [CMake] Selecing make tool

Okay my complaint was an issue of upgrading without deleting cmakecache.txt... my android projects had an issue because of a new variable for platform=windows in cmakefiles/3.0.0 that didn't get set correctly because again I didn't delete cmakecache On Thu, Jun 12, 2014 at 7:35 PM, J Decker

[CMake] full path to cmakelists.txt

CMake Error at CMakeLists.txt:23 (INSTALL_SACK_BINARY): Unknown CMake command INSTALL_SACK_BINARY. which cmakelists.txt? i have a lot that use that macro that it does exist in -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] install(QUIET ...)

Did this make it to 3.0 release? Could it have been implemented as more of a global flag so I don't have to modify every single install() I have? On Thu, May 15, 2014 at 6:07 AM, Emmanuel Blot eblot...@gmail.com wrote: Too bad it did not make it to RC3... This is a really nice feature.

[Cmake-commits] CMake branch, next, updated. v3.0.0-3689-ge0eb758

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via e0eb7588e7290f3a806f23d99900e481559d7d6a (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-1118-g031ee74

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 031ee74a63d98a4e21ba47eeb67ccd0b642b6daf (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-3697-g7f74f79

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 7f74f79890c3044f0332678f8c4a0deb22692906 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-3700-g015fe82

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 015fe828a71558e8369b661d4a0865884bef0de4 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.0-3706-g4276648

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 4276648a2e50e4e3b977c875108dcdfe7252f496 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.0-1121-gba36363

20140612) +set(CMake_VERSION_PATCH 20140613) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake