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

2017-02-03 Thread Chuck Atkins
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 Li

Re: [CMake] COMMAND dependencies with add_custom_command()

2017-02-03 Thread Craig Scott
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 wrote: > On 2017-01-25 20:25, Cr

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

2017-02-03 Thread Alexander Neundorf
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

2017-02-03 Thread Doug Digglington
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 paths

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

2017-02-03 Thread Gregor Jasny via CMake
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 framework

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

2017-02-03 Thread Neil Williams
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: \${resolv