Re: [CMake] can't generate WindowsPhone 8.1 projects

I'm using CMake 3.5.0 on Windows 10. To simplify things, I started from a fresh Windows 10 image and installed Visual Studio 2015. When I try your suggestion to use the 2013 generator, I get cmake .. -G "Visual Studio 12 2013 ARM" -DCMAKE_SYSTEM_NAME=WindowsPhone -DCMAKE_SYSTEM_VERSION=8.1

Re: [CMake] can't generate WindowsPhone 8.1 projects

I think my problem was that I had a dev machine that had upgraded through several Visual Studio versions. Now that I'm using a fresh-install of Visual Studio 2015, its working. The use of the old compiler was confusing, but if that's expected then that's ok. Aaron Simmons Application Software

Re: [CMake] can't generate WindowsPhone 8.1 projects

If you only have VS2015, then this behavior is normal. When you install the Windows Phone 8.1 SDK, it will have the VS 2013 toolset for those projects, but not the full compiler toolset. So is this currently working? Are you having trouble on one particular machine? Thanks ~Gilles From: Aaron

Re: [CMake] Cmake fails to build libssh2 - wants VC 2010 told for VC 2015 build

2016-03-14 17:44 GMT+03:00 Barry Scott : > Windows 10 with Cmake 3.4.3 or 3.5.0. > I have the following Visual C versions installed. > > Microsoft Visual Studio 14.0 > Microsoft Visual Studio 12.0 > Microsoft Visual Studio 11.0 > Visual C++ for Python > ...snip... > Why

Re: [CMake] Cmake fails to build libssh2 - wants VC 2010 told for VC 2015 build

