[cmake-developers] [PATCH] Proposed fix for bug 15183

Hello, I would like to propose the following fix for bug 15183 ( https://cmake.org/Bug/view.php?id=15183) For some reason the XcodeGenerator seemed to be setting the INSTALL_PATH variable regardless of if it was initialized or not (which is done only for shared libraries). This seems almost

Re: [cmake-developers] CMake alternative language

Hi, > * There is a lot of code out there in the current CMake language so I do not think it is realistic to drop it. I'm not proposing that this change. I am. (more below) > * Many projects build elaborate macro/function systems in the CMake language in order to end up with a declarative

[cmake-developers] cmake daemon mode protocol

Hi Stephen, I have successfully build and run your cmake server mode changes and the python client script does work as advertised. I do have a couple of remarks about it. This is more intended as a starting point for discussion as a real proposal. Would something along these lines be possible:

Re: [cmake-developers] CMake alternative language

I don't think this is a dumb question, actually this is part of the problem I think would be resolved whit a new language. The barrier of entry to using CMake is too high in my opinion, and I think using an existing language would lower it *a lot*. Thanks for sharing :) Le mer. 13 janv. 2016 à

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 1/12/16, Brad King wrote: > On 01/08/2016 06:15 PM, Eric Wing wrote: >> simple 'swiftc' integration going for ADD_EXECUTABLE, as described in >> the original post. > > Take the generator check out of Modules/CMakeDetermineSwiftCompiler.cmake > to get rid of the up-front

Re: [cmake-developers] CMake alternative language

On Sri, 2016-01-13 at 13:14 +, Charles Huet wrote: > I don't think this is a dumb question, actually this is part of the > problem I think would be resolved whit a new language. > > The barrier of entry to using CMake is too high in my opinion, and I > think using an existing language would

Re: [CMake] How to get generated dependencies

On Tue, Jan 12, 2016 at 9:58 AM, Tom Kacvinsky wrote: > Is there a way of invoking cmake to get the list of non-system header > dependencies, like invoking gcc with -MMD? I need to find out the > list of non-system header dependencies and I know cmake has a way of >

Re: [CMake] How to get generated dependencies

On Wed, Jan 13, 2016 at 11:31 AM, j s wrote: > From what I remember from the mailing list a long time ago, CMake has its > own dependency generator independent of the CPP. > it does; but not for all generators > > On 1/13/16 1:20 PM, Tom Kacvinsky wrote: >> >> On Wed, Jan 13,

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

On Wednesday, January 13, 2016 10:16:23 Robert Dailey wrote: > Running version 3.2.2 on Ubuntu 15. I run the following command: > > $ cmake .. -G"KDevelop3" -DCMAKE_C_COMPILER=gcc-4.9 > -DCMAKE_CXX_COMPILER=g++-4.9 -DCMAKE_BUILD_TYPE=$config >

[Cmake-commits] CMake branch, next, updated. v3.4.1-1956-g0a9d803

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

[cmake-developers] [CMake 0015916]: [Buildroot] [PATCH] cmake: use system libzma when the xz package is enabled

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15916 == Reported By:R Jones Assigned To:

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

On Wed, Jan 13, 2016 at 12:36 PM, Brad King wrote: > On 01/13/2016 11:16 AM, Robert Dailey wrote: >> Running version 3.2.2 on Ubuntu 15. I run the following command: > [snip] >> cmake: ../../Source/cmTarget.cxx:722: void >>

Re: [CMake] How to get generated dependencies

On Wed, Jan 13, 2016 at 2:09 PM, J Decker wrote: > The short answer is 'no'. I see depends.internal was generated with the gcc (in my case) option -MD (or perhaps -MDD). Ss cmake knows how to do this. Question: is this at build time or Makefile generation time? If the

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

On 01/13/2016 11:16 AM, Robert Dailey wrote: > Running version 3.2.2 on Ubuntu 15. I run the following command: [snip] > cmake: ../../Source/cmTarget.cxx:722: void > cmTarget::GetSourceFiles(std::vector> &, const string&) const: Assertion `this->GetType() != >

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

On Wednesday, January 13, 2016 12:44:59 PM Robert Dailey wrote: > On Wed, Jan 13, 2016 at 12:36 PM, Brad King wrote: > > On 01/13/2016 11:16 AM, Robert Dailey wrote: > >> Running version 3.2.2 on Ubuntu 15. I run the following command: > > [snip] > > > >> cmake:

Re: [cmake-developers] CMake alternative language

On Wednesday, January 13, 2016 10:59:39 yann suisini wrote: > Hi, > > I'm a new user of CMake, but I just want to express my newcomer point of > view. > Honestly , I can feel the power of CMAKE, but it's a real pain to learn ... > I'm using CMAKE for an embedded platform with a non GNU compiler ,

Re: [CMake] How to get generated dependencies

From what I remember from the mailing list a long time ago, CMake has its own dependency generator independent of the CPP. On 1/13/16 1:20 PM, Tom Kacvinsky wrote: On Wed, Jan 13, 2016 at 2:09 PM, J Decker wrote: The short answer is 'no'. I see depends.internal was

Re: [CMake] How to get generated dependencies

Or reorganize your project so your includes aren't all scattered and just INSTALL(DIRECTORY include ) On Wed, Jan 13, 2016 at 12:00 PM, Tom Kacvinsky wrote: > Should have read the docs before I asked that last question: > file(STRINGS ...) is what I want > > On

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

Am Mittwoch, 13. Januar 2016, 12:44:59 schrieb Robert Dailey: > On Wed, Jan 13, 2016 at 12:36 PM, Brad King wrote: > > On 01/13/2016 11:16 AM, Robert Dailey wrote: > >> Running version 3.2.2 on Ubuntu 15. I run the following command: > > [snip] > > > >> cmake:

Re: [CMake] How to get generated dependencies

Should have read the docs before I asked that last question: file(STRINGS ...) is what I want On Wed, Jan 13, 2016 at 2:59 PM, Tom Kacvinsky wrote: > I suppose what I could do is get the target properties for the > compiler flags (will this include compiler defines

Re: [CMake] How to get generated dependencies

I suppose what I could do is get the target properties for the compiler flags (will this include compiler defines and include directories?), add -MDD -c (using gcc, so those are the options I want) to the compiler flags and make a custom command to generate the file, then post process it to get

Re: [CMake] How to get generated dependencies

The short answer is 'no'. On Wed, Jan 13, 2016 at 10:26 AM, Tom Kacvinsky wrote: > On Tue, Jan 12, 2016 at 9:58 AM, Tom Kacvinsky > wrote: >> Is there a way of invoking cmake to get the list of non-system header >> dependencies, like

[Cmake-commits] CMake branch, next, updated. v3.4.1-1954-g021378e

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

[CMake] using macros

I am trying to use a macro to enable c99 in some of my cmake modules. In the top level cmake file I add this macro macro(use_c99) if (CMAKE_VERSION VERSION_LESS "3.1") if (CMAKE_C_COMPILER_ID STREQUAL "GNU") set (CMAKE_C_FLAGS "--std=gnu99 ${CMAKE_C_FLAGS}") endif () else ()

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

> For the moment, I like swiftc over swift because it seems a lot > simpler. I hope this means the least changes for CMake right now. I need to correct myself on this. While I like swiftc for looking simpler, I'm actually thinking swift might be fewer changes since the file-by-file thing is what

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

>> If my hunch is correct, how do I tell CMake to ‘promote’ Swift as the >> correct tool? > > See the CMAKE__LINKER_PREFERENCE platform information variable. > There is also the LINKER_LANGUAGE target property. For C, C++, and > Fortran one generally chooses between C++ and Fortran to drive the >

[cmake-developers] [CMake 0015917]: Visual Studio project files generated incorrectly

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15917 == Reported By:Daniel Williams Assigned To:

Re: [CMake] CMAKE_INSTALL_RPATH_USE_LINK_PATH is broken?

On Jan 8, 2016 8:16 PM, Elizabeth Fischer wrote: > > Hello, > > I'm using cmake 3.4.1.  I'm trying to compile libraries & executables with an > RPATH.  To that end, I use the following settings: >> >> >> SET(CMAKE_SKIP_BUILD_RPATH  FALSE) >>

[Cmake-commits] CMake branch, master, updated. v3.4.1-833-g6be2ded

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20160113) +set(CMake_VERSION_PATCH 20160114) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, next, updated. v3.4.1-1952-g9167410

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

[cmake-developers] [CMake 0015915]: add_subdirectory(directory EXPORT_VARIABLES VAR_1 VAR_2) gives "add_subdirectory called with incorrect number of arguments"

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15915 == Reported By:Bryan Koch Assigned To:

[cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

Running version 3.2.2 on Ubuntu 15. I run the following command: $ cmake .. -G"KDevelop3" -DCMAKE_C_COMPILER=gcc-4.9 -DCMAKE_CXX_COMPILER=g++-4.9 -DCMAKE_BUILD_TYPE=$config -DCMAKE_TOOLCHAIN_FILE="../toolchains/linux_i686.toolchain.cmake" My toolchain file is specified as follows:

[CMake] test endian ness

Hi I am familiar with autoconf and trying to migrate our project to cmake. Thus newbie. I am running cmake 3.2.2 on Linux Mint 17 I have seen in the documentation the macro https://cmake.org/cmake/help/v3.2/module/TestBigEndian.html?highlight=endian#module:TestBigEndian which seems very

Re: [CMake] test endian ness

Hi, May be to include the module before using it: include (TestBigEndian) On 13/01/16 15:25, "CMake on behalf of Vania Joloboff" wrote: >Hi > >I am familiar with autoconf and trying to migrate our project to cmake. >Thus

Re: [CMake] [cmake-developers] Why does INTERFACE type targets only support whitelisted properties?

On Mon, Jan 11, 2016 at 16:47:03 -0500, Taylor Braun-Jones wrote: > I have another INTERFACE property use case that is not whitelisted, but > should be: VERSION VERSION is a special property for libraries. Particularly the name for the file with the actual content of the library (the SOVERSION

Re: [cmake-developers] [CMake] Why does INTERFACE type targets only support whitelisted properties?

On Mon, Jan 11, 2016 at 16:47:03 -0500, Taylor Braun-Jones wrote: > I have another INTERFACE property use case that is not whitelisted, but > should be: VERSION VERSION is a special property for libraries. Particularly the name for the file with the actual content of the library (the SOVERSION

[Cmake-commits] CMake branch, next, updated. v3.4.1-1950-g1e6e2d6

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1940-ge0c8efb

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

Re: [cmake-developers] Allowing generator expressions in install DIRECTORY

On 01/12/2016 04:34 PM, Yves Frederix wrote: > I am attaching a patch that adds support for generator expressions in > the DIRECTORY arguments of install(DIRECTORY ...). It is my first > contribution Very nice! The impl, docs, and tests all look good. Applied with minor whitespace tweak and a

[Cmake-commits] CMake branch, next, updated. v3.4.1-1946-g646f594

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-830-g59dac28

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-827-g5774f38

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-825-gef3202f

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