[Cmake-commits] CMake branch, master, updated. v3.7.2-1198-g83596d4

_VERSION_MINOR 7) -set(CMake_VERSION_PATCH 20170126) +set(CMake_VERSION_PATCH 20170127) #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)

My personal experience is, always create the distribution on old Linux with older compiler to keep the maximal compatibility. Since usually the GCC will pick libstdc++ from system, so if user runs the distribution on even older Linux, 100% sure the error raises. On CentOS/Redhat we do have the

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

I've had to deal with this in the past. For glibc, it's more tricky since when you compile on a newer distribution, it will automatically use the newer version of some symbols. Some functions have had breaking changes and to keep compatibility, they kept all the different version in the

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

> On Jan 26, 2017, at 1:45 PM, Gonzalo Garramuño wrote: > > > > El 26/01/2017 a las 18:35, Michael Ellery escribió: >> In what way is the stdlib incompatible? Does it have bugs, or is this more a >> matter of cpp standard support? > I should have been more clear. Sorry.

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

El 26/01/2017 a las 18:35, Michael Ellery escribió: In what way is the stdlib incompatible? Does it have bugs, or is this more a matter of cpp standard support? I should have been more clear. Sorry. The incompatabilities happen at linker time, with complaints such as: exrstdattr:

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

> On Jan 26, 2017, at 1:23 PM, Gonzalo Garramuño wrote: > > I currently own an Ubuntu Xenial 14.04.1 LTS box in which I do all my work. > I distribute a binary image viewer. However, recently one of my users > tried to run the viewer on a CentOS 7 distro and found out

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

I currently own an Ubuntu Xenial 14.04.1 LTS box in which I do all my work.I distribute a binary image viewer. However, recently one of my users tried to run the viewer on a CentOS 7 distro and found out that that distro libc and libstdc++ are older and incompatible. I would like to

Re: [cmake-developers] What should the behaviour of NUMBER_OF_LOGICAL_CORES be?

Hi, I agree that it should be total number of cores. In addition, cmake_host_system_information() might be extended to provide the number of cores per physical core. This aligns with the information in the XML procuded by CTest: The Site element has the attributes NumberOfLogicalCPU,

[cmake-developers] What should the behaviour of NUMBER_OF_LOGICAL_CORES be?

Hi, This question comes from https://gitlab.kitware.com/cmake/cmake/issues/16594 Currently cmake_host_system_information(RESULT logical QUERY NUMBER_OF_LOGICAL_CORES) is buggy, some parts of the code that implement it assume it refers to the number of cores in the system and some assume it is

[Cmake-commits] CMake branch, next, updated. v3.7.2-2371-g0758c65

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2365-g4b9e085

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

Re: [cmake-developers] Eclipse CDT Managed build

On Thu, Jan 26, 2017 at 11:41:21 -0500, Paul Smith wrote: > IMO the right place for managing relocatable builds is in the > compiler/linker, not in the build tool. This is about making the files CMake writes relocatable, not the resulting binaries. --Ben -- Powered by www.kitware.com Please

Re: [cmake-developers] Eclipse CDT Managed build

IMO the right place for managing relocatable builds is in the compiler/linker, not in the build tool. The compiler/linker should provide options that allow the output to be relocatable regardless of the contents of the command line.  GCC for example has -fdebug-prefix-map that will allow you to

[Cmake-commits] CMake branch, next, updated. v3.7.2-2361-g7c51e93

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

Re: [CMake] externalproject_add and generating sources

> On Jan 26, 2017, at 1:23 AM, David Jobet wrote: > > Hello, > > suppose I want to use protobuf and integrate it in my project with > externalproject_add. (actually, I just have precompiled binaries and libs + > header files, I don't have the full sources) > Once the

[Cmake-commits] CMake branch, next, updated. v3.7.2-2359-g63bba4d

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2357-g1325cfc

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

[Cmake-commits] CMake branch, master, updated. v3.7.2-1193-g4ab35eb

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

[Cmake-commits] CMake branch, master, updated. v3.7.2-1197-gb8db2ed

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

[Cmake-commits] CMake branch, master, updated. v3.7.2-1191-g09cad30

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

[Cmake-commits] CMake branch, master, updated. v3.7.2-1188-g6ee9efa

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2350-g67c2364

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2348-g2a1a1cd

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

Re: [cmake-developers] Eclipse CDT Managed build

Thank you for the warning and support. We would prefer to not maintain a fork, but I have not been able to find any other technology that is suitable. For future reference. The intended use-case is for CMake to act as an engine in an IDE project generator solution similar to the below

Re: [cmake-developers] Eclipse CDT Managed build

On 01/26/2017 05:57 AM, Bøe, Sebastian wrote: > I will investigate relocatable builds, because in spite of this not being > trivial, I think CMake still comes out as the best suited technology for my > use-case. We once had an option to produce relative paths in the build system and it was a

Re: [CMake] externalproject_add and generating sources

You'll also want to build your own project with ExternalProject, and use the DEPENDS option to control build order. This ensures that all dependencies are fully installed before your own project is even configured. The project with all the ExternalProject calls is typically called a superbuild,

Re: [cmake-developers] Eclipse CDT Managed build

I was not aware that this was a non-goal. Thank you for feedback. I am sorry if my use-case sounds foreign, but I can't use cmake server mode, because I can't modify the IDE. I will investigate relocatable builds, because in spite of this not being trivial, I think CMake still comes out as the

Re: [cmake-developers] CMake server-mode aborting

On 01/26/2017 10:45 AM, Tobias Hunger wrote: Hello CMake developers, I have been using Qt Creator extensively with cmake server-mode for a while now and am very happy with the results so far. Once the project is initially configured by cmake it is really nice. Today I started to look into a

[cmake-developers] CMake server-mode aborting

Hello CMake developers, I have been using Qt Creator extensively with cmake server-mode for a while now and am very happy with the results so far. Once the project is initially configured by cmake it is really nice. Today I started to look into a bug report that creator behaves horribly when not

Re: [CMake] Generate a file with a custom command as part of build

I'll have a play with that later. Thanks again for all your help. Doug. On 25 January 2017 at 16:02, Michael Ellery wrote: > > > On Jan 24, 2017, at 11:22 PM, doug livesey wrote: > > > > Is there any way that I can make the files webpack compiles

[CMake] externalproject_add and generating sources

Hello, suppose I want to use protobuf and integrate it in my project with externalproject_add. (actually, I just have precompiled binaries and libs + header files, I don't have the full sources) Once the project has been 'built' (actually, installed by a custom rpm-like tool to a shared path),

[CMake] Re : Re: Interfacing cmake with 3rdparties package manager, and exclude them from ninja clean

Hello, I actually gave it a try : it works fine so long versions are hardcoded somewhere in the CMakeLists.txt and it make things really simpler. But it does not work when version is extracted from git repository. I came to realize I can extract this version number at build time (using