Re: [CMake] Custom installation of cmake

Hi Mahmood, Did you try typing "./bootstrap --help"? Perhaps something there is what you need? Ray On Sun, Oct 20, 2019 at 2:19 AM Mahmood Naderan via CMake wrote: > > OK and how about custom installation path of cmake? > > > Regards, > Mahmood -- Powered by www.kitware.com Please keep

[cmake-developers] [ANNOUNCE] CMake 3.16.0-rc2 is ready for testing

I am proud to announce the second CMake 3.16 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.16 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.16/release/3.16.html Some of the more

[CMake] [ANNOUNCE] CMake 3.16.0-rc2 is ready for testing

I am proud to announce the second CMake 3.16 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.16 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.16/release/3.16.html Some of the more

[CMake] Policy Stack within Macros/Functions

Hey everyone, I’m shipping a config file for my library and inside I set push/pop specific policies so that me and the consumers of my library can target different policies without us clashing against each other. However I’m struggling with |cmake_policy(PUSH)|/|cmake_policy(POP)| once they are

Re: [CMake] Custom installation of cmake

The easiest way is to specify the custom compiler via the CC and CXX environment variables. On Sat, Oct 19, 2019 at 2:19 PM Mahmood Naderan via CMake wrote: > > OK and how about custom installation path of cmake? > > > Regards, > Mahmood > > > On Saturday, October 19, 2019, 4:44:28 PM GMT+3:30,

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-88-g41854d608b

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 41854d608ba2c76f81a1488a6156606232184a5f (commit) from

Re: [CMake] Custom installation of cmake

OK and how about custom installation path of cmake? Regards, Mahmood On Saturday, October 19, 2019, 4:44:28 PM GMT+3:30, 15 knots wrote: What worked for me, is to add 'ools/gcc-7.1.0/bin/' in front of the PATh environment variable for the time cmake is invoked. E.g from bash.

[CMake] Custom installation of cmake

Hi I would like to compile cmake source with a non default gcc version. That is, I have built gcc in my home$ ls tools/gcc-7.1.0/bin/ c++ gcc-ar gcov-dumpx86_64-pc-linux-gnu-gcc x86_64-pc-linux-gnu-gcc-ranlib cpp gcc-nm gcov-tool

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-87-g0671f71d70

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 0671f71d70db238b35c7cd64296e0b9f3a5e68a9 (commit) from

Re: [CMake] CMake link order

Hello, I have always used all of the libraries at once to the TARGET_LINK_LIBRARIES command. In the following example, the link line order appears the same as the libraries are listed on the line. TARGET_LINK_LIBRARIES(devsim_tcl ${LIBRARIES} ${TCL_ARCHIVE} ${SUPERLU_ARCHIVE} ${BLAS_ARCHIVE}

Re: [CMake] CMake link order

Hey all, I face a similar problem when constructing a correct (and predictable) link order for Linux and Cygwin. It would be of great help, if there is some documentation. In particular, I would raise two question     1) when does the link order change?     2) when does a clean up happen and in

Re: [CMake] CMake link order

On Fri, Oct 18, 2019, at 11:55 AM, Fred Baksik wrote: > > In target_link_libraries it states that "The library dependency graph is > normally acyclic (a DAG)". I recall from my own experience that the DAG is > not always created the same way when generating the project. It has to do > with

Re: [CMake] CMake link order

On Fri, Oct 18, 2019, at 6:24 AM, Bon, William wrote: > Hello, > > we are facing an issue while using cmake and we have no idea how to solve or > debug it. > We have a complex and huge project (about 50 subdirectories and dependencies > everywhere), and we are facing issue regarding the link

[CMake] CMake link order

Hello, we are facing an issue while using cmake and we have no idea how to solve or debug it. We have a complex and huge project (about 50 subdirectories and dependencies everywhere), and we are facing issue regarding the link order. There is a lot of dependencies between those projects, and to

