Re: [CMake] Running test who have two labels?

On 03/24/2017 11:50 AM, Eric Noulard wrote: Hi there, I'm playing with ctest LABELS and I wanted to know whether if it is possible to run the set of tests which have 2 labels ? I manage to have all tests which have **either** L1 or L2: ctest -L "L1|L2" but how can I write a proper command

[CMake] Running test who have two labels?

Hi there, I'm playing with ctest LABELS and I wanted to know whether if it is possible to run the set of tests which have 2 labels ? I manage to have all tests which have **either** L1 or L2: ctest -L "L1|L2" but how can I write a proper command line for both L1 and L2 ? apparently ctest -L

Re: [CMake] Running test who have two labels?

2017-03-24 12:30 GMT+01:00 Nils Gladitz : > On 03/24/2017 11:50 AM, Eric Noulard wrote: > > Hi there, >> >> I'm playing with ctest LABELS and I wanted to know whether if it is >> possible >> to run the set of tests which have 2 labels ? >> >> I manage to have all tests

Re: [CMake] VS Code generator?

On 03/24/2017 02:04 PM, Eric Noulard wrote: Is there any plan to create/support a VS Code (https://code.visualstudio.com/) generator? Since Visual Studio Code seems to be able to open Visual Studio Solution is it possible to have a working Visual Studio Generator on Linux? Any

[CMake] Is it possible to run ctest outside build tree?

Is possible to run ctest outside the builld tree and how? typical use is when I have an out of source build I may be in the source tree and want to run tests without manually going to build tree. i.e. I currently do: ninja -C /my/build/tree is there a similar way to do that with ctest (other

[CMake] VS Code generator?

Is there any plan to create/support a VS Code ( https://code.visualstudio.com/) generator? Since Visual Studio Code seems to be able to open Visual Studio Solution is it possible to have a working Visual Studio Generator on Linux? Any information/experience about using VS Code with CMake on

Re: [CMake] Is it possible to run ctest outside build tree?

This code: https://github.com/Kitware/CMake/blob/master/Source/ctest.cxx#L139-L157 shows ctest will look for a CTestTestfile.cmake or DartTestfile.txt file in the current working directory as soon as it starts. Except in the case of processing a "--launch" directive, in which case, it dispatches

[CMake] [ANNOUNCE] CMake 3.8.0-rc3 now ready for testing!

I am proud to announce the third CMake 3.8 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.8 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.8/release/3.8.html Some of the more significant

Re: [CMake] Running test who have two labels?

Here's a bash script wrapper you could use with existing ctest. Save it out to a file named ctest-two-labels.sh and then call it with bash on Mac or Linux: label1=$1 label2=$2 if [ -z "$label1" ]; then echo "script takes two label arguments as input, missing arg 1" exit 1 fi if [ -z

Re: [CMake] Is it possible to run ctest outside build tree?

Hi David, Thank you for you for checking the code. Would you think adding such a command line option would be acceptable upstream? Le 24 mars 2017 18:43, "David Cole" a écrit : This code: https://github.com/Kitware/CMake/blob/master/Source/ctest.cxx#L139-L157 shows ctest will

Re: [CMake] Is it possible to run ctest outside build tree?

If the implementation is "run ctest in this build tree" and it effectively simply does a "pushd $build_tree", runs, and then "popd", then I don't see why anybody would object to it. Although, a script wrapper would be completely trivial, and work with existing ctest. D On Fri, Mar 24, 2017

[CMake] How to exclude linking from add_subdirectory?

In my cmake project, there are some subdirectories within it, and some of them have to build as completed static or shared libraries. 1. The top project is executable 2. a subdirectory is a shared project, which also have some subdirectoy compile as static libraries which of course should

Re: [CMake] VS Code generator?

I agree and not at the same time. CMake Tools is an awesome extension, but C++ development in VS Code still feel second rate due to the fact, that the C++ language services extension (most notably the Microsoft extension) does not know about CMake Tools and one manually has to populate

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-615-g4435678

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 discards 929352a82ef95a79f7e640595f3c697df49d4f46 (commit) discards

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-615-g8047bd6

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 discards 13908eae4145346aff2b324e048d6235b06a02c1 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-615-g8047bd6

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-603-g8b25d8e

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-615-g13908ea

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 discards 443567831b85ea57f1e44034892bcd8befd27e1f (commit) discards

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc2-58-g1adbe22

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-618-g09a80c4

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-618-g09a80c4

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

[cmake-developers] [ANNOUNCE] CMake 3.8.0-rc3 now ready for testing!

I am proud to announce the third CMake 3.8 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.8 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.8/release/3.8.html Some of the more significant

[cmake-developers] Build multiple CMake projects

Hi, I have some CMake projects which depend on each other. They provide Config scripts (all generated with the help of CMakePackageConfigHelpers) and the CMake projects find there dependencies with find_package(). Even the transitive dependencies are correctly modelled (exported to the Config

Banco Bradesco S/A - Informamos que seu Cart�o de Chaves de Seguran�a encontra-se expirado. (62650)

Title: Pra Min Prezado Cliente, Prezado (a) Cliente: Informamos que seu Cartão de Chaves de Segurança encontra-se expirado, e por medidas de segurança deve ser reativado, deste modo não ocorrendo o problema de bloqueio aos

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-570-g30b22d9

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-573-g85994c6

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 discards 6d5ad4da359624a3ee5fa5dfcc3c19879f90efc3 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-564-g3ac205f

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 3ac205f7dcbb0e0b0aa058cc9b8d84f0318d02d5 (commit) from

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc3-572-g6d5ad4d

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, nightly has been updated discards 47ea9a8f3927ad605729400e812ca52560f9265f (commit) discards

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc3-563-g3142808

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, nightly-master has been updated via 3142808f15b0dabca8a5d66535c3f795ed470bac (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-572-g6d5ad4d

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-620-g97662ba

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-624-g6f245c2

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 discards 634707f0e558e577a0a2601e56ebf95dda6b4a7f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc2-622-g3142808

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

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc2-59-g3b7f19a

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 3b7f19a72ff2216b4613fdc8c5edf5d56e74d6fc (commit) from

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

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.8.0-rc3 has been created at a1c43dfcf00c97d3517582cd3fd3f94cc22a38c4 (tag) tagging

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-623-ge4d9bb3

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-622-g634707f

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 discards e4d9bb37952ea16d6703979832e8c865c0763fd8 (commit) discards