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, no?
Done ... not that
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 keep messages on-topic an
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 ov
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
For the Visual Studio generator, the ALL_BUILD is not added to the
PREDEFINED_TARGETS_FOLDER ("CMakePredefinedTargets").
Tested on Windows 10 with Visual Studio 2013 using the following
minimal CMakeLists.txt:
cmake_minimum_required(VERSION 3.5)
project(foobar)
set_property(GLOBAL PROPERTY USE_FO