[Cmake-commits] CMake annotated tag, v3.16.0-rc2, created. v3.16.0-rc2

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 annotated tag, v3.16.0-rc2 has been created at 371dbf3c152a397447bfae8ddff298b64b01b83b (tag) tagging

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-49-g92780281c2

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 92780281c2e8a46223b262b152caa9c8329373b1 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-135-g493c4e781a

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

[CMake] setting rpath in executable in build directory

Hello, I have the following scenario. I have gcc 9.2.0 and boost 1.71.0 installed in /opt/ZS/deps/... directory, built for both arm and x86_64. I can build programs using them just fine and they run as expected provided -Wl,-rpaht,/opt/ZS/deps... is added to g++ command line. Now I'm trying to

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-133-gfdb41a5102

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-48-g6dedb97420

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-126-gc867981c9d

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

Re: [CMake] Help request for hierarchical directory example

Hi Eric Thanks very much for your answer. I understand now. David On Fri, Oct 18, 2019 at 12:57 PM Eric Noulard wrote: > > > Le ven. 18 oct. 2019 à 12:53, David Aldrich > a écrit : > >> Hi >> >> >> >> I'm learning how to use hierarchical directories in CMake and am trying >> to get an

Re: [CMake] Help request for hierarchical directory example

Le ven. 18 oct. 2019 à 12:53, David Aldrich a écrit : > Hi > > > > I'm learning how to use hierarchical directories in CMake and am trying to > get an example to work that I saw on YouTube. The example isn't doing what > I expect so I would be grateful for some help in understanding why. > > > >

[CMake] Help request for hierarchical directory example

Hi I'm learning how to use hierarchical directories in CMake and am trying to get an example to work that I saw on YouTube. The example isn't doing what I expect so I would be grateful for some help in understanding why. I am running CMake 3.10.2 on Ubuntu 18.04 (Microsoft WSL) and using

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-121-g154aa87ca6

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 154aa87ca6bd906b6422ad81f51161995c89cc14 (commit) from

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-45-g7aab792716

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-120-gf6dac38c11

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-113-gea048ed66c

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

Re: [CMake] error executing script with cmake -P

On Thu, Oct 17, 2019 at 2:14 AM Edoardo Pasca wrote: > Hi Tom, > > I thought ${testdata} was going to be filled in by the actual > patch_script.cmake at this line. > > file (STRINGS TestData.py testdata NEWLINE_CONSUME) > Sorry, some nasty formatting in my email client had me misreading your

Re: [CMake] error executing script with cmake -P

Hi Tom, I thought ${testdata} was going to be filled in by the actual patch_script.cmake at this line. file (STRINGS TestData.py testdata NEWLINE_CONSUME) So it appears that this command doesn't quite work. I'll try also Alan's suggestion. Thanks Edo On Tue, Oct 15, 2019 at 7:00 PM Tom

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-109-g095fc6d9d9

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 095fc6d9d96bf9f12770f85ebf0b75d384a7d5fb (commit) from

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-41-gc2a7729

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-108-ge60412b

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

Re: [cmake-developers] CTest load balancing

On 10/16/19 10:05 AM, Wouter Klouwen wrote: > Is the intent for CTest to specifically manage CPU load or system load > overall? I don't think a careful distinction was made at the time. If Linux needs some updates to be consistent with other platforms then that would be fine with me. -Brad --

[cmake-developers] CTest load balancing

Hi all, CTest has a very useful feature that performs load balancing. This works by comparing the current system load to a target load. The current implementation defers to SystemInformationImplementation::GetLoadAverage() to return a value. This is implemented on the platforms that have

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-104-g96a93a7

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-39-g3658f44

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-99-g0e5a3ae

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

Re: [CMake] using `install()` with EXPORT and COMPONENT

On Mon, Sep 30, 2019 at 4:09 AM Stefan Seefeld wrote: > Hi Craig, > > thanks for the detailed explanation ! > On 2019-09-29 5:13 a.m., Craig Scott wrote: > > > If all of your headers should be installed to a single directory, then you > can list the headers in the target's PUBLIC_HEADER or

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-88-g220d599

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 220d5995076f794e222c882963fb634169a6600b (commit) from

