[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-239-gcf1a414

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-237-g634c780

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

Re: [cmake-developers] Patch: refactor XCode blocks writing function

Hello Robert, On 19/02/16 20:12, Robert Goulet wrote: > I did this refactoring of the function that writes the XCode blocks in the > project files, that adds support for any number of nested blocks. And it also > makes the code easier to expand in the future. > > One of the areas that required

Re: [cmake-developers] Drop support for older Xcode versions?

Hello, On 19/02/16 00:34, Davy Durham wrote: Actually we have to keep an os x 10.8 box up with the 10.7 sdk using xcode 4.2 targeting 10.6. Apple long ago stopped allowing you to target such old APIs in more recent xcodes. At my company we build 10.6 compatible software using Xcode 6.3. What

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc1-55-g830e87e

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc1-53-gc4e3666

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

[CMake] Drop support for older Xcode versions?

Hello, I'd like to get your feedback on deprecating or dropping support for older Xcode versions. During changes on the Xcode generator it gets harder and harder to test against old and very old Xcode versions like 3 and 4. Are there still users around for these versions of Xcode? PS: I'm

[cmake-developers] Drop support for older Xcode versions?

Hello, I'd like to get your feedback on deprecating or dropping support for older Xcode versions. During changes on the Xcode generator it gets harder and harder to test against old and very old Xcode versions like 3 and 4. Are there still users around for these versions of Xcode? PS: I'm

Re: [cmake-developers] Xcode generator is adding old attributes on .pbxproj

Hello, some time ago I started a project to make the CMake generated pbxproj identical to the one Xcode writes. Some patches of that effort are already in master, some lack some cleanup. It would be great working with you on individual patches to 'modernize' generated pbxproj files. Patches

Re: [CMake] Using ccache with Xcode generator

Hello, On 01/02/16 04:52, Craig Scott wrote: > After a bit of experimenting, it seems that getting ccache working with the > Xcode generator isn't so straightforward. For Ninja and Unix Makefiles, the > RULE_LAUNCH_COMPILE global property nicely gives us the behaviour we want, > but this doesn't

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

Hello, On 13/01/16 12:13, Marko Kylmämaa wrote: > 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

Re: [CMake] Adding definitions to compile one file ?

Hi, On 21/01/16 15:14, Vania Joloboff wrote: Hi I want to add two definitions to compile one specific files in addition to the global definitions. I have the following problem. If I use set_source_files_properties(source.cpp PROPERTIES COMPILE_DEFINITIONS VAR1=${MY_VAR1} VAR2=${MY_VAR2} )

[Cmake-commits] CMake branch, next, updated. v3.4.1-1845-gacf58fe

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1837-gb03eb97

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

Re: [CMake] Add support for cross compiling to VxWorks

Hello, please have a look at some other toolchain file like the BlackBerry one: > https://github.com/blackberry/OGRE/blob/master/src/CMake/toolchain/blackberry.toolchain.cmake On 30/12/15 21:38, Kuhl, Brian wrote: > I'm trying to add support for VxWorks to CMake. > My current dilemma is that

[cmake-developers] Anyone going to FOSDEM?

Hello, I wonder if any of you CMake Developers go to FOSDEM [1] this year? Thanks, Gregor [1] https://fosdem.org/2016/ -- 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 support the

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 11/12/15 22:16, Clinton Stimpson wrote: >> To enable iOS build, I'm using following settings in CMakeLists.txt: >> > >> > >> > set(APPLE_PLATFORM "iphonesimulator") >> > set(CMAKE_OSX_SYSROOT >> > "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platf >> >

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 11/12/15 20:21, clin...@elemtech.com wrote: > - On Dec 11, 2015, at 11:44 AM, Bartosz Kosiorek > wrote: >> Because there is difference between OS X and iOS Bundles directory structure >> (see: Apple specification >>

[Cmake-commits] CMake branch, next, updated. v3.4.1-1695-gcaa83f4

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

Re: [CMake] target_include_directories SYSTEM adds -isystem to Clang, but not GCC

On 08/12/15 20:21, digitalriptide wrote: > Thank you Gregor! I have tried the Makefile generator, but on OS X -isystem > still seems to be missing with GCC. The -isystem flag appears with Clang, > however. I have installed CMake 3.4.1 and GCC 5.3.0, both through MacPorts. > I can provide a sample

Re: [cmake-developers] Please comment on ios-universal topic

Hello, On 09/12/15 10:21, Ruslan Baratov wrote: IOS_INSTALL_COMBINED_BINARY Just to clarify you want to leave only one variable IOS_INSTALL_COMBINED_BINARY for the device + simulator on iOS platforms. Other platforms (in future) will be controlled by using *_ARCHITECTURES variables, right?

Re: [cmake-developers] Static Bootstrap: CCMake & GPM

Hello Axel, On 08/12/15 01:53, Huebl, Axel wrote: My problem: I found that in the last step of linking ccmake against a static (pre-compiled, ubuntu 12.04) ncurses library leads to linker errors such as: /usr/lib/x86_64-linux-gnu/libncurses.a(lib_mouse.o): In function `_nc_mouse_event':

Re: [cmake-developers] Please comment on ios-universal topic

Hello, On 02/12/15 13:44, Bartosz Kosiorek wrote: > I would like to propose to rename property name to INSTALL_IOS_UNIVERSAL_LIBS. My thoughts about the property name: I added the necessary functionality to also combine Frameworks and App Bundles. So the _LIBS suffix now got misleading. And I

[Cmake-commits] CMake branch, next, updated. v3.4.1-1578-g23b5ca6

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1607-g1c27e7d

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

[cmake-developers] Please comment on ios-universal topic

Hello, During the last days I worked on the iOS Universal Install topic which now would benefit from a review. Especially the core changes could need a third pair of eyes: https://cmake.org/gitweb?p=stage/cmake.git;a=commit;h=8fb23b42cfc2fb7490e8645fff328add9c231713 I will now concentrate on

[Cmake-commits] CMake branch, next, updated. v3.4.0-1550-g523ccb5

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1548-g48f4880

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1528-gf312371

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

Re: [CMake] target_include_directories SYSTEM adds -isystem to Clang, but not GCC

On 15/11/15 21:13, digitalriptide wrote: Did this fix make it into 3.4? After upgrading to 3.4, GCC still seems to lack -isystem flags on OS X. Is there anything extra I need to do? It should be fixed for the Makefile and Ninja generators but not Xcode. My proposed fix broke older Xcode

[Cmake-commits] CMake branch, next, updated. v3.4.0-1336-gfaf5e0e

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

Re: [cmake-developers] [PATCH] CMake 3.4.0rc3 Apple documentation update

On 11/11/15 05:48, Bartosz Kosiorek wrote: Hello. I think before release CMake 3.4.0 the documentation needs to be updated, to reflect last changes in CMake regarding Apple platform. I have created bug report for that issue: https://public.kitware.com/Bug/view.php?id=15843 I also updated

Re: [cmake-developers] [PATCH] iOS Framework Bundle support

Hello, On 10/11/15 16:22, Bartosz Kosiorek wrote: > My name is Bartosz Kosiorek and I'm TomTom developer and Open Source > enthusiast. I'm Gregor a part time contributor to CMake. During the last months I mostly worked on Xcode support. > Last time in our products, we notice that cmake is not

[CMake] Greediness of kwsys regex

Hello, Today I stumbled across funny behavior of string(REGEX REPLACE: This one would lead to an empty match: string(REGEX REPLACE "(.*)" "\\1Proxy.cpp" _out "IConnectionCallback") This one would match whole "IConnectionCallback" string(REGEX REPLACE "(.+)" "\\1Proxy.cpp" _out

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc2-1201-gacd292f

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc2-923-g8fbc8e4

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc2-925-gaddb1da

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

Re: [cmake-developers] Patch: install universal iOS libraries

On 08/10/15 02:37, Ruslan Baratov wrote: >>> export CORRESPONDING_DEVICE_PLATFORM_NAME=iphoneos >>> export CORRESPONDING_DEVICE_SDK_NAME=iphoneos9.0 >>> export SDK_NAME=iphonesimulator9.0 >> Could you use those variables to avoid hardcoding iphoneos/simulator in >> the module? > I see

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-813-g8ab1833

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-733-g03c0c9c

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

Re: [CMake] Known issues with Xcode 6.x and CMake

Hello, On 17/10/15 18:28, Michael Jackson wrote: Are there any known issues with Xcode 6.4 and CMake 3.3.x? I ask because in our project when we generate the Xcode project we end up with 2 or 3 executables listed in the drop down combo box. We also end up with lots of duplicate targets in

Re: [cmake-developers] cmake Xcode bug clobbering -ObjC/-ObjC++ flags

On 15/10/15 19:16, Davy Durham wrote: > Bug filed here: https://cmake.org/Bug/view.php?id=15794 > Patch file against git master HEAD attached to this email. > > Acceptable? I responded to the bug report itself: https://cmake.org/Bug/view.php?id=15794#c39625 Two questions for the CMake

Re: [cmake-developers] Issue on CMAKE_OSX_SYSROOT

Hi Francesco, On 10/10/15 14:34, Gregor Jasny wrote: > On 06/10/15 16:00, Brad King wrote: >> Okay, that looks like the underlying issue. The >> Modules/Platform/Darwin-Initialize.cmake module will have >> to be taught about this case to do the right thing by default >> if it does not already.

Re: [cmake-developers] Issue on CMAKE_OSX_SYSROOT

On 06/10/15 16:00, Brad King wrote: > Okay, that looks like the underlying issue. The > Modules/Platform/Darwin-Initialize.cmake module will have > to be taught about this case to do the right thing by default > if it does not already. > > Gregor, do you mind taking a look at this? Sure.

Re: [CMake] [cmake-developers] Xcode build settings and BullseyeCoverage

Hello, On 09/10/15 17:51, Roman Wüger wrote: > I’m trying to configure and build a project with the “Xcode” generator and > the bullseye coverage tool. > > Without the bullseye coverage tool it works fine but if I want to use it I > had to do the following workaround: >

Re: [cmake-developers] Patch: install universal iOS libraries

Hello, thank you for working on this. This is really hairy stuff. On 24/09/15 11:10, Ruslan Baratov via cmake-developers wrote: > Patches help to install universal iOS (device + simulator) libraries by > triggering some extra instructions (build + fuse) after "regular" > library installation

Re: [cmake-developers] xcode7-defaults-to-c11 topic

Hi, On 15/09/15 20:24, Stephen Kelly wrote: > I have merged a Konsole output compute-default-dialect to next for > testing which implements the automatic detection. Please test it to see > if it works with xcode 7. The CompileFeatures test does pass: $ git describe v3.3.1-3005-gf1591ef I

Re: [CMake] FindGit.cmake proposal

Hello, On 10/09/15 16:34, Daniel Wirtz wrote: > i've now quite often encountered the need to access basic git > information about the source tree from within cmake. > i've attached the current FindGit.cmake module shipped with CMake > enhanced by two functions: getGitRevision and getGitBranch. >

[Cmake-commits] CMake branch, next, updated. v3.3.1-2926-g4653dc3

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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2822-g34141ce

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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2773-gcfbf387

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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2775-g5259219

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

Re: [CMake] How to do that w/o LOCATION property of a target...

On 05/09/15 08:22, Alex Turbov wrote: > Hi, > > in my project I have `add_executable()`. after that, in a current binary > dir I need to render a `*.cmake` script (via `configure_file()`) to be > running from `add_test()` (as `cmake -P`) which should start just the > compiled executable via

Re: [CMake] Writing find packages

Hello, On 03/09/15 23:15, Robert Dailey wrote: > How recent is this documentation? > http://www.cmake.org/Wiki/CMake:How_To_Find_Libraries#Writing_find_modules > > It seems rather old. What is the modern way of doing this? The cmake-developer help page has a section about modules:

[Cmake-commits] CMake branch, next, updated. v3.3.1-2770-g6985b37

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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2765-g8be433e

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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2762-ga9b52ab

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

[cmake-developers] CDash broken

Hello, from time to time the CMake Dashboard at http://www.cdash.org/CDash/index.php?project=CMake is very slow. Right now I cannot access it at all. Does anyone know what's wrong? Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

[Cmake-commits] CMake branch, next, updated. v3.3.1-2694-gb817975

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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2666-g70c864a

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

Re: [cmake-developers] Fixing bug #12506 (iOS install)

Hallo, On 13/08/15 12:56, Ruslan Baratov wrote: On 13-Aug-15 08:46, Gregor Jasny wrote: On 13/08/15 01:44, Ruslan Baratov via cmake-developers wrote: Sending patches with fix. Now it's possible to install simulator libraries by: cmake --build _builds --config Release --target install --

Re: [cmake-developers] Xcode 7 tbd library stub support

On 25/08/15 19:01, Brad King wrote: On 08/24/2015 04:43 PM, Gregor Jasny via cmake-developers wrote: I just pushed a topic branch to add support for Xcode 7 TDB files: http://www.cmake.org/gitweb?p=stage/cmake.git;a=shortlog;h=refs/heads/apple-tbd-stubs Thanks. Please merge to 'next' when

[Cmake-commits] CMake branch, next, updated. v3.3.1-2450-g849ccc5

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

Re: [cmake-developers] Adding Swift support to CMake

Hi Eric Brad, On 15/07/15 12:16, Eric Wing wrote: On 7/7/15, Brad King brad.k...@kitware.com wrote: On 07/02/2015 07:54 PM, Eric Wing wrote: Thank you Brad. When you are ready, let me know how I can help next. I have basic support with the Xcode generator done. Please try out this commit:

Re: [cmake-developers] [CMake 0015669]: XCTest for iOS target has incorrect TEST_HOST

Hi Brad, On 21/08/15 15:36, Brad King wrote: Thanks. I merged to 'next' for testing last night. Please take a look at the failures: https://open.cdash.org/testSummary.php?project=1name=RunCMake.XcodeProjectdate=2015-08-21 It's all green now:

[cmake-developers] Xcode 7 tbd library stub support

Hello, Starting with Xcode 7 the OSX and iOS SDKs contain only stub files for dynamic system libraries. These stub files contain some meta data and a list of exported sysbols in plain text. They are handled by the toolchain like regular dylibs. I just pushed a topic branch to add support for

[Cmake-commits] CMake branch, next, updated. v3.3.1-2325-gc12be0d

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

[Cmake-commits] CMake branch, next, updated. v3.3.1-2319-g524481c

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

Re: [CMake] cmake iOS application + framework link error

Hi David, On 04/05/15 20:12, David Hirvonen wrote: Thanks for the response. I've moved to a more standard *nix layout for all platforms, and will rely on a post-build step to create my framework (for now). If I find a fix, I'll be sure to share it here. On Wed, Apr 29, 2015 at 5:22 AM, Eric

Re: [CMake] target_include_directories SYSTEM adds -isystem to Clang, but not GCC

Hello, On 17/08/15 01:01, digitalriptide wrote: When I add SYSTEM to target_include_directories, for example using target_include_directories( my_target SYSTEM PUBLIC ${MY_LIBRARIES} ) in Clang, CMake prepends -isystem to the relavent -I/my/library/path type flags. With GCC, however, I see no

Re: [cmake-developers] [CMake 0015597]: Issues with the 'Eclipse CDT4 - NMake Makefiles' Generator

Hello, On 29/05/15 20:56, Mantis Bug Tracker wrote: Summary:Issues with the 'Eclipse CDT4 - NMake Makefiles' Generator Description: The project compiles and links in Eclipse but the preprocessor symbols are not defined by the .cproject file. As a result, sections with

Re: [cmake-developers] Fixing bug #12506 (iOS install)

On 15/08/15 21:00, Gregor Jasny wrote: On 13/08/15 12:56, Ruslan Baratov wrote: This looks great! I've spent several hours trying to figure out how '$(EFFECTIVE_PLATFORM_NAME)' can be set to Xcode and some CMake friendly string to cmake_install.cmake script. I didn't know Xcode understand

Re: [cmake-developers] Fixing bug #12506 (iOS install)

On 13/08/15 12:56, Ruslan Baratov wrote: This looks great! I've spent several hours trying to figure out how '$(EFFECTIVE_PLATFORM_NAME)' can be set to Xcode and some CMake friendly string to cmake_install.cmake script. I didn't know Xcode understand `${VAR}` syntax (probably it didn't, it's

Re: [cmake-developers] Fixing bug #12506 (iOS install)

Hi, On 13/08/15 01:44, Ruslan Baratov via cmake-developers wrote: Sending patches with fix. Now it's possible to install simulator libraries by: cmake --build _builds --config Release --target install -- -sdk iphonesimulator and device libraries by: cmake --build _builds --config Release

Re: [cmake-developers] Fixing bug #12506 (iOS install)

Hi, On 07/08/15 00:43, Ruslan Baratov via cmake-developers wrote: Hi, I'm thinking about fixing bug http://public.kitware.com/Bug/view.php?id=12506 and before I go deeper in CMake internals just want to ask is there any work-in-progress attempts already or hints/directions of how it can be

[Cmake-commits] CMake branch, next, updated. v3.3.0-1895-gc06c74f

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

[Cmake-commits] CMake branch, next, updated. v3.3.0-1577-g45a48d7

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

Re: [cmake-developers] [CMake 0015669]: XCTest for iOS target has incorrect TEST_HOST

Hello, On 29/07/15 14:07, Mantis Bug Tracker wrote: == http://www.cmake.org/Bug/view.php?id=15669 == this bug caused by different App Bundle layout in MacOSX

[CMake] Create space delimited string with $JOIN: genex

Hello, in my build process I need to call a compiler like tool with the same include directories as a certain target. I tried the following: cmake_minimum_required(VERSION 3.2) project(cmake-genex C) add_library(dummy dummy.c foo.c) target_include_directories(dummy PUBLIC foo bar) set(prop

Re: [cmake-developers] How is the Visual Studio compiler looked up

On 07/07/15 10:10, Gregor Jasny wrote: one of my colleagues is unable to generate a VS2013 solution. He gets the following error: Please disregard. This was a vc12 vs. VS2012 confusion. Sorry for the noise. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ

[cmake-developers] How is the Visual Studio compiler looked up

Hello, one of my colleagues is unable to generate a VS2013 solution. He gets the following error: F:\CitrixLibs\ExternalLibs\CMake\3.1.3\Tools_Windows\bin\cmake.exe -G Visual Studio 12 -T v120_xp -A Win32 -DWITH_COPY_PREBUILT_CACHE=ON -DWITH_COPY_PREBUILT=ON

Re: [CMake] Xcode project generation failed

On 17/06/15 16:29, Michael Jackson wrote: Just to follow up with this issue in case anyone else has issues with Xcode here is what happened. Thanks to Gregor for taking a look at the generated project file he was able to identify an issue where there were file paths in the form of // inside

Re: [CMake] Xcode project generation failed

Hello, I applied some fixes to what becomes CMake 3.3. could you please test the release candidate? On 16/06/15 16:27, Michael Jackson wrote: Running OS X 10.8.5 with Xcode 5.1.1 and Cmake 3.2.x and 3.3.RC and neither generate a Xcode project file that can be opened by Xcode. We get valid

Re: [CMake] Xcode project generation failed

On 16/06/15 21:27, Gregor Jasny wrote: Hello, I applied some fixes to what becomes CMake 3.3. could you please test the release candidate? Sorry, somehow overlooked the statement about RC in your mail. On 16/06/15 16:27, Michael Jackson wrote: Running OS X 10.8.5 with Xcode 5.1.1 and

Re: [CMake] CMAKE_COLOR_MAKEFILE

On 10/06/15 04:17, Dave Yost wrote: Hey, I love colors. But one of my users doesn’t. You could try the Ninja generator instead of Makefile. It much often faster, as verbose as necessary, and black'n'white. Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and check

Re: [CMake] How do I set an Xcode property on the global/root project?

Hi Eric, On 14/06/15 14:38, Eric Wing wrote: I have been successful at setting Xcode properties on specific targets with CMake via: set_property (TARGET ${TARGET} PROPERTY XCODE_ATTRIBUTE_${XCODE_PROPERTY} ${XCODE_VALUE}) But I have been unable to set properties on the global/root

<    1   2