Re: [CMake] Benchmarking with CMake

On Monday, November 09, 2015 23:21:58 Nagy-Egri Máté Ferenc via CMake wrote: > Hi! > > Can anyone tell me if CMake (or CTest) can be customized in a way to produce > decent benchmark output? An .xlsx perhaps, or something GnuPlot friendly? I > have not found any examples of CTest being

[CMake] Custom message if target fails

Dear all, i've been thinking on this for a while but i can't seem to get my head around how to solve this. The task is simple: How can i display a custom error message if a target fails to build for whatever reason? - cmake .. - make - - below the (compile-tool dependent error output) i'd

Re: [CMake] Custom message if target fails

Hey, neat idea, i've tried and it works (i have custom targets there). However, the "nice" colored build text output of such a solution gets lost completely (pipes etc); are there any alternative ideas/solutions? thanks again! Dr. Daniel Wirtz Dipl. Math. Dipl. Inf. SRC SimTech

Re: [CMake] Configuration dependent link

Hey all, I have a few more findings about this before I finally give up and resort my old self made approach: It looks to me like the imported target mechanism is not propagating properties the way it could and probably should. Es specially not like it is described here:

Re: [CMake] Custom message if target fails

On 11/12/2015 09:54 AM, Daniel Wirtz wrote: Dear all, i've been thinking on this for a while but i can't seem to get my head around how to solve this. The task is simple: How can i display a custom error message if a target fails to build for whatever reason? - cmake .. - make - - below the

[CMake] Porting to CMAKE and utilizing the CPack

I have managed to port my SW to CMake fine, but now I'm running into issues with the CPack package generation (debian packages for now). I'm using the "dh_" commands in the package generation for debian. What would be the equivalent in CMake? In particular, installing cron scripts, init.d

Re: [CMake] Porting to CMAKE and utilizing the CPack

Installing arbitrary files is accomplished by adding install commands into your CMakeLists. The documentation for the command is here: https://cmake.org/cmake/help/v3.3/command/install.html For something like an init script or systemd unit file they are going to live outside the normal

Re: [CMake] SuperProject package/install

[rm] Right now, the Main ExternalProject_add INSTALL_COMMAND is "". How can I change this (or add another step) to build the package target (I don't want to just hard-code make package, as it should work with MSVC too). I've tried things like '${CMAKE_COMMAND} cmake--build package' but

Re: [CMake] Custom message if target fails

I'm assuming this is under a Unix platform - in my experience, on Windows, I get the color escape codes even running cmake builds under Jenkins. On Unix platforms, you could install expect and use the unbuffer tool, e.g. "unbuffer make -j8 -k". -- Daniel Schepler

Re: [CMake] SuperProject package/install

On 2015-11-11 11:04-0800 Rob McDonald wrote: Right now, the Main ExternalProject_add INSTALL_COMMAND is "". How can I change this (or add another step) to build the package target (I don't want to just hard-code make package, as it should work with MSVC too). I've tried things like

[CMake] [ANNOUNCE] CMake 3.4.0 Released

I am proud to announce that CMake 3.4.0 is now available for download at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.4 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.4/release/3.4.html Some of the more

[Cmake-commits] CMake branch, next, updated. v3.4.0-1332-g3597b37

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 3597b371f980b961baaec9990c70902ec27d0dea (commit) via

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

> * The "CPackDeb" module now correctly excludes symlinks during package checksum calculation. > * The "CPackDeb" no longer uses fakeroot and system tar program for packaging. Does this mean that the ubuntu package manager will stop complaining of CPack DEBs ? Thanks for the great work :)

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

12.11.2015, 21:57, "Robert Maynard" : > I am proud to announce that CMake 3.4.0 is now available for download at: > https://cmake.org/download/ > > Documentation is available at: > https://cmake.org/cmake/help/v3.4 > > Release notes appear below and are also published

Re: [cmake-developers] [PATCH] iOS Framework Bundle support

Hello. With this tiny little patch, the correct directory structure for iOS Frameworks is created. The changes are backward compatible (it is not touching OS X at all, only iOS Frameworks). The risk of regression is very low, as the change is for iOS frameworks, and officially CMake 3.4 do

[Cmake-commits] CMake branch, next, updated. v3.4.0-1326-gf3deee3

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 f3deee39e482cbc898f78d52c261ff9e1137ee7a (commit) via

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

Meet the fresh update online installers (CMake3.4.20151113): http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe and http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe If you have used them previously, then just update via "CMake Maintenance Tool". 12.11.2015, 23:55,

[Cmake-commits] CMake branch, release, updated. v3.4.0-rc3-2-gbab8f83

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, release has been updated via bab8f83cac33df3f48da178076fe3668dd222648 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc3-512-g16efed6

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 16efed6af970796a3a7d4071e8a802f223ae7034 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1320-g9274cfb

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 9274cfb8630c96c2aacebc6252d5c7d7596ca35b (commit) via

[cmake-developers] [CMake 0015845]: CMake fails to identify the Cray compilers' version numbers

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15845 == Reported By:Damian Rouson Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1317-g8813a3a

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 8813a3a6913690eaad76fe7486efc1819b5ba113 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc3-510-g8f8f9e2

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 8f8f9e216eea962f9b7c978ccd37f3c87fbe09e2 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1323-gf8a917d

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 f8a917d886a41d5fbc2c734db8b078eebce1f33d (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-512-g415863e

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20151112) +set(CMake_VERSION_PATCH 20151113) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc3-1325-g0110ad2

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 0110ad290e5796cc8c511f48939b9f79f67cc653 (commit) via

[cmake-developers] XCode Unit Test Bundle targets support

Hi all, In XCode we can add a target of type "Test", specifically for us is the "iOS Unit Test Bundle" that is interesting, because with it we can write iOS test cases that will install, launch and close the app on the iOS device. Does CMake has started to support any of this yet? And if no,

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc3-514-g7387f06

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 7387f06586f0b01dd3c1c4f66339c89f2e985e82 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.4.0-rc3-3-gb4a2ada

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, release has been updated via b4a2ada297214119647b26df8abe394cd73ca53a (commit) from

[cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

I am proud to announce that CMake 3.4.0 is now available for download at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.4 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.4/release/3.4.html Some of the more

[Cmake-commits] CMake annotated tag, v3.4.0, created. v3.4.0

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 annotated tag, v3.4.0 has been created at f6d18315c0033a3438e5b1c6ccee87f4d0128d30 (tag) tagging