Re: [CMake] error executing script with cmake -P

On 2019-10-14 12:00+0100 Edoardo Pasca wrote: Dear all, I am using external project. I would like to patch a source file. I came out with a cmake script that does the string replacement I'm interested in. I tested in a standalone project, with the following CMakeLists.txt

Re: [CMake] error executing script with cmake -P

It looks like you aren't passing the $testdata variable down to the script. >From your message it looks like you need to add the following to your PATCH_COMMAND: -Dtestdata=${testdata} You must explicitly pass $testdata (and any other variables defined in the calling script) to

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-87-g6050951

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-30-g4041f6a

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

Re: [CMake] Can I use a *Targets-someName.cmake file to get access to _IMPORT_PREFIX ?

TL;DR: - For a project thing I get thingTargets.cmake when I install EXPORT it - thingTargets.cmake sets _IMPORT_PREFIX - thingTargets.cmake loads files thingTargets-*.cmake Can I create and install thingTargets-someName.cmake which uses _IMPORT_PREFIX to "hook" into above mechanism? Or is

Re: [CMake] CMake 3.15 fails to install on OS X

System Integrity Protection (SIP, introduced with macOS 10.11) prevents you from writing into various system directories (like /usr) even as the root user. You can either install cmake to a different location (like /usr/local, which apparently is not protected), or disable SIP entirely (which

[CMake] CMake 3.15 fails to install on OS X

I'm building CMake cmake-3.15.4.tar.gz on OS X 10.12. The machine is stripped down, and only has the COmmand Line tools. No Xcode and friends. I configured with: ./configure --prefix=/usr Configure appears OK. Make appears OK. Install is failing: $ sudo make install VERBOSE=1 ...

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-77-gdaf6a6b

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 daf6a6ba68a6fa1c5d1956f151104d903f3447cc (commit) from

[CMake] Mac Xcode 11 Generator bug/problem with CODE_SIGN_IDENTITY default

I hit a problem with the CMake/Xcode Generator using Xcode 11. (I think this problem started in Xcode 10 actually, but now I'm blocked really hard and need to solve this.) By default, Xcode is now trying to do "Sign to run locally" for the Code Signing Identity (CODE_SIGN_IDENTITY) property, by

[CMake] Sending you config file of an unknown system Platform/MINGW64_NT-10.0-17763

If it makes sense one could add mingw platform so next time cmake won't speak warnings # This is the CMakeCache file. # For build in directory: /home/user/project/blatt-1-aufgabe-3-tendermonster/build # It was generated by CMake: /usr/bin/cmake.exe # You can edit this file to change values found

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

On 2019-10-13 17:15-0400 Paul Smith wrote: A unity source file can lump together N real source files from the same target (library/executable) as long as those files don't have extra source-specific flags, because all other files in a given target have the same flags. I agree that it is not

Re: [CMake] How to make a hierarchical application using CMake?

In the build directory, the build rules are generally like the would be in the source too... so you can just go into src/libwhatever and do 'make' in that branch. like if your target was visual studio or some IDE, you could click on a single project to build, and it would of course check and

Re: [CMake] How to make a hierarchical application using CMake?

On Mon, Oct 14, 2019, at 9:13 AM, David Aldrich wrote: > Hi > > I am trying to convert a large software project from makefiles to CMake. The > project is organised as a set of shared ‘star’ libraries, linked to a static > ‘kernel’ library. The current directory arrangement is: > >

[CMake] How to make a hierarchical application using CMake?

Hi I am trying to convert a large software project from makefiles to CMake. The project is organised as a set of shared ‘star’ libraries, linked to a static ‘kernel’ library. The current directory arrangement is: |--stars | |-- star1_lib | |-- source files |

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

Hi Paul, As another reference point, I verified that -DCMAKE_UNITY_BUILD=ON works with the VTK-m ( https://gitlab.kitware.com/vtk/vtk-m ) project. I only verified using a clean CMake 3.16 build directory. On Thu, Oct 10, 2019 at 6:43 PM Paul Smith wrote: > > On Thu, 2019-10-10 at 14:57 -0400,

[CMake] error executing script with cmake -P

Dear all, I am using external project. I would like to patch a source file. I came out with a cmake script that does the string replacement I'm interested in. I tested in a standalone project, with the following CMakeLists.txt cmake_minimum_required(VERSION 3.4) project(patching_string) file

[CMake] finding cdk

Hi, I have got some problems finding cdk lib in my debian system I used find_library without success libcdk can be found in /usr/lib/x86_64-linux-gnu/ and cdk in include system path cdk/cdk.h Regards, S.Ancelot -- Powered by www.kitware.com Please keep messages on-topic and check the

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-76-g30f0319

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 30f0319e7f11f299cbe113b2c4db9f9c9a6ea21c (commit) from

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

On Sat, 2019-10-12 at 19:25 -0700, Alan W. Irwin wrote: > > Virtually all my properties are set on a per-target basis, so I assumed > > they wouldn't be an issue here. > > > > Am I misunderstanding that? > > I think the current documentation is ambiguous about this. But > certain target and

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-75-g25eef45

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-69-g001a1d2

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 001a1d2686243698527d59a9e5d00287a259 (commit) from

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

On 2019-10-12 15:40-0400 Paul Smith wrote: On Fri, 2019-10-11 at 10:17 -0400, Kyle Edwards wrote: On Fri, Oct 11, 2019 at 1:36 AM Alan W. Irwin < alan.w.irwin1...@gmail.com wrote: The source files that have COMPILE_OPTIONS, COMPILE_DEFINITIONS, COMPILE_FLAGS, or INCLUDE_DIRECTORIES will also

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

On Fri, 2019-10-11 at 10:17 -0400, Kyle Edwards wrote: > On Fri, Oct 11, 2019 at 1:36 AM Alan W. Irwin > < > alan.w.irwin1...@gmail.com > > wrote: > > The source files that have COMPILE_OPTIONS, COMPILE_DEFINITIONS, > > COMPILE_FLAGS, or INCLUDE_DIRECTORIES will also be skipped." > > This is by

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-68-g3008d69

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-24-g6847d81

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-38-gb727e74

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-36-ga8d42ec

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 a8d42ecb8dddc615e93559889994390bd10daf88 (commit) from

Re: [CMake] target_sources vs. PUBLIC_HEADER for libraries

Hello! After some look into target installation, I've devised the following abomination . It is ugly and not the way it should be done, but it works and only requires some discipline at copying and pasting

Re: [CMake] target_sources vs. PUBLIC_HEADER for libraries

Hi, On Fri, Oct 11, 2019 at 9:33 PM Michael Ellery wrote: > I’d like to make sure I understand two different aspects of header files > management for libraries: > > (1) typically you can add header files to target_sources, but it’s only > helpful for IDEs..so that the IDE will show the header

Re: [CMake] target_sources vs. PUBLIC_HEADER for libraries

On Fri, Oct 11, 2019, at 3:33 PM, Michael Ellery wrote: > I’d like to make sure I understand two different aspects of header files > management for libraries: > > (1) typically you can add header files to target_sources, but it’s only > helpful for IDEs..so that the IDE will show the header

[CMake] target_sources vs. PUBLIC_HEADER for libraries

I’d like to make sure I understand two different aspects of header files management for libraries: (1) typically you can add header files to target_sources, but it’s only helpful for IDEs..so that the IDE will show the header files in its sources list, correct?. In theory, cmake does not

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

On Fri, Oct 11, 2019 at 1:36 AM Alan W. Irwin wrote: > The source files that have COMPILE_OPTIONS, COMPILE_DEFINITIONS, > COMPILE_FLAGS, or INCLUDE_DIRECTORIES will also be skipped." This is by far the most likely reason. We added this restriction because we don't want files that have different

[CMake] Error because of MSVC_RUNTIME_LIBRARY value

*Here is my root CMakeLists.txt file:* cmake_minimum_required(VERSION 3.15) cmake_policy(SET CMP0091 NEW) project(test_masm) set(CMAKE_MSVC_RUNTIME_LIBRARY "MultiThreaded$<$:Debug>") add_subdirectory(src) *Here is the src/CMakeLists.txt file:* enable_language(ASM_MASM)

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-35-gfe9a903

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-3-gef5875b

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

Re: [CMake] Unity builds vs. compile_commands.json

On 10/10/19 6:53 PM, Paul Smith wrote: > Is there an intent to address this before the 3.16 release? > > Or is this a known limitation, which may or may not be addressed in > some future version of CMake? > > If the latter it should probably be added to the release notes and/or > documentation

[CMake] Linking twice for CRC32

Hello  everyone, For integrating the CRC to an ELF I believe I will need to link twice. First to create a binary on which to caclulate the CRC, and using a second pass to actually put the CRC into a the symbol at the last part of the RAM. Using the pointers by Eric  Noulard I have constructed

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

On 2019-10-10 18:21-0400 Paul Smith wrote: On Thu, 2019-10-10 at 14:57 -0400, Robert Maynard via CMake wrote: * The "UNITY_BUILD" target property was added to tell generators to batch include source files for faster compilation times. Are there any instructions on how to make this work? I

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-28-g696b2d4

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 696b2d40d4bdf5a8094f7d7c3e9ac66b039f34bf (commit) from

[CMake] Unity builds vs. compile_commands.json (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

On Thu, 2019-10-10 at 14:57 -0400, Robert Maynard via CMake wrote: > * The "UNITY_BUILD" target property was added to tell generators to > batch include source files for faster compilation times. For some reason this didn't work with my actual cmake environment, but I could enable it on a

[CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

On Thu, 2019-10-10 at 14:57 -0400, Robert Maynard via CMake wrote: > * The "UNITY_BUILD" target property was added to tell generators to > batch include source files for faster compilation times. Are there any instructions on how to make this work? I tried this: cmake -G 'Unix Makefiles'

[CMake] [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing

I am proud to announce the first CMake 3.16 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.16 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.16/release/3.16.html Some of the more

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-27-g8d2f18a

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

Re: [cmake-developers] FindThreads module documentation needs some work

I have [opened an issue on the bugtracker](https://gitlab.kitware.com/cmake/cmake/issues/19823) concerning this documentation bug. Alan __ Alan W. Irwin Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net);

[Cmake-commits] CMake annotated tag, v3.16.0-rc1, created. v3.16.0-rc1

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 annotated tag, v3.16.0-rc1 has been created at b0030385395d25452fd043fff69c603df363b328 (tag) tagging

[Cmake-commits] CMake branch, master, updated. v3.15.4-1367-gafdb354a

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

[Cmake-commits] CMake branch, release, updated. v3.15.4-1342-g9150c81

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 9150c818b7d2afb868575fcb2e0c9ba62b9d7f85 (commit) from

Re: [CMake] cmake end user vs. developer rpath handling

On Thu, 10 Oct 2019, Eric Noulard wrote: ... > with patchelf is works with an intriguing warning: > warning: working around a Linux kernel bug by creating a hole of 2093056 > bytes in ‘/path/to/executable’ > > which seems to be a resolved issue: > https://github.com/NixOS/patchelf/issues/92 > >

Re: [CMake] cmake end user vs. developer rpath handling

On Thu, 10 Oct 2019, Eric Noulard wrote: ... > No rpath and using "only" LD_LIBRARY_PATH is not feasible in that case? > Removing rpath is easy; chrpath -d lib_or_exe You could but, to avoid a maintenance headache, you'd normally end up getting the environment module to load any prereq

[Cmake-commits] CMake branch, release, updated. v3.15.4-1341-g580e322

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

[Cmake-commits] CMake branch, master, updated. v3.15.4-1365-ge3b9d12

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

Re: [CMake] HOWTO declare component inter-dependencies in multi-component packages

ping ? On 2019-10-07 12:47 p.m., stefan wrote: Hi, can you reproduce my observations ? I'm I doing something wrong or is there indeed an issue with CMake ? Should I follow up with a bug report ? Thanks, On 2019-10-04 2:20 p.m., stefan wrote: On 2019-10-03 5:24 p.m., Kyle Edwards wrote:

Re: [CMake] cmake end user vs. developer rpath handling

From: Eric Noulard Sent: 10 October 2019 14:43 To: Zakrzewski, Jakub Cc: cmake@cmake.org Subject: Re: [CMake] cmake end user vs. developer rpath handling > So I was wrong, thank you for your honest question Jakub. > I learned something usefull thanks to you.

Re: [CMake] cmake end user vs. developer rpath handling

Le jeu. 10 oct. 2019 à 14:30, Eric Noulard a écrit : > > > Le jeu. 10 oct. 2019 à 14:02, Zakrzewski, Jakub < > jakub.zakrzew...@scheer-group.com> a écrit : > >> -- >> *From:* CMake on behalf of Eric Noulard < >> eric.noul...@gmail.com> >> *Sent:* 10 October 2019

Re: [CMake] cmake end user vs. developer rpath handling

Le jeu. 10 oct. 2019 à 14:02, Zakrzewski, Jakub < jakub.zakrzew...@scheer-group.com> a écrit : > -- > *From:* CMake on behalf of Eric Noulard < > eric.noul...@gmail.com> > *Sent:* 10 October 2019 12:05 > *To:* DIXON, MARK C. > *Cc:* cmake@cmake.org > *Subject:* [DKIM]

Re: [CMake] cmake end user vs. developer rpath handling

From: CMake on behalf of Eric Noulard Sent: 10 October 2019 12:05 To: DIXON, MARK C. Cc: cmake@cmake.org Subject: [DKIM] Re: [CMake] cm?ake end user vs. developer rpath handling > No they can't because the maximum size is burried into the binary ELF file, >

Re: [CMake] cmake end user vs. developer rpath handling

Le jeu. 10 oct. 2019 à 13:08, DIXON, MARK C. a écrit : > On Thu, 10 Oct 2019, Eric Noulard wrote: > ... > > No they can't because the maximum size is burried into the binary ELF > file, > > that why CMake "reserve" some space with many ";;;" in order to replace > > BUILD_RPATH with INSTALL_RPATH

Re: [CMake] cmake end user vs. developer rpath handling

On Thu, 10 Oct 2019, Eric Noulard wrote: ... > No they can't because the maximum size is burried into the binary ELF file, > that why CMake "reserve" some space with many ";;;" in order to replace > BUILD_RPATH with INSTALL_RPATH when doing > 'install'. Hi Eric, Interesting - any ideas on how

Re: [CMake] lintian errors when using cpack

Hi again I just tried adding those additional two options, but I am getting the same error with lintian. Is there something wrong in my shlibs or control file? Thanks Matthew From: CMake on behalf of "Gillman, Matthew" Date: Thursday, 10 October 2019 at 10:58 To: Kerstin Keller ,

Re: [CMake] lintian errors when using cpack

Le jeu. 10 oct. 2019 à 11:58, Gillman, Matthew a écrit : > Hi Kerstin > > > > Sorry, I forgot to list them. Right now I only have the following set: > > > > SET(CPACK_GENERATOR "DEB") > > SET(CPACK_DEBIAN_PACKAGE_MAINTAINER "Me ") > > INCLUDE(CPack) > > > > I will try adding the two you suggest

<    1   2   3   4   5   6   7   8   9   10   >