[Cmake-commits] CMake branch, next, updated. v3.7.1-1928-gf14f487

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1925-g8dc707a

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1923-g1f2f6e0

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1919-g18e54de

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

[Cmake-commits] CMake branch, master, updated. v3.7.1-941-gaff368b

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

Re: [cmake-developers] Unknown Imported & Global libraries

> On 9 Jan 2017, at 20:55, Brad King wrote: > > On 12/21/2016 07:12 AM, Florent Castelli wrote: >> find_package(foo) >> if(NOT FOO_FOUND) >> add_library(foo STATIC foo.cpp) >> endif() > > Instead do > > find_package(foo) > if(NOT FOO_FOUND) >

[Cmake-commits] CMake branch, next, updated. v3.7.1-1915-g2d08b22

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1913-g73b4584

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1910-ga2773b1

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

[Cmake-commits] CMake branch, master, updated. v3.7.1-938-g4ce6cd2

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1908-g0e1c33d

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

[Cmake-commits] CMake branch, master, updated. v3.7.1-940-geee51e2

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

[Cmake-commits] CMake branch, master, updated. v3.7.1-934-g0dabeb6

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

[Cmake-commits] CMake branch, master, updated. v3.7.1-936-gcda3a69

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

[Cmake-commits] CMake branch, master, updated. v3.7.1-932-ga0ed39a

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

[Cmake-commits] CMake branch, master, updated. v3.7.1-930-g8f9e088

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1901-g12663fc

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1899-gc354e66

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1887-g73677b9

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1883-g07d6480

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1885-g8be34d3

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1881-gd497b25

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

[Cmake-commits] CMake branch, next, updated. v3.7.1-1879-g6681122

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

Re: [cmake-developers] Unknown Imported & Global libraries

On 12/21/2016 07:12 AM, Florent Castelli wrote: > find_package(foo) > if(NOT FOO_FOUND) > add_library(foo STATIC foo.cpp) > endif() Instead do find_package(foo) if(NOT FOO_FOUND) add_subdirectory(bundled_foo) endif() so that the imported targets are visible. Inside the bundled_foo

Re: [cmake-developers] Creating a Keil uVision generator

On 01/02/2017 06:27 PM, Paul Wilkinson wrote: > As with the Visual Studio generators, a generator for uVision projects would > ideally be a multi-configuration generator. Yes, the layouts sounds similar. A uVision project generator implementation could be modeled after the VS 2015 generator. It

Re: [cmake-developers] Recording compiler features for older gcc versions

On 01/09/2017 04:59 AM, Rolf Eike Beer wrote: > I need for several projects the ability to set CMAKE_C_STANDARD on older > compilers I think it would be fine to add the minimum infrastructure needed for that and then just disable the WCDH and Tests/* pieces that don't work with it. We could

Re: [cmake-developers] Can we please require TR1 to build CMake?

On 01/09/2017 05:46 AM, Daniel Pfeifer wrote: > start using TR1/C++11 library features, namely std::function, std::bind, > std::placeholders, std::shared_ptr, std::make_shared. I'd love to be able to start using those too, but last time I checked they are not supported everywhere CMake builds, at

[cmake-developers] CMake 3.8 feature freeze on 2017-02-01

Hi Folks, The feature freeze in 'master' for CMake 3.8 will be on Feb 1, 2017. I may announce a freeze in 'next' sometime in the preceding week so that we can get any remaining dashboard trouble cleaned up. I've just returned from vacation and will try to work through the open MRs and mailing

Re: [CMake] CMake 3.7.1 gui fails to launch

Another alternative, which is the one we use here, is to configure the custom Qt build with a "-qtlibinfix" flag - which produces libraries with completely different SONAMEs so there's no conflict. (We use this in conjunction with an RPATH.) One thing that could break is that some

[CMake] Mixing CPack and ExternalProject

All, I currently have a set of packages defined as ExternalProjects and packaged up with CPack. I've noticed recently that the preinstall step has begun failing for a given package and after a little digging, I've realized that I've likely been using CPack incorrectly for years. So, rather than

Re: [CMake] [EXTERNAL]: Up to date iOS instructions

Hi Harry, I’m not sure about any official instructions, but here’s how I’m doing it: # Adapted from https://code.google.com/p/ios-cmake/ # Standard settings set (CMAKE_SYSTEM_NAME Darwin) set (CMAKE_SYSTEM_VERSION 1) set (UNIX True) set (APPLE True) set (IOS True) # Required as of cmake 2.8.10

[CMake] SET(ENV{PKG_CONFIG_SYSROOT_DIR} $FOO) doesn't work on the first run

Hello everyone, in my toolchain file I have : SET(ENV{PKG_CONFIG_SYSROOT_DIR} "${RPI_ROOT_PATH}") then I run : cmake -DCMAKE_TOOLCHAIN_FILE=${PWD}/../of/dev/arm-linux-gnueabihf.cmake -DRPI_ROOT_PATH='/tmp/rpi/root' -DOF_PLATFORM=armv7 -G Ninja ../of Environnement variable

Re: [CMake] How do static libraries get linked in Ninja?

When I make an example project I see the following link line /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/example.dir/test.cpp.o -o example liblib1.a liblib2.a && : Can you

[CMake] Up to date iOS instructions

Hello, Are there any up to date instructions for doing iOS builds? There are load of tutorials going back many years on Google. I am using something based on this https://github.com/cristeab/ios-cmake as a toolchain file currently but I am seeing the ${EFFECTIVE_PLATFORM_NAME} generator

[cmake-developers] Can we please require TR1 to build CMake?

Hi and happy 2017, I am currently doing some refactoring (more on that later) and I would like to start using TR1/C++11 library features, namely std::function, std::bind, std::placeholders, std::shared_ptr, std::make_shared. Some background information: The Dinkumware standard library

[cmake-developers] Recording compiler features for older gcc versions

I need for several projects the ability to set CMAKE_C_STANDARD on older compilers, at least gcc 4.2, but preferably also down to gcc 3.4. I have them available, so testing is not the issue. But there are some problems besides "just record them". The problems that I know of:

Re: [cmake-developers] [RFC] Fastbuild generator

Hi, I ported the work of @inbilla to CMake trunk a few months ago, and fixed quite a few tests on my fork: https://github.com/packadal/CMake I think it would be best if we tried to synchronize our efforts, since lots of people are interested in getting a FastBuild generator for CMake ! There is

Re: [CMake] Tracing ctest crash on windows

Hallo Aaron, if you’d like to have the full luxury of visual studio with test explorer and running/debugging tests directly as you can do it with other .NET based tests etc. you can try these extensions: - child process debugging power tools