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

Hello, On 20.10.19 19:25, Robert Maynard via cmake-developers wrote: I am proud to announce the second CMake 3.16 release candidate. https://cmake.org/download/ CMake 3.16.0-rc2 successfully builds and tests our two large mono-repos. I'm looking forward to the release! Thanks, Gregor --

Re: [CMake] optional parameters in add_custom_target?

Hello, On 20.05.19 16:01, hex wrote: What means command1 [args1...]]? Or, should this read *add_custom_target(Name [ALL] [COMMAND command1 [args1...]]** **   [COMMAND command2 [args2...] ...]* I believe this is due to backward compatibility (pre 2.6) reasons so that you could still write:

Re: [CMake] Why is the binary md5sum value different?

On 17.05.19 02:53, Gelryun wrote: I write MakefileList.txt like this. include_directories(${COMMINC_DIR} ${DBINC_DIR} ./) link_directories(${DBLIB_DIR} ${COMMLIB_DIR}) set(DBUSERID withdb/ufdb)

Re: [CMake] Fwd: CMAKE_HOST_SYSTEM_NAME is empty

Hello, On 25.04.19 09:29, Orban, Laszlo wrote: Please help me an issue I'm facing with CMAKE_HOST_SYSTEM_NAME on FreeBSD 10.3. It gives back empty string, if I read it before the 'project(...)'. As far as I understood, CMAKE_SYSTEM_NAME can be used only after the 'project(...)' call, but

[cmake-developers] How to speed up CMake configuration on macOS

Hello, in the past when building CMake (itself) I spent long times waiting for configuration of the embedded libraries. Mostly libcurl send / receive signature detection. Today I had the idea of using system libraries installed with Homebrew and the speedups are quite noticeable: You first

Re: [CMake] CMake Project Generation Speedup

Hello, On 17.11.16 17:15, Damian wrote: We are still in the process of switching our large Make-based build to CMake. One of the issues we're running into is the time it takes to reparse and regenerate the CMake project (whether ninja, VS, or make) after touching any CMake file. To give you

[cmake-developers] Specification for CTest XML format

Hello, I'm wondering if there is a specification for the XML test output file produced by CTest? Some background: For a dashboard we'd like to know in which CMakeLists.txt a test was created. For that we use the Path tag. Here the baz test was declared in subdir/CMakeLists.txt

Re: [cmake-developers] [ANNOUNCE] CMake 3.14.0-rc3 is ready for testing

Hello, On 01.03.19 20:28, Robert Maynard via cmake-developers wrote: I am proud to announce the third CMake 3.14 release candidate. All problems observed with -rc1 and -rc2 have been solved. The rc3 works as expected for our multi-platform mono repository. Thanks for all your hard work!

Re: [cmake-developers] Properly Documenting a CMake Module

Hello, On 14.02.19 04:39, Timothy Wrona wrote: Okay so I dug a little deeper into this and it definitely looks like sphinx is the correct tool to use, but I still have one problem. I would like sphinx to be able to extract ".rst" formatted comments directly out of my cmake source files to

Re: [CMake] The Xcode generator and ASM_NASM support

Hello, On 10/3/18 6:08 PM, Tom Finegan via CMake wrote: I'm trying to get rid of some local CMake scripting for building assembly with nasm and yasm, but I'm running into a problem with the Xcode generator. For the make and ninja generators, everything is fine-- nasm and yasm are both working

Re: [cmake-developers] RfD: deprecate link_directories() and link_libraries()

Hello, On 20.08.18 19:10, Brad King wrote: On 08/15/2018 01:30 PM, Rolf Eike Beer wrote: My dislike against these functions is probably known, and now I would like to bring this to a new level: I would like to formally deprecate these functions. I don't think they serve any useful purpose

Re: [CMake] CMake update for older PPC7

Hello, On 6/20/18 3:10 AM, A. Sanchez via CMake wrote: > Hello. I have been trying to get a good version of CMake for my PS3 cluster > running linux. But everything I try to compile needs CMake 3.0 or higher? Is > there any way to update from CMAKE 2.4. Right now I am running Fedora 9, > since

Re: [cmake-developers] iOS friendly CMake

Hi, On 1/16/18 11:19 AM, Gregor Jasny wrote: > I created a CMake branch where I attempt to provide an easy way to > configure CMake projects for iOS (and all other Xcode SDKs). I have a second revision of the patches. Issue: https://gitlab.kitware.com/cmake/cmake/issues/17870 Branch:

[cmake-developers] iOS friendly CMake

Hi, I created a CMake branch where I attempt to provide an easy way to configure CMake projects for iOS (and all other Xcode SDKs). All you need to build for iOS is: cmake -DCMAKE_SYSTEM_NAME=Darwin -DCMAKE_OSX_SYSROOT=iphoneos -GXcode . In case you build code that must be code signed also

Re: [CMake] How to refer to *.so files in Android NDK?

On 6/22/17 4:01 PM, Robert Dailey wrote: > In my toolchain file for Android NDK, I specify the following *.so > paths manually: > > set( ANDROID_PREBUILT_LIBRARIES > > ${CMAKE_ANDROID_NDK}/sources/cxx-stl/gnu-libstdc++/4.9/libs/x86/libgnustl_shared.so >

Re: [CMake] Xcode duplicate filename issue?

Hello, On 6/26/17 8:12 PM, Watson, Andre wrote: > We're currently migrating a huge internal system over to CMake, and we're > nearing completion, but have run into an issue with the generated Xcode > projects. We build this system on Windows, Linux, and Mac (both makefile and > Xcode). On

[cmake-developers] Help needed: debug a xcodebuild hang

Hello, In issue #16752 [1] a hanging xcodebuild during try_compile is reported. Currently I cannot manage to find the spare time it takes to handle all CMake issues in a timely manner. Is anyone willing to help debugging this issue and/or filing a rdar:// report? Maybe someone also knows someone

[cmake-developers] Nighly build of CMake release branch available?

Hello, I wonder if a nightly (or on-demand) build of the CMake release branch is available somewhere as it is for the master branch. That would help me testing those snapshots within our companies projects. Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and

Re: [CMake] ZERO_CHECK generation and Xcode

On 3/29/17 10:15 PM, Steven Velez wrote: > I do have a pretty large project with around 142 targets. > > Another characteristic of note, and which I noticed while investigating > this is that our project suffers from > https://gitlab.kitware.com/cmake/cmake/issues/14297, and I think it is >

[cmake-developers] Email addresses of Mantis bug reporters

Hello, while walking through old bug reports contacting the reporters by email would be helpful sometimes. Is there a way for me access this information in Mantis? Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] ZERO_CHECK generation and Xcode

Hi Steven, On 3/29/17 5:24 PM, Steven Velez wrote: > If I understand correctly the purpose of the ZERO_CHECK target is to update > the generated project files when necessary. > > That's fine, but I have noticed on Xcode (8.2) that when ZERO_CHECK runs > and updates the project, it causes the

Re: [CMake] Multiple ELSE() clauses

On 3/20/17 12:09 PM, Sergey Zakharchenko wrote: > Rolf, > > 2017-03-20 14:06 GMT+03:00 Rolf Eike Beer : >> https://gitlab.kitware.com/cmake/cmake/issues/14335 > > Since the issue is marked "easy" and it's over 3 years old, I assume > nobody cares? OK then.

Re: [CMake] Multiple ELSE() clauses

Hello, On 20/03/2017 12:09, Sergey Zakharchenko wrote: Rolf, 2017-03-20 14:06 GMT+03:00 Rolf Eike Beer : https://gitlab.kitware.com/cmake/cmake/issues/14335 Since the issue is marked "easy" and it's over 3 years old, I assume nobody cares? OK then. I can try to fix it. I

Re: [CMake] Missing 'undefined dynamic_lookup' flag

On 3/12/17 6:45 PM, Gregor Jasny wrote: > On 3/10/17 12:31 AM, Cedric Doucet wrote: >> Actually, I should not modify CMAKE_CXX_COMPILER_FLAGS. >> It seems that the problem comes from the variable >> CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS which only contains ' -bundle >>

Re: [CMake] Missing 'undefined dynamic_lookup' flag

Hello, On 3/10/17 12:31 AM, Cedric Doucet wrote: > Actually, I should not modify CMAKE_CXX_COMPILER_FLAGS. > It seems that the problem comes from the variable > CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS which only contains ' -bundle > -Wl,-headerpad_max_install_names' but not ' -undefined

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-654-g7f38595

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

[cmake-developers] One Xcode project per project() call?

Hello, I just noticed that the Xcode generator creates one xcode project per project() call: > $ find _build_xcode -name "*.xcodeproj" |grep -v CMakeFiles |grep -v Tests > _build_xcode/CMake.xcodeproj > _build_xcode/Source/CursesDialog/form/CMAKE_FORM.xcodeproj >

[cmake-developers] Mirror CMake release files on GitHub?

Hello, I noticed cmake.org is quite slow on serving release files. I seldom get more than 300KB/s. So I wonder if it would make sense to publish the CMake release tarballs and binaries not only on cmake.org but also on github as part of the release process. (From GitHub I currently get 9 MB/s)

Re: [CMake] Mac OS. Cmake changes it's behaviout when building framework for iOS simulator

Hello, On 02/02/2017 16:15, Сергей Бойцов wrote: Hello. I'm looking for some help cause i have faced a really strange problem with building frameworks on Mac OS So i have: Mac OS X : el captain Xcode 8.0 CMake 3.3.2 [1], CMake 3.4.5 [2], CMake 3.5-3.6 [3] CMake [1] produced correct

Re: [CMake] Using XCODE_PRODUCT_TYPE to make kexts

Hello, On 16/01/2017 15:43, Harry Mallon wrote: Sorry look like it is not in the release build yet. correct, please use a recent nightly: https://cmake.org/files/dev/?C=M;O=D Maybe you could report back if the attribute works for you. Thanks, Gregor -- Powered by www.kitware.com Please

[CMake] MSVC15 variable available for Visual Studio 2017

Hello, I wonder if there is a reason why no MSVC15 variable is available for Visual Studio 2017? I'm using those MSVCxx variables and CMAKE_GENERATOR_TOOLSET to detect the active toolset: # Visual Studio 2008 if((MSVC90 AND "${CMAKE_GENERATOR_TOOLSET}" STREQUAL "") OR

[Cmake-commits] CMake branch, next, updated. v3.7.1-1875-g040e28b

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

[cmake-developers] require-tr1 topic

Hello Daniel, I wonder what's the idea behind the require-tr1 topic? Some still supported platforms like macOS with Xcode 3.x seem to fail now. Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware

[Cmake-commits] CMake branch, next, updated. v3.7.1-1870-g2969f55

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1866-g54fd083

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1864-g3738245

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1861-gf96cd09

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1859-g4c3b612

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

Re: [cmake-developers] Boost 1.63 support

Hello, On 27/12/2016 13:20, Roger Leigh wrote: > I opened the following merge request to add support for the > newly-released Boost 1.63: > > https://gitlab.kitware.com/cmake/cmake/merge_requests/361 I wonder what's the reason for stating explicitly all the released versions? It they are

[Cmake-commits] CMake branch, next, updated. v3.7.1-1690-g2e29d71

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

Re: [CMake] A trouble in using cmake for xcode

On 03/12/2016 19:46, Gregor Jasny wrote: > On 03/12/2016 15:07, wy39666...@163.com wrote: I have a trouble in using cmake.I try to find a way to resolve that for a long time, but finally get no results. I attempt to create an ios application imessage extension by cmake but i can't

Re: [CMake] A trouble in using cmake for xcode

On 03/12/2016 15:07, wy39666...@163.com wrote: >>> I have a trouble in using cmake.I try to find a way to resolve that for a >>> long time, but finally get no results. I attempt to create an ios >>> application imessage extension by cmake but i can't find a suitable >>> command. So i contact

Re: [CMake] A trouble in using cmake for xcode

Hello, On 01/12/2016 07:02, wy39666...@163.com wrote: > I have a trouble in using cmake.I try to find a way to resolve that for a > long time, but finally get no results. I attempt to create an ios application > imessage extension by cmake but i can't find a suitable command. So i contact >

Re: [CMake] v3.7.0 - archive_cryptor_private.h - compile error

016 09:29:14 MEZ, schrieb Gregor Jasny via CMake > <cmake@cmake.org>: >> Hello, >> >> On 25/11/2016 19:25, Nathan Sizemore wrote: >>> I receive the following when building: >>> >>> [ 40%] Building C object >>> >> Utilities/cmlibar

Re: [CMake] v3.7.0 - archive_cryptor_private.h - compile error

Hello, On 25/11/2016 19:25, Nathan Sizemore wrote: > I receive the following when building: > > [ 40%] Building C object > Utilities/cmlibarchive/libarchive/CMakeFiles/cmlibarchive.dir/archive_cryptor.c.o > In file included from >

[Cmake-commits] CMake branch, next, updated. v3.7.0-1322-g86d0d04

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

[cmake-developers] cm(Generator)Target::IsFrameworkOnApple

Hello, it looks like that during Generator Target refactoring the cm(Generator)Target::IsFrameworkOnApple and similar got duplicated. Is there a reason for this or could the GeneratorTarget simply query the Target? Do you have by any chance some high level design documentation about the most

[Cmake-commits] CMake branch, next, updated. v3.7.0-1247-ga3fb155

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

Re: [CMake] CMake 3.6 and OSX

Hello, On 02/11/2016 06:01, Robert Ramey wrote: > Here is what I'm seeing: > > a) it looks like CMake is looking for boost_filesystem rather than > libboost as I expect. (same for system). > > b) even if I tweak findBoost to force the system to look for libboost... > it still fails > > b) If I

[cmake-developers] Developer workflow with gitlab

Hello, I wonder what's the recommended workflow for CMake developers with commit access to stage? I'd like to use feature branches in gitlab but wonder how those are best merged into 'next'? Could you please advise or point me to some documentation? Thanks, Gregor -- Powered by

Re: [cmake-developers] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

On 31/10/2016 00:03, Gregor Jasny wrote: > On 30/10/2016 18:33, Jack Howarth wrote: >> Gregor, >> Your commit of... >> >> https://cmake.org/gitweb?p=cmake.git;a=log;h=540815eec2b83a8b43689580c54e8950d9f5868b >> >> has caused a major regression in cmake 3.7.0 as it no longer properly >>

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc2-828-gd3c45a8

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

Re: [CMake] CMake 3.6 and OSX

Hello Robert, On 29/10/2016 22:03, Robert Ramey wrote: > I've just "upgraded" to version 3.6 of CMake. I'm using Xcode with the > clang compiler. Now when I'm trying to configure a project I'm getting: > > The C compiler identification is unknown > The CXX compiler identification is unknown >

Re: [cmake-developers] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

On 30/10/2016 18:33, Jack Howarth wrote: > Gregor, > Your commit of... > > https://cmake.org/gitweb?p=cmake.git;a=log;h=540815eec2b83a8b43689580c54e8950d9f5868b > > has caused a major regression in cmake 3.7.0 as it no longer properly > honors the combination... > >

Re: [cmake-developers] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

On 30/10/2016 20:23, Jack Howarth wrote: > Gregor, > While I still think your hack to obtain the versioned SDK is > wrong because it relies on passing invalid arguments to 'xcodebuild > -sdk', the following change restores the expected behavior for > -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING=""

Re: [cmake-developers] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

On 30/10/2016 20:37, Jack Howarth wrote: > Proposed fix to restore functionality for > -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ > while retaining the current hack when CMAKE_OSX_DEPLOYMENT_TARGET is > not set to an empty string. Thanks for the patch but it is breaking

Re: [cmake-developers] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

Hello Howarth, I'm sorry that I broke your use case with that patch. The problem I have with maintaining the Xcode / Darwin code is that it is full of backward compatibility and unknown, undocumented use cases. That makes it sometimes hard to foresee consequences. On 30/10/2016 19:04, Jack

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-549-ga23f4f0

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-547-g54379ca

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-2461-gd1bc55f

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

Re: [CMake] CMAKE_OSX_DEPLOYMENT_TARGET vs CMAKE_OSX_SYSROOT

On 23/09/2016 22:35, Gregor Jasny wrote: > On 21/09/2016 10:54, James Turner wrote: >> >>> On 20 Sep 2016, at 16:00, Braden McDaniel wrote: >>> >>> When setting CMAKE_OSX_SYSROOT to the unversioned directory name (using >>> Xcode 8, as it happens) and setting

Re: [CMake] CMAKE_OSX_DEPLOYMENT_TARGET vs CMAKE_OSX_SYSROOT

On 21/09/2016 10:54, James Turner wrote: > >> On 20 Sep 2016, at 16:00, Braden McDaniel wrote: >> >> When setting CMAKE_OSX_SYSROOT to the unversioned directory name (using >> Xcode 8, as it happens) and setting CMAKE_OSX_DEPLOYMENT_TARGET, I get this >> error: >> >> >>

[Cmake-commits] CMake branch, next, updated. v3.6.1-1760-gb8ececb

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1474-g031a9c4

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1374-g91e3176

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

Re: [cmake-developers] [PATCH] Fix RunCMake.Framework on case sensitive file systems.

On 09/08/16 22:01, Brad King wrote: > On 08/09/2016 03:47 PM, Chaoren Lin via cmake-developers wrote: >> The file is lowercase: Tests/RunCMake/Framework/osx.cmake > > Thanks, applied: > > Tests: Fix RunCMake.Framework on case sensitive file systems. >

[cmake-developers] Email feed for new CMake bugs

Hello, in the past (with Mantis) I found it quite helpful to see new bugs posted here on this mailing list. Is it planned to restore that functionality? Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

[Cmake-commits] CMake branch, next, updated. v3.6.1-1205-g8bbcf86

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

Re: [CMake] XCode generator and .metal shader files

Hello, On 22/07/16 23:07, Victor Rykov wrote: > After adding a .metal file to a target via add_executable the metal file > does not get pushed to the generated project`s Compile Sources queue and > subsequently does not compile during project build unless I add the file to > the queue manually

[Cmake-commits] CMake branch, next, updated. v3.6.0-970-gfc0ef29

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-964-ge4b2afd

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

Re: [CMake] Logical block opening error

Hello, an editor with syntax highlighting and indention support would have helped here. On 04/07/16 01:26, Sambeet Panigrahi wrote: IF(NOT NOT_BUILD_SHARED ) ADD_LIBRARY(orocos-rtt-mqueue-${OROCOS_TARGET}_dynamic SHARED ${CPPS})

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-539-g56b88e2

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

Re: [cmake-developers] [patch] iOS combined, some fixes

On 21/06/16 18:48, Ruslan Baratov wrote: > Is the patch applied? Let me know if there are any questions left about it. Pushed into next. Sorry for the delay. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-530-g2152e11

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-410-gbb9d46a

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

Re: [cmake-developers] [patch] iOS combined, some fixes

Hello, Thanks for the patch! On 15/06/16 16:41, Ruslan Baratov wrote: > Sending some fixes found by testing with Xcode 7.3 We were chasing some errors regarding the unified build some time ago. But it appeared some for of heisenbug: the more I looked the less likely it happened. Is the error

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-291-g5ec42ea

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

Re: [cmake-developers] CMake 3.5.2 conflates OSX SDK version with target deployment

I'm away from keyboard until June 8th. everything written is from the top of my head. AFAIR the warning goes away if you properly set the OSX SYSROOT. Setting it to macosx without version number should be sufficient (maybe you have to insert a xcrun --showsdk-path there). As far as I see the

Re: [CMake] Cannot include third-party Framework headers directories as system directories in XCode for avoiding their warning

Hello, On 11/05/16 09:25, Attila Krasznahorkay wrote: > I'm a bit surprised by this. I had to explicitly tell CMake not to treat > includes coming from imported targets as system includes. Using this variable: > > https://cmake.org/cmake/help/v3.0/variable/CMAKE_NO_SYSTEM_FROM_IMPORTED.html >

Re: [cmake-developers] CLang error when building iOS bundle

Hello, On 11/05/16 21:22, Roman Wüger wrote: > I got the following error when linking the iOS bundle: > > clang: error: cannot specify -o when generating multiple output files > > I didn’t found anything about the error in the internet, so maybe someone > has already solved such error? > >

Re: [CMake] [cmake-developers] CLang error when building iOS bundle

Hello, On 11/05/16 21:22, Roman Wüger wrote: > I got the following error when linking the iOS bundle: > > clang: error: cannot specify -o when generating multiple output files > > I didn’t found anything about the error in the internet, so maybe someone > has already solved such error? > >

Re: [CMake] Xcode generator results in a project file without optimization

On 10/05/16 01:52, Siyuan Ren wrote: > Version 7.3.1 (7D1014) Could you please share your build and source directory with me? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to

Re: [CMake] Xcode generator results in a project file without optimization

On 02/05/16 11:16, Siyuan Ren wrote: > I have CMake 3.5.2. > > I write a simple CMakeLists.txt like the below > > ``` > project(mytest) > add_executable(mytest test.cpp) > ``` > > Then generate the Xcode project file with `cmake -G Xcode .`. Open the > project file in Xcode, and I found the

Re: [cmake-developers] Integration of clang-tidy

Hallo Daniel, On 09/04/16 00:31, Daniel Pfeifer wrote: > I implemented the integration of `clang-tidy` along the lines of the > `include-what-you-use` integration. > There is a new `_CLANG_TIDY` target property that is initialized > with the value of the `CMAKE__CLANG_TIDY` variable. > It

[Cmake-commits] CMake branch, next, updated. v3.5.2-1110-g3483677

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

Re: [CMake] OBJECT Libraries with Xcode Generator

On 06/04/16 20:32, Matthew Keeler wrote: > > I think I ran into a bug but I am wondering if anyone has seen it an worked > around. > > I have a source structure like the following (this is a contrived small > example to illustrate the problem): > > - CMakeLists.txt > - main.c > - lib >

Re: [cmake-developers] Making shared xcscheme files for Xcode from Cmake

Hello, On 31/03/16 16:30, Harry Mallon wrote: > This became an annoyance in our Cmake build system so here is a barebones > xcscheme creator. > https://github.com/hm1992/CMake/commit/5345881861a4b510d3a3283825584ec90f8d2061 > > Current situation: > * It seems to work for the executable targets

Re: [CMake] EFFECTIVE_PLATFORM_NAME not expanded in TARGET_* generator expressions on iOS

Hello, I fear you're one of the first users of the XCtest feature :) On 21/03/16 13:42, Vladimír Vondruš wrote: Hello, I came across this problem when trying to use XCTest macros ( https://cmake.org/cmake/help/latest/module/FindXCTest.html ) on iOS. When compiling for OSX, ctest properly

[Cmake-commits] CMake branch, next, updated. v3.5.1-671-g2d932b4

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

Re: [CMake] CMAKE_SIZEOF_VOID_P is unset when building libgit2 on Windows

On 25/03/16 22:11, Sebastian Schuberth wrote: > I also just realized CMAKE_C_ABI_COMPILER is set to FALSE in > CMakeCCompiler.cmake. Looking at CMakeError.log was a good hint. I > found: > > ---8<--- > Building C object CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj > >

Re: [cmake-developers] [CMake 0016030]: CMAKE_ASM_NASM_COMPILE_OBJECT lacks

On 25/03/16 19:28, Brad King wrote: > On 03/25/2016 01:46 PM, Gregor Jasny via cmake-developers wrote: >> Does anyone see a reason to *not* prepend all with a ? > > I'm not particularly familiar with the ASM tooling landscape but > that prepend step is exactly what was

[Cmake-commits] CMake branch, next, updated. v3.5.1-657-g021e01c

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

Re: [cmake-developers] [CMake 0016030]: CMAKE_ASM_NASM_COMPILE_OBJECT lacks

Hello, On 22/03/16 17:10, Mantis Bug Tracker wrote: > Starting with CMake 3.4 the ASM_NASM language does not pass forward > include_directories(XYZ) to the nasm compiler line. > > As far as I can see is missing for other assemblers as well. When I grep for CMAKE_ASM * _COMPILE_OBJECT I get the

[Cmake-commits] CMake branch, next, updated. v3.5.0-409-g49cff25

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-307-g67e7b48

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

Re: [cmake-developers] [CMake 0015992]: Xcode generator's ReRunCMake.make fails if dependencies have been deleted

On 27/02/16 06:11, Mantis Bug Tracker wrote: > Summary:Xcode generator's ReRunCMake.make fails if > dependencies have been deleted > Description: > Currently, if a file that a CMake script previously had a dependency on is > deleted, the Xcode generator's ReRunCMake.make

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-305-g5be433e

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

Re: [CMake] check_cxx_compiler_flag fails silently for complex compiler paths

Hello, On 26/02/16 00:00, Andrew Hundt wrote: > I believe check_cxx_compiler_flags is failing due to a long/complicated > compiler path. > > Specifically my compiler is set to: > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ > > CMake version: 3.4.3

Re: [CMake] [ANNOUNCE] CMake 3.5.0-rc3 is now ready!

Hello, I discovered that the Visual Studio 2015 Generator does not work with v120 toolsets (#15986) and consider that major issue. As far as I see this is related to the debug information setting from #15894. Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and

  1   2   >