[Cmake-commits] CMake branch, master, updated. v3.7.2-1281-gd5f0c69

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

Re: [CMake] Forcing linking compatability to old libc / libstdc++ (Linux)

FWIW, we've moved to CentOS 6 for the binaries we package and distribute for ParaView. It's about the oldest widely deployed Linux distro that's still actively supported (EL5 is EOL'd and most deployments have long since moved to 6 or 7). it's binaries are compatible with virtually all current

Re: [CMake] COMMAND dependencies with add_custom_command()

Great, thanks. That was a similar case to the example I was using to experiment with this stuff, I just hadn't picked up that if generated.out already existed, it wouldn't be rebuilt if generate.cpp changed. Cheers. On Thu, Feb 2, 2017 at 7:12 AM, Matthew Woehlke

Re: [CMake] Forcing linking compatability to old libc / libstdc++ (Linux)

On 2017 M02 2, Thu 20:07:29 CET you wrote: > Hi Gonzalo, > > Using the dockcross/manylinux-x64 docker image should allow to build you > project out-of-the-box. > It is based on Centos5, include recent gcc, CMake, Git, etc ... > > See https://github.com/dockcross/dockcross > > In a nutshell, >

[CMake] OSX RPATH linker flags not added on first build

Hello, I am using ExternalProject to download and build a third-party library (SDL) in my project. I am running into an issue on OSX where the RPATH linker flags will not be added when my project is built and linked for the first time. As a result the built executable will not have any RPATH

[Cmake-commits] CMake branch, next, updated. v3.7.2-2538-g5d57061

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2535-gf28a0de

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2531-ga792ec4

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2529-g70284f1

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2527-gf010bae

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

[Cmake-commits] CMake branch, master, updated. v3.7.2-1280-gfb26fcb

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2524-gcac9e0b

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2518-gf50c357

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

Re: [CMake] Mac OS. Cmake changes it's behaviout when building framework for iOS simulator

Hello, On 02/02/2017 16:15, Сергей Бойцов wrote: Hello. I'm looking for some help cause i have faced a really strange problem with building frameworks on Mac OS So i have: Mac OS X : el captain Xcode 8.0 CMake 3.3.2 [1], CMake 3.4.5 [2], CMake 3.5-3.6 [3] CMake [1] produced correct

# Santander Brasil S.A - Smiles Gol - Comunicado de expira��o 2017. (54397)

Santander (Brasil) SA www.santander.com.br (4004-3535)      Super Linha Online - Comunicado de expiração Prezado(a) Cliente: Prezado cliente, você possui 207.000 mil

Re: [CMake] fixup_bundle fails for read-only .dylib files

Hello, I have found a reasonable workaround, override the call to fixup_bundle_item (called by fixup_bundle) and mark the file as writable: install(CODE " INCLUDE (BundleUtilities) macro (fixup_bundle_item resolved_embedded_item exepath dirs) message (\"Making writable: