[cmake-developers] CTestCoverageCollectGCOV and ctest_submit(CDASH_UPLOAD)

2015-02-23 Thread Nils Gladitz
Hi, I saw ctest_submit(CDASH_UPLOAD)signature and the CTestCoverageCollectGCOV module being added to CMake. I was wondering how these differ in functionality from the old ctest_coverage() and ctest_upload(FILES). Specifically I couldn't tell from the existing documentation what new use

Re: [cmake-developers] CTestCoverageCollectGCOV and ctest_submit(CDASH_UPLOAD)

2015-02-23 Thread Bill Hoffman
On 2/23/2015 9:47 AM, Brad King wrote: Specifically I couldn't tell from the existing documentation what new use cases or features the new implementations support. Currently it is just a different implementation of the same use cases. However, logic for processing the gcov output moves from

Re: [cmake-developers] CTestCoverageCollectGCOV and ctest_submit(CDASH_UPLOAD)

2015-02-23 Thread Brad King
On 02/23/2015 07:52 AM, Nils Gladitz wrote: I was wondering how these differ in functionality from the old ctest_coverage() and ctest_upload(FILES). Specifically I couldn't tell from the existing documentation what new use cases or features the new implementations support. Currently it is

Re: [cmake-developers] cmake install command expected performance?

2015-02-23 Thread Nils Gladitz
On 02/23/2015 04:13 PM, Robert Goulet wrote: I’m running into an issue were using the CMake install command to copy a directory with over 5000+ files (slightly over 1GB of data) takes a lot more time than doing a simple copy. On an SSD drive it takes 0.2 seconds to copy, while it takes about 56+

Re: [cmake-developers] cmake install command expected performance?

2015-02-23 Thread Robert Goulet
We deleted the destination folder every time we did a test. And it's an SSD drive, I don't think having files in cache would be the issue. When files are already there it still takes 30+ seconds for cmake to not copy the files. -Original Message- From: Nils Gladitz

Re: [cmake-developers] [PATCH 0/3] CPACK_RPM_PACKAGE_ARCHITECTURE

2015-02-23 Thread Brad King
On 02/21/2015 09:39 AM, Domen Vrankar wrote: 2015-02-19 9:01 GMT+01:00 Joshua A Clayton stillcompil...@gmail.com: This patch series extends CPackRPM to support cross-built rpms Previously only native and noarch rpms were possible. Other architecture choices resulted in an error from rpmbuild.

Re: [cmake-developers] [vc12/idl] output directory problem

2015-02-23 Thread Brad King
On 02/21/2015 07:58 AM, Tim Blechmann wrote: i'd love to provide a reduced test case, though i can only reproduce this in a complex real-world buildsystem, with dozens of libraries and some include_external_msproject / add_dependencies pairs ... [snip] that said, i wonder: why would it be ok

Re: [cmake-developers] COMPILE_LANGUAGE generator expression

2015-02-23 Thread Brad King
On 02/22/2015 01:21 PM, Stephen Kelly wrote: Is there any updated knowledge since http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/6844/focus=6855 AFAICT nothing has changed, except: I saw commit 06e527b3 (Merge topic 'xcode-flags-per-language', 2015-02-10) go in

Re: [cmake-developers] Object library linking (and a bit about INTERFACE_SOURCES)

2015-02-23 Thread Stephen Kelly
Ben Boeckel wrote: Hi, I have a branch on my Github fork to support object library linking: object-library-linking https://github.com/mathstuf/CMake/tree/object-library-linking Thanks for working on this. There is also a commit which updates usage of $TARGET_OBJECTS to not

Re: [cmake-developers] Object library linking (and a bit about INTERFACE_SOURCES)

2015-02-23 Thread Ben Boeckel
On Mon, Feb 23, 2015 at 21:05:01 +0100, Stephen Kelly wrote: Is there a reason to disallow that? We might guess it will be possible to install object libraries in the future. We could also lift the restriction then. I'm fine with just dropping the patch. Basically without it, all it blocks is