[CMake] add_test CONFIGURATIONS and linux

Hi, I'm failing to be able to use "run-only-in-release" tests when running under linux (Debian). Below is a short reproduction. CmakeLists.txt = cmake_minimum_required(VERSION 3.0) = CMAKE_BUILD_TYPE=Release. Correct? Doesn't work for me: Run Script ==

[Cmake-commits] CMake branch, next, updated. v3.6.2-1985-g8f24764

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-934-gf51f4ee

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-928-g8a56e31

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-930-g5b85a3e

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-941-g112f758

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1979-g23034b9

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1971-g1836176

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-932-g2fbd309

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-937-g994e98b

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1981-g82c7905

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1987-g579af61

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1993-gd3a223e

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1990-gb129f20

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1998-g154dcb8

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-942-g989ca43

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

[cmake-developers] Downloading file from S3 private bucket

Hi, Currently I'm investigating possibilities of downloading files from private S3 bucket using CMake. The only real issue I see for now is the computing of HMAC + SHA1. This look like a work for some new cryptographic module in family of 'string' functions similar to 'string(MD5|SHA1|...)'.

Re: [cmake-developers] Downloading file from S3 private bucket

On 09/13/2016 07:42 AM, Ruslan Baratov via cmake-developers wrote: > Will it be okay if CMake will optionally depend on OpenSSL? > Or other third party crypto library? Currently the only place that needs it is through `curl`, and that uses either OpenSSL or the Windows-native or macOS-native APIs

Re: [cmake-developers] Downloading file from S3 private bucket

On 13-Sep-16 15:58, Brad King wrote: On 09/13/2016 07:42 AM, Ruslan Baratov via cmake-developers wrote: Will it be okay if CMake will optionally depend on OpenSSL? Or other third party crypto library? Currently the only place that needs it is through `curl`, and that uses either OpenSSL or the

[cmake-developers] Fixing up arbitrary Mac OS bundles

Hello, I'm trying to fixup an embedded bundle which is a QuickLook plugin. The bundle has .qtgenerator extension and should be located in .app/Contents/Library/QuickLook/.qtgenerator. This doesn't work right away. I've tried: 1. fixup_bundle(".app/Contents/Library/QuickLook/.qtgenerator" "" "")