[CMake] cmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory

Trying to build lastest release, to get a preview for 3.12-rc1 that should be released soon. The specific reason is to fix a problem with linking failing due to response files not generated:

Re: [CMake] cmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory

On 06/13/2018 04:22 AM, Gerhard Olsson wrote: > The build works on my PC, but not on the Jenkins server running Windows > Server 2012R2: cmake.exe: error while loading shared libraries: ?: cannot > open shared object file: No such file or directory > > Any steps required to get a binary that runs

Re: [CMake] CMakeLists.txt in different place than source

On Tue, Jun 12, 2018 at 7:22 PM Andrew White wrote: > I have a situation where I want my CMakeLists.txt in a different place > than my source. > > e.g.: > > /some/path/project/CMakeLists.txt > /other/path/source/src/a.c > /other/path/source/include/a.h > > Is there an easy way to say "process

Re: [CMake] CMakeLists.txt in different place than source

J Decker wrote: You can define a variable to define the base of the sources set( SOURCE_ROOT /some/path ) could be set relative to the current cmake path per cmake that uses those souces... and then just prefix it add_library(my_lib ${SOURCE_ROOT}/src/a.c

[CMake] Null alias targets?

I have a library that needs to be built on some platforms but on others is part of the OS. I'd like to avoid putting "if platform" conditional code in the places it is used, but instead hide it away in my platform-specific code. One way to do this is define a variable mylib_targetname in each

[CMake] cmake in MacPorts environment difficulties

I’ve been trying to add the Radiance lighting simulation package to the MacPorts package manager, and I am running into cmake problems. I can build Radiance with cmake from the command line and from the CMake command line app, but when I write a MacPorts to build it, it falls down on install.

[CMake] Refer existing xcode project from cmake project

Hello, I want to add sub project to xcode generated project. I am adding xcodeproj folder as a source file and it looks like the sub project is added correctly to the parent project. But I can not add target dependency from the parent to the sub project target. Parent project is generated from

Re: [CMake] cmake in MacPorts environment difficulties

CMake is looking for .app package and my guess is that the package being built is a "unix" style installation. If your project depends on just MacPorts you should be able to just do "make install" after setting the CMAKE_INSTALL_PREFIX=/opt/local. -- Mike Jackson On 6/13/18, 4:17 PM, "CMake

Re: [CMake] CMakeLists.txt in different place than source

On Wed, Jun 13, 2018 at 9:46 PM Andrew White wrote: > J Decker wrote: > > You can define a variable to define the base of the sources > > set( SOURCE_ROOT /some/path ) > > > > could be set relative to the current cmake path per cmake that uses those > > souces... and then just prefix it > >

Re: [CMake] cmake in MacPorts environment difficulties

That could be. I'll have to see if I can figure a way to get MacPorts to cough up more information about the commands it is issuing; the MacPorts people ought to know. -- Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com On Wed, Jun 13, 2018 at 4:34 PM, Michael Jackson <

Re: [cmake-developers] cmake on AIX

Hi Brad, With cmake 3.2.3 , Séna is able to build MariaDB. However, with version 3.11.1 , we have issues (core or hang of cmake, and other issues). Investigating. We'll move to 3.11.3 asap in order to see if we face the same issues. Cordialement, Tony Reix ATOS / Bull SAS ATOS Expert IBM Coop

Re: [cmake-developers] Using pkgconf

On 06/12/2018 12:11 PM, Paul Fultz II via cmake-developers wrote: > https://github.com/pkgconf/pkgconf > > CMake could use pkgconf internally The license looks MIT-like. Please confirm that it is at least BSD-3 compatible. > find_package(zlib CONF) > > And this would look up zlib using

[Cmake-commits] CMake branch, master, updated. v3.11.3-948-g38e4246

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

[Cmake-commits] CMake branch, master, updated. v3.11.3-964-g9eeed4f

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

[Cmake-commits] CMake branch, release, updated. v3.11.3-935-gef5e2e8

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

[Cmake-commits] CMake branch, master, updated. v3.11.3-965-gb367da7

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 96228d8..2486bdf 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 12) -set(CMake_VERSION_PATCH 20180613) +set(CMake_VER