On Tue, 15 Mar 2016 10:37:04 +0300 Sergei Nikulov wrote: > Just checked with following steps > > 1. Opened command window (cmd.exe) > 2. Clone libssh2 from GitHub (git clone > https://github.com/libssh2/libssh2.git) Out of curiosity why did you ignore my steps using

[CMake] Clarifying Cmake behavior

Hey all: I'm trying to compile boost with some weird options, and I can't get projects linked with it to compile correctly. As using regularly compiled boost seems to work just fine, this indicates my issue is not with cmake...however I was hoping I could get some clarification on how cmake

Re: [CMake] Clarifying Cmake behavior

So I combed through the source code, and solved the problem, mostly. It did turn out to be a cmake issue, sort of, so I figured I'd post here for posterity in case future problem solvers come across a similar issue. So I'm using both a custom compiler and a custom set of boost libraries. For

Re: [cmake-developers] BUG: ALL_BUILD not added to the PREDEFINED_TARGETS_FOLDER

On 15.03.2016 21:44, Taylor Braun-Jones wrote: On Tue, Mar 15, 2016 at 4:28 AM, Nils Gladitz wrote: https://cmake.org/Bug/view.php?id=15578 https://cmake.org/Bug/view.php?id=15931 It seems like one of those reports should be marked as a duplicate of the other,

Re: [cmake-developers] find_package with NO_MODULE while cross-compiling

On 15.03.2016 23:01, Julien Schueller wrote: Hi, When using find_package ( NO_MODULE) while cross-compiling, cmake may find an existing Config.cmake in the host root path if Config.cmake is not available in the target root path. For example let's say that I have Qt5 project in my host Linux

Re: [cmake-developers] BUG: ALL_BUILD not added to the PREDEFINED_TARGETS_FOLDER

On Tue, Mar 15, 2016 at 4:28 AM, Nils Gladitz wrote: > > https://cmake.org/Bug/view.php?id=15578 > https://cmake.org/Bug/view.php?id=15931 It seems like one of those reports should be marked as a duplicate of the other, no? -- Powered by www.kitware.com Please

[Cmake-commits] CMake branch, next, updated. v3.5.0-468-g0726f7a

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

Re: [cmake-developers] FindGTest modification

On 03/15/2016 02:57 PM, Zak Eckert wrote: > I updated to using the CMAKE_CONFIGURE_DEPENDS Thanks. I squashed the changes and applied them: FindGTest: Automatically re-run cmake when tests change https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a5d3d003 Please verify that version works

Re: [cmake-developers] BUG: ALL_BUILD not added to the PREDEFINED_TARGETS_FOLDER

On 03/15/2016 08:27 AM, Petr Kmoch wrote: Hi Taylor, I am afraid this behaviour is by design, so that ALL_BUILD can be the first target in the generated solution and thus the Startup project by default. However (speaking to the wider list audience), I would really appreciate an option to

Re: [cmake-developers] Duplicated linking flags are removed when linking final executable

Hi, Thanks for the suggestion about OBJECT libraries, I've learnt one more way to design my build process. Nevertheless, the effect also appears when linking dynamic libraries. For example, a slightly modified CMakeLists.txt: cmake_minimum_required(VERSION 3.5) file(WRITE a.cpp "") file(WRITE

Re: [cmake-developers] BUG: ALL_BUILD not added to the PREDEFINED_TARGETS_FOLDER

Hi Taylor, I am afraid this behaviour is by design, so that ALL_BUILD can be the first target in the generated solution and thus the Startup project by default. However (speaking to the wider list audience), I would really appreciate an option to override this "by design" behaviour. For projects

[Cmake-commits] CMake branch, next, updated. v3.5.0-453-geba1962

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

[cmake-developers] #16013 merged for testing

Hi folks, I've merged the branch boost-optional-indirect-deps into next for testing (for https://cmake.org/Bug/view.php?id=16013). Kind regards, Roger -- 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.5.0-457-g3337c49

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-461-gb256010

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

[cmake-developers] Patch to only consider build dependencies between files in the source directory

Dear All, I've already talked about this a bit back in December. https://cmake.org/pipermail/cmake-developers/2015-December/027197.html I looked at this issue today again, as in our builds we can be seriously hampered by "cmake -E cmake_depends" calls. And then, by the huge dependency trees

Re: [cmake-developers] Support CMAKE_IOS_INSTALL_COMBINED for single architecture targets

On 03/14/2016 06:40 AM, Ruslan Baratov via cmake-developers wrote: > Though user can explicitly set CMAKE_IOS_INSTALL_COMBINED=OFF for > targets with empty list of supported architectures for given SDK (say > simulator) I think it make sense to handle this case correctly in CMake > module too.

[Cmake-commits] CMake branch, next, updated. v3.5.0-459-ga308fd0

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

Re: [cmake-developers] [PATCH] Ninja: Optionally skip library dependencies for object targets

On 03/14/2016 07:39 PM, Matthias Männich wrote: > increase build parallelism by omitting dependencies of object file > targets to the libraries they will be linked with in a later step. Nice. I like the idea of doing that, but I think it can be made automatic and safe without an explicit option

Re: [cmake-developers] Duplicated linking flags are removed when linking final executable

On 03/15/2016 05:58 AM, Sergio Checa wrote: > In this example, I only want libA and libB linked into the main > executable iff their symbols are used somewhere in the linking > chain (-as-needed). This may work: add_library(A SHARED a.cpp) add_library(B SHARED b.cpp) add_library(L SHARED

[Cmake-commits] CMake branch, next, updated. v3.5.0-464-g20e46bd

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

Re: [cmake-developers] Ninja and add_subdirectory EXCLUDE_FROM_ALL

On 03/14/2016 05:04 AM, Charles Huet wrote: > I modified my patch a bit to use C++98 only, and try to stick > to the coding conventions. Thanks. While reviewing the logic I realized my suggestion to include all targets was not quite consistent with my observation that this matches the Makefile

Re: [cmake-developers] Patch to only consider build dependencies between files in the source directory

On 03/15/2016 10:48 AM, Attila Krasznahorkay wrote: > https://cmake.org/pipermail/cmake-developers/2015-December/027197.html > > With the following patch, when setting the CMAKE_ONLY_IN_SOURCE_DEPENDENCIES > variable to 1/ON/TRUE, this file size goes down to just a few kilobytes. > Speeding up

[Cmake-commits] CMake branch, master, updated. v3.5.0-234-g98f3edc

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

Re: [cmake-developers] FindGTest modification

I updated to using the CMAKE_CONFIGURE_DEPENDS. I have attached a patch that has both commits in it. Let me know if there are any other issues. Zak On Mon, Mar 14, 2016 at 10:58 AM, Brad King wrote: > On 03/11/2016 12:00 PM, Zak Eckert wrote: > > +

[Cmake-commits] CMake branch, next, updated. v3.5.0-466-g5189455

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