[Cmake-commits] CMake branch, master, updated. v3.6.1-717-gd6734ee

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

Re: [cmake-developers] VS Toolchain Support

Did a bit of poking around the CMake codebase to see what a patch might look like. Was thinking something along the lines of this. #ifndef cmVisualStudio10ToolsetOptions_h #define cmVisualStudio10ToolsetOptions_h #include "cmStandardIncludes.h" struct cmIDEFlagTable; /** \class

[Cmake-commits] CMake branch, next, updated. v3.6.1-1419-g9619967

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1417-gd644883

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1415-ga035078

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1413-g0ad6db5

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

[CMake] CPack change file extension

Hey everybody, I try to rename the fileextension of my cpack zip file. So i use cpack -G ZIP to create the package and get my zip file. Now i need to rename these fileextension to another name, like microsoft did it with with docx word format, where the file is a zip file, but has the docx

Re: [cmake-developers] VS Toolchain Support

For a first pass it might be best to just follow what is in cmIDEFlagTable as this would largely be unintrusive and just get the architecture there. That would look like { "library":[ { "name":"ErrorReporting", "command":"ERRORREPORT:PROMPT",

[Cmake-commits] CMake branch, next, updated. v3.6.1-1411-g873ec69

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

Re: [cmake-developers] VS Toolchain Support

Thanks for the response Brad! I would be interested in the JSON format. Do you have any opinions on what that would look like or would you just like to see some implementation before proceding? -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Wednesday, August

Re: [cmake-developers] VS Toolchain Support

On 08/24/2016 02:25 PM, Olmstead, Don wrote: > I would be interested in the JSON format. Do you have any > opinions on what that would look like or would you just > like to see some implementation before proceding? Please propose a sample format. Just take a few entries from one of the existing

[Cmake-commits] CMake branch, next, updated. v3.6.1-1404-g075c74e

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-716-g81c3e63

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1402-g6b3d7f6

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

[CMake] Problems running npm-based tests on Windows

Hi, we are running ctest's on appveyor using npm-installed packages. Specifically, we run jsonlint and ajv on json files to validate the content. Packages are installed in this line: https://github.com/QIICR/dcmqi/blob/master/appveyor.yml#L12-L13 of the appveyor configuration. The installed

[CMake] set_directory_properties ADDITIONAL_MAKE_CLEAN_FILES globbing pattern?

As part of our build process we tag certain binary files with version information such as git branch, number of commits, build variant etc. Eg, for a binary called "app" we could install a file in the local source directory with the name "app.branch_foo.91.debug" The shell globbing pattern that

[Cmake-commits] CMake branch, release, updated. v3.6.1-22-gfc552ce

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1400-g15d79ad

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-714-g86f1d70

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1397-g05a67e9

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

Re: [CMake] trouble with find_package

Hi. In your e-mail, there are curly quotes in the set() command. Is that an artifact of e-mailing, or are they actually present in your code? The latter could indeed cause the error you're seeing. Petr On 24 August 2016 at 17:09, Cotton Candy wrote: > Hi, > Cmake

[CMake] trouble with find_package

Hi, Cmake was having trouble finding the MySQL libraries on my machine so I tried using find_package with a package finder that I downloaded ( https://gist.github.com/RenatoUtsch/1623340) called FindMySQL.cmake. In my CMakeLists.txt file I added: set(CMAKE_MODULE_PATH

[Cmake-commits] CMake branch, next, updated. v3.6.1-1395-gdbd8384

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1393-g89a08c9

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-712-g96de370

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-688-gccddb45

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1390-ge4ad8dc

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-681-g5c8b69b

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-685-g4a2a66e

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-677-g2986ca5

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-679-g1d858dc

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-683-g21a7809

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-674-ga71ca1f

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1381-gbbc5b5c

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1379-gab1846f

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

Re: [cmake-developers] VS Toolchain Support

On 08/23/2016 01:58 PM, Olmstead, Don wrote: > is there any work being done to more accurately create project > files for different toolchains? No one is actively working on it AFAIK. The central tracking issue for this is here: https://gitlab.kitware.com/cmake/cmake/issues/16153 Basically

[CMake] surround executable with flags

Hi, i trying to migrate a cross-compiler project (ARM on Windows) from an IDE (Cypress PSoC Creator) to cmake. The toolchain is a standard gcc for arm. The IDE compiles the binary with arm-none-eabi-gcc.exe -Wl,--start-group . -Wl,--end-group. I'm trying to reach the same in cmake, but

[CMake] surround add_executable with flags

Hi, i trying to migrate a cross-compiler project (ARM on Windows) from an IDE (Cypress PSoC Creator) to cmake. The toolchain is a standard gcc for arm. The IDE compiles the binary with arm-none-eabi-gcc.exe -Wl,--start-group . -Wl,--end-group. I'm trying to reach the same in cmake, but