[Cmake-commits] CMake branch, next, updated. v3.6.1-1708-g5ae80fe

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-831-gcb3e091

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

[cmake-developers] Feature request: file globbing in ADDITIONAL_MAKE_CLEAN_FILES

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, next, updated. v3.6.1-1704-gbaaf490

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1700-ge623fc9

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

[CMake] Error: no cmake_fortran_compiler could be found.

Dear There, This is first time to use CMAKE. I got the error that says "no cmake_fortran_compiler could be found." I use it on Windows 8.1, which have installed Visual Studio Community 2015, Intel FORTRAN Composer XE 2013, and CUDA 7.0. The Fortran compiler identification is unknown

[Cmake-commits] CMake branch, next, updated. v3.6.1-1698-g1ec2259

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1696-gda6f1e4

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1685-ge30f686

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1683-gfc66613

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

Re: [CMake] User-overriding IMPORTED targets (overlaying libraries, ...)

Ivan Shapovalov wrote: > Of course, I can always edit the FooConfig.cmake file manually, but I'd > better avoid patching anything (installing new files or running any > cmake commands is OK). > > Is there any nice way to solve this? After find_package(Foo CONFIG) do set_property(TARGET

Re: [CMake] set_directory_properties ADDITIONAL_MAKE_CLEAN_FILES globbing pattern?

Steve Lorimer wrote: > Is this just not possible? Indeed - this is not possible. Thanks, Steve. -- 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.

Re: [CMake] CMake library installations and pkg-config

01.09.2016, 08:34, "n...@appletonaudio.com" : > On 2016-08-31 23:32, Konstantin Tokarev wrote: >>  31.08.2016, 16:22, "Nick Appleton" : >>>  Hi, >>> >>>  I’ve been recently doing a bit of work for an open source project >>>  trying to extend it’s

[Cmake-commits] CMake branch, next, updated. v3.6.1-1681-g24e158b

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1679-g3ebb968

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

Re: [cmake-developers] QtAutogen: Use Base32 instead of Base64 for file names

On 09/01/2016 07:22 AM, Sebastian Holtermann wrote: > The patches. Thanks, applied with minor tweaks: Add cmBase32Encoder class https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=67dba415 cmFilePathUuid: Use Base32 string instead of Base64 string

[Cmake-commits] CMake branch, next, updated. v3.6.1-1676-g53f189c

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1673-gb93f03c

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-830-g0c46750

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-828-gd7ca93f

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

Re: [cmake-developers] QtAutogen: Use Base32 instead of Base64 for file names

Am 30.08.2016 um 16:53 schrieb Brad King: On 08/28/2016 10:00 AM, Sebastian Holtermann wrote: Base32 is a better choice IMO because it is single case and does not generate disruptive characters like '_', '-' or '/'. Here are two patches that replace Base64 with Base32. Thanks. Please revise

Re: [CMake] CMake library installations and pkg-config

On 2016-08-31 23:32, Konstantin Tokarev wrote: 31.08.2016, 16:22, "Nick Appleton" : Hi, I’ve been recently doing a bit of work for an open source project trying to extend it’s support for CMake. I’ve been trying to get CMake to be able to replicate most of the