Re: [cmake-developers] Trojan in latest release

2019-03-21 Thread kevin
Yes, your correct on the url. Using the link from your email. Gave me the same 
Trojan. I have not actually seen the file, because windows defender is 
preventing the download from completing.

Sent from my iPhone

> On Mar 21, 2019, at 12:45 PM, Brad King  wrote:
> 
>> On 3/21/19 12:31 PM, kevin wrote:
>> Linked from https://camel.org/download
> 
> I'll assume you meant `cmake.org` there.
> 
>> Platform->windows win64-x64 installer: ...
> 
> That would be
> 
>  
> https://github.com/Kitware/CMake/releases/download/v3.14.0/cmake-3.14.0-win64-x64.msi
> 
> I downloaded it and got a SHA-256 sum of
> 
>  4cbc62929f313d9890d377fa022753e9e5509e7afa3e16978127b7b2813633cf
> 
> which matches our published signatures.
> 
> What tool claims the binary contains Skeeyah?
> 
> -Brad
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [cmake-developers] Trojan in latest release

2019-03-21 Thread kevin
Linked from https://camel.org/download

Platform->windows win64-x64 installer: ...

Sent from my iPhone

> On Mar 21, 2019, at 12:20 PM, Brad King  wrote:
> 
>> On 3/21/19 12:05 PM, kevin wrote:
>> I just tried to install the latest release and noticed it contained Skeeyah.l
> 
> What is the URL of the binary you downloaded?
> What is the sha256 sum of the installer file on your local disk?
> 
> -Brad
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers


[cmake-developers] Trojan in latest release

2019-03-21 Thread kevin
I just tried to install the latest release and noticed it contained Skeeyah.l


-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [cmake-developers] Native Compilers

2017-09-26 Thread Kevin Funk
On Monday, 25 September 2017 20:39:01 CEST Ivam Pretti wrote:
> When you use cmake-gui, below the button configure  there is an option to
> choose the compiler. This compilers are alredy intalled with cmake or it
> needs to install separetely?
> 
> Another question, when you specify a for example kdevelop files is it
> necessary to run at kdevelop to get the executables files?

Heya,

Not sure if you took KDevelop just as an example, but let me clarify that the 
generator for the KDevelop project files is unmaintained (to my knowledge). 
[1]

For the latest versions of KDevelop (4.x, 5.x), it's no longer necessary to 
use this generator to import the project into this IDE. Under newer KDevelop 
you can simply import the CMake project via the user interface -- everything 
else is handled automatically.

You still need a compiler though :)

Regards,
Kevin
(one of the KDevelop maintainers)


[1] In fact, I wonder if we should just ditch that generator altogether(?)

-- 
Kevin Funk | kf...@kde.org | http://kfunk.org

signature.asc
Description: This is a digitally signed message part.
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] [PATCH] QtCreator integration: C++ includes must come first

2016-08-25 Thread Kevin Ottens
Hello,

When using the Clang Code Model in QtCreator, it turned out that having
the C system include dirs can make it report false positives for most
uses on the STL. This is due to the order the Clang Code Model looks at
the include directories and some C includes in /usr/include could be
incompatible with the used STL if found first.

For further details on how this is currently processed within QtCreator and 
how the issue shows up on my computer, you can take a look at this issue:
https://bugreports.qt.io/browse/QTCREATORBUG-16432

It got a previous fix earlier, but it looks like I am in a loophole which 
requires slight adjustment of the previous commit by Tobias Hunger.

I've been successfully using the attached patch for the last two weeks now. 
Obviously I'd like to see it merged upstream instead of having this locally 
only. It looks trivial enough to me, but please let me know if something needs 
to be changed with it which I didn't spot.

Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com

From=20017a5f63d4175a8b0853982daec99945a7374263 Mon Sep 17 00:00:00 2001
From: Kevin Ottens <er...@kde.org>
Date: Wed, 17 Aug 2016 22:45:06 +0200
Subject: [PATCH] QtCreator integration: C++ includes must come first

When using the Clang Code Model in QtCreator, it turned out that having
the C system include dirs can make it report false positives for most
uses on the STL. This is due to the order the Clang Code Model looks at
the include directories and some C includes in /usr/include could be
incompatible with the used STL if found first.
---
 Source/cmExtraCodeBlocksGenerator.cxx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Source/cmExtraCodeBlocksGenerator.cxx b/Source/cmExtraCodeBlocksGenerator.cxx
index 0ded17a..cd4b9ce 100644
--- a/Source/cmExtraCodeBlocksGenerator.cxx
+++ b/Source/cmExtraCodeBlocksGenerator.cxx
@@ -595,7 +595,7 @@ void cmExtraCodeBlocksGenerator::AppendTarget(
   includes.end());
 
 std::string systemIncludeDirs = makefile->GetSafeDefinition(
-  "CMAKE_EXTRA_GENERATOR_C_SYSTEM_INCLUDE_DIRS");
+  "CMAKE_EXTRA_GENERATOR_CXX_SYSTEM_INCLUDE_DIRS");
 if (!systemIncludeDirs.empty()) {
   std::vector dirs;
   cmSystemTools::ExpandListArgument(systemIncludeDirs, dirs);
@@ -603,7 +603,7 @@ void cmExtraCodeBlocksGenerator::AppendTarget(
 }
 
 systemIncludeDirs = makefile->GetSafeDefinition(
-  "CMAKE_EXTRA_GENERATOR_CXX_SYSTEM_INCLUDE_DIRS");
+  "CMAKE_EXTRA_GENERATOR_C_SYSTEM_INCLUDE_DIRS");
 if (!systemIncludeDirs.empty()) {
   std::vector dirs;
   cmSystemTools::ExpandListArgument(systemIncludeDirs, dirs);
-- 
2.9.2



signature.asc
Description: This is a digitally signed message part.
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] QtAutoGenerators output in Ninja

2016-07-12 Thread Kevin Funk
On Tuesday, July 12, 2016 10:43:52 AM CEST Daniel Pfeifer wrote:
> Hi,
> 
> CMake currently puts messages like "Generating moc source" into the
> buildlog. This conflicts with the convention "no output == all good".

+1

> The messages blend nicely in the colorful output of Unix Makefiles,
> but when using the Ninja generator, they create quite some noise.

Indeed.

> How can this be improved?
> * remove the messages (no output == all good)
> * add an option to silence them
> * add an option to show them and hide them per default
> * ...

While it probably still makes sense to have it for Unix Makefiles; can we just 
disable this particular output in case Ninja files are used?

After all it's just a call to `cmake -E cmake_autogen`, right? Can we 
parameterize this call?

Just my 2 ct.

Cheers,
Kevin

> Cheers, Daniel


-- 
Kevin Funk | kf...@kde.org | http://kfunk.org

signature.asc
Description: This is a digitally signed message part.
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

2016-01-14 Thread Kevin Funk
On Wednesday, January 13, 2016 10:16:44 PM Alexander Neundorf wrote:
> On Wednesday, January 13, 2016 10:16:23 Robert Dailey wrote:
> > Running version 3.2.2 on Ubuntu 15. I run the following command:
> > 
> > $ cmake .. -G"KDevelop3" -DCMAKE_C_COMPILER=gcc-4.9
> > -DCMAKE_CXX_COMPILER=g++-4.9 -DCMAKE_BUILD_TYPE=$config
> > -DCMAKE_TOOLCHAIN_FILE="../toolchains/linux_i686.toolchain.cmake"
> 
> are you sure you actually want to use the KDevelop3 generator ?
> This is for the KDE3 version, and you are probably using the KDE4 version of
> KDevelop ? For that you don't need these generated project files.
> 
> Actually I was thinking about removing this generator, because KDevelop3 is
> really really old, not sure whether it is still available in current Linux
> distributions.
> 
> Alex

+1 from my side, KDevelop 3 is super ancient (last release around 2008 
according to the interwebs). Get rid off the generator.

Cheers,
Kevin

-- 
Kevin Funk | kf...@kde.org | http://kfunk.org

signature.asc
Description: This is a digitally signed message part.
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] Assertion hit in CMake for KDevelop on Ubuntu

2016-01-13 Thread Kevin Funk
On Wednesday, January 13, 2016 12:44:59 PM Robert Dailey wrote:
> On Wed, Jan 13, 2016 at 12:36 PM, Brad King <brad.k...@kitware.com> wrote:
> > On 01/13/2016 11:16 AM, Robert Dailey wrote:
> >> Running version 3.2.2 on Ubuntu 15. I run the following command:
> > [snip]
> > 
> >> cmake: ../../Source/cmTarget.cxx:722: void
> >> cmTarget::GetSourceFiles(std::vector<std::__cxx11::basic_string
> >> 
> >>> &, const string&) const: Assertion `this->GetType() !=
> >> 
> >> INTERFACE_LIBRARY' failed.
> >> ../frontend/Core/CMake/helper-scripts/kdevelop-linux.sh: line 13:
> >> 21545 Aborted (core dumped) cmake "$DIR/../../.."
> > 
> > Please try running with CMake 3.4 or 'master' to see if it still
> > happens.  There has been substantial refactoring of this code
> > since 3.2.
> > 
> > Thanks,
> > -Brad
> 
> 3.4 isn't available to me on Ubuntu 15; do you have a custom PPA I can
> add to grab the latest CMake debian package?

There are pre-built binaries here:
  https://cmake.org/download/

I also use them on Ubuntu, no issues.

Cheers,
Kevin

-- 
Kevin Funk | kf...@kde.org | http://kfunk.org

signature.asc
Description: This is a digitally signed message part.
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] Retire expected builds

2016-01-05 Thread Kevin H. Hobbs
I'm moving to a new job, and will no longer be able to maintain my
nightly builds (even in their neglected state.)

Please expect the expected builds from bubbles, murron, and k450e to
dissapear.



signature.asc
Description: OpenPGP digital signature
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] ITK NIfTI broken Oct 6

2015-10-12 Thread Kevin H. Hobbs
On 10/12/2015 01:09 PM, Brad King wrote:
> On 10/09/2015 10:06 AM, Kevin H. Hobbs wrote:
>> The ITK dashboard builds on bubbles, murron, and k450e all started
>> failing at the configure step on October 6.
>>
>> CMake Error at
>> Modules/ThirdParty/NIFTI/src/nifti/znzlib/CMakeLists.txt:18 (install):
>>   install TARGETS given no LIBRARY DESTINATION for shared library target
>>   "znz".
> 
> Kevin, thanks for reporting this promptly.
> 

Brad,

You're welcome.

I'm sorry for my impatient cross posting to the ITK developer's list.





signature.asc
Description: OpenPGP digital signature
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] ITK NIfTI broken Oct 6

2015-10-09 Thread Kevin H. Hobbs
The ITK dashboard builds on bubbles, murron, and k450e all started
failing at the configure step on October 6.

These builds all use the development version of CMake.

There were no remarkable changes in ITK that night, however there were
some interesting updates to CMake.

The errors are in the third party library NIfTI and look like this :

CMake Error at
Modules/ThirdParty/NIFTI/src/nifti/znzlib/CMakeLists.txt:18 (install):
  install TARGETS given no LIBRARY DESTINATION for shared library target
  "znz".


CMake Error at
Modules/ThirdParty/NIFTI/src/nifti/znzlib/CMakeLists.txt:28 (install):
  install FILES given no DESTINATION!



signature.asc
Description: OpenPGP digital signature
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] Patch for write_compiler_detection_header

2015-05-06 Thread Kevin Godby
Hello.

When I tried to use the write_compiler_detection_header() function, I
got the following error:

  write_compiler_detection_header: FILE parameter missing.

Apparently on line 250 of WriteCompilerDetectionHeader.cmake, CMake
was parsing FILE as a variable instead of a string.  Wrapping FILE
in quotation marks fixed the problem.

A patched module is available via
https://github.com/godbyk/CMake/commits/fix-write-compiler-detection-header.

Please let me know if there's a better solution.

Thanks!

—Kevin Godby
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] Patch for some GUI Mac fixes

2015-01-26 Thread Kevin Wojniak
These 3 patches fix the Install menu not showing for Qt5 builds, the Install 
buttons not behaving like the other (standard) buttons, and fixes the search 
field not being shown on OS X when the window is at minimum size.



gui-mac.patch
Description: Binary data


Kevin

-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] Problems with CMake-master and OBJECT libraries

2014-04-14 Thread Kevin Funk
On Sunday 13 April 2014 11:07:21 Stephen Kelly wrote:
 Kevin Funk wrote:
  I see that there was some discussion wrt this on the cmake ML, [3], but
  actually I lack the CMake foo in order to understand this discussion's
  implications. At any rate, I don't think the above behavior is intended,
  is it?
 
 Nope, that's a bug.
 
 I've merged a fix into next for testing.
 
 Thanks,
 
 Steve.

Thanks,

note that there is also a small typo in your help text regarding CMP0051.

Watch out for STRIP_GENEX.

Cheers

-- 
Kevin Funk
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] Learning from the source

2014-04-13 Thread Kevin Ingwersen
Hello everyone! This is my first post here, so hopefuly you can understand me - 
because I am not a native english speaker! :)

As the title suggests, I wish to learn one thing or another. Currently, I am 
working on a project that has a good bunch of dependencies. They all originate 
from different build systems - Autotools, GYP, CMake - and are therefore pretty 
individual. So I have searched for a build system that works cross-platform and 
has a nice syntax that makes things look clean. Turns out I found one, forked 
it, and customized it.

But now I am stuck at the configuration part. The program can very nicely track 
dependencies and build properly. However, it has only partial integration for 
configuring (generating config.h’s for example) - and that is what I wish to 
implement. Since CMake supports things as checking for includes, libraries, and 
functions, i wanted to ask how CMake is doing this.

The reason why I ended up asking here is plain simple:
- GYP has no configuration part at all.
- Autotools looks to me like I am reading some raw certificate… AKA. I just 
can’t wrap my head around it.

Here are some references, if you need them.
- The fork of the build system in question: 
https://github.com/IngwiePhoenix/build
- The project in question: https://github.com/Deskshell-Core/PhoenixEngine

Hopefully I am right here to learn more about the rather complex task of 
probing a system for things! ^-^

Kind regards, Ingwie.
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] Problems with CMake-master and OBJECT libraries

2014-04-11 Thread Kevin Funk
Hey guys,

Recently I've started porting internal KDevelop libraries to OBJECT libraries.
The CMake code I've written seems to work fine with v2.8.12.2 (what I have on 
my system, locally) but apparently fails with recent CMake-master (which is 
installed on the KDE CI).

The error I get on the CI [1] is:


CMake Internal Error (please report a bug):
  Missing cmGeneratorTarget instance!


CMake Error at /srv/jenkins/install/linux/x86_64/g++/latest-
qt4/kde/kdelibs/inst/share/apps/cmake/modules/KDE4Macros.cmake:1010 
(add_executable):
  Error evaluating generator expression:

$TARGET_OBJECTS:kdevclangcodecompletion

  Objects of target kdevclangcodecompletion referenced but no such target
  exists.
Call Stack (most recent call first):
  /srv/jenkins/install/linux/x86_64/g++/latest-
qt4/kde/kdelibs/inst/share/apps/cmake/modules/KDE4Macros.cmake:862 
(kde4_add_executable)
  tests/CMakeLists.txt:24 (kde4_add_unit_test)


The relevant code is here: [2]

I see that there was some discussion wrt this on the cmake ML, [3], but 
actually I lack the CMake foo in order to understand this discussion's 
implications. At any rate, I don't think the above behavior is intended, is 
it?

Greets

[1] http://build.kde.org/view/kdevelop/job/kdev-clang_master/5/console
[2] 
http://quickgit.kde.org/?p=kdev-clang.gita=treehb=22e0c136a252813ff0732eba25bda79d89173682
[3] 
http://public.kitware.com/pipermail/cmake-developers/2014-February/009838.html

-- 
Kevin Funk
-- 

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 CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] Reduce output of install step

2014-02-17 Thread Kevin Burge
At Brad King's request, I am posting this here.

I opened a feature request for reducing the output of the installation
step.  I don't think it is necessary (or even helpful) to output Up to
date for targets that are up to date during the install step.  There can
only be three outcomes to the install step: a) the target is installed, b)
the target failed to be installed or updated, or c) the target is up to
date.  I think it makes the most sense to just log a message for a) and b),
not c).  If we compare this to the build step, the build step does not
notify of targets that are up to date.

We recently switched to ninja which is extremely fast.  I never noticed how
much time I spent waiting for the install MESSAGES to finish scrolling by,
until I patched cmake and noticed the difference.  When building in emacs,
or remotely, this can be a significant amount of data going over the wire
(especially for a remote desktop session) for absolutely no benefit.

Thanks for the consideration.

http://www.cmake.org/Bug/view.php?id=14757
-- 

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers