[Cmake-commits] CMake branch, master, updated. v3.13.0-rc2-215-g01c6f99

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 635a694..2c106b6 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 13) -set(CMake_VERSION_PATCH 20181028) +set(CMake_VER

Re: [CMake] Removing rpath paths

El 28/10/18 a las 18:32, Alexander Neundorf escribió: well, then you do have some RPATH/RUNPATH somewhere ;-). As you say probably in the libraries. ld.so.conf could also contains additional search directories, but I doubt that that's the case for you. Yes, I found two libraries with rpath

Re: [CMake] Removing rpath paths

On 2018 M10 28, Sun 14:20:40 CET you wrote: > El 28/10/18 a las 13:59, Alexander Neundorf escribió: > > On 2018 M10 28, Sun 10:19:58 CET Gonzalo Garramuño wrote: > > ... > > > >> 3) Why does running 'readelf -d myexecutable | grep RPATH' returns > >> nothing > > > > only grep for "PATH", then

Re: [CMake] Removing rpath paths

El 28/10/18 a las 13:59, Alexander Neundorf escribió: On 2018 M10 28, Sun 10:19:58 CET Gonzalo Garramuño wrote: ... 3) Why does running 'readelf -d myexecutable | grep RPATH' returns nothing only grep for "PATH", then you also get the newer RUNPATH entry. Alex Thanks.  I tried it but it

Re: [CMake] Removing rpath paths

On 2018 M10 28, Sun 10:19:58 CET Gonzalo Garramuño wrote: ... > 3) Why does running 'readelf -d myexecutable | grep RPATH' returns nothing only grep for "PATH", then you also get the newer RUNPATH entry. Alex -- Powered by www.kitware.com Please keep messages on-topic and check the CMake

[CMake] Removing rpath paths

This is probably something very simple, but I cannot find the answer. I would like to remove all references to rpath and have my executable and libraries be controlled by LD_LIBRARY_PATH. According to the wiki, that's the default behavior. However, I am finding it does not work so I set

Re: [CMake] CMake Can't Find Boost.Filesystem in Docker Container

On 28/10/2018 10:26, Osman Zakir wrote: I'm creating a new email thread for this because the other thread's problem was already solved. In the Dockerfile for my project, the build process can't go any farther from the point where I'm trying to build the Jinja2Cpp library.  CMake isn't able

Re: [CMake] CMake Can't Find Boost.Filesystem in Docker Container

On Sun, 28 Oct 2018 at 12:44, Osman Zakir wrote: > > The build does work locally, and I don't get that particular error either. > I'm using Windows 10 Home on my local machine (which also means I have to use > Docker Toolbox with VirtualBox, since the Home edition doesn't have Hyper-V). > I

Re: [CMake] CMake Can't Find Boost.Filesystem in Docker Container

On Sun, 28 Oct 2018 at 11:26, Osman Zakir wrote: > In the Dockerfile for my project, the build process can't go any farther from > the point where I'm trying to build the Jinja2Cpp library. CMake isn't able > to find Boost.Filesystem, but it's still able to build the library and write > the

[CMake] CMake Can't Find Boost.Filesystem in Docker Container

I'm creating a new email thread for this because the other thread's problem was already solved. In the Dockerfile for my project, the build process can't go any farther from the point where I'm trying to build the Jinja2Cpp library. CMake isn't able to find Boost.Filesystem, but it's still

[cmake-developers] PIE flags on various platforms

I'm currently reviewing a merge request that addresses problems with creating PIE executables. Is anyone here sufficiently familiar with Fuchsia, FreeBSD or NetBSD to be able to check whether the right flags are being used there (look at