[cmake-developers] [PATCH] fixed msvc 64 bit build
This is just a one-char-bugfix, WIN32 instead of _WIN32 macro was used. Sorry if I should have opened up a ticket in mantis before posting here. Just didn't know what would be correct order. Are there any regular Win64 builds done actually? I'm just curious if there is anyone else using 64bit versions of CMake on Windows ... Best regards Michael Stürmer 0001-fixed-msvc-64-bit-build.patch Description: 0001-fixed-msvc-64-bit-build.patch -- 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] [CMake 0015617]: When assembler is enabled TI Compiler might end up with wrong archiver
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15617 == Reported By:Florian Reinhard Assigned To: == Project:CMake Issue ID: 15617 Category: Modules Reproducibility:always Severity: major Priority: normal Status: new == Date Submitted: 2015-06-15 08:43 EDT Last Modified: 2015-06-15 08:43 EDT == Summary:When assembler is enabled TI Compiler might end up with wrong archiver Description: If ENABLE(ASM) is used in a TI-Toolchain project and something named ar(.exe) is present in your path, this archiver (ar) will be used and not the TI toolchain's ar6x! Here's why: CMakeDetermineCCompiler.cmake (line 153, [1]) and CMakeDetermineCXXCompiler.cmake have some special code/regex to get the toolchain prefix and suffix. CMakeDetermineASMCompiler.cmake does not contain this code. What happeens? - The ASM Compiler is processed, pre- and suffix are empty. - CMakeFindBinUtils.cmake is processed and CMAKE_AR is filled witht he wrong archiver - Subsequent languages (c/cxx) will not overwrite the wrong CMAKE_AR setting. Steps to Reproduce: I managed to reproduce this easily on multiple machines (all windows): 1. Get a regular archiver named ar in your path. On windows something named ar.exe should do the trick 2. setup a project that uses the TI Toolchain 3. use ENABLE(ASM) in yourproject Additional Information: [1] http://www.cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CMakeDetermineCCompiler.cmake;h=937aa8c3efe6a83acbc751aee527b7409f68b300;hb=refs/heads/master#l153 == Issue History Date ModifiedUsername FieldChange == 2015-06-15 08:43 Florian ReinhardNew Issue == -- 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] Add command line options for deprecation message control
On 06/13/2015 01:41 PM, Michael Scott wrote: I've implemented some changes to cmake.cxx and cmake.h, to implement setting the CMAKE_ERROR_DEPRECATED and CMAKE_WARN_DEPRECATED variables via command line options, for the Mantis issue 0014669, in a generic GCC style pattern. I've attached the proposed patch to this email, does this look like a sensible implementation? Thanks for working on this. Here are some comments: * Please use 2 spaces and no tabs for indentation. * Please extend Tests/RunCMake/CommandLine to cover this or find another appropriate test to update. All options need coverage, including the error cases. * The cmHasLiteralPrefix helper function may be useful in place of x.find(...) == 0. Thanks, -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: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Problems when creating config files and add_dependencies
On 06/12/2015 07:19 AM, Roman Wüger wrote: It would be great if generator expressions can be used with configure_file to avoid such overhead. Does anyone have an idea on how to solve that? See file(GENERATE). -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: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Custom commands with Ninja on Windows
On 06/12/2015 06:01 AM, Florent Castelli wrote: So I've been thinking that on Windows, instead of concatenating everything, we should be a script that is run using a response file that just runs all the command with error checking. Eventually, we could reuse cmLocalVisualStudioGenerator::ConstructScript() for that matter. Yes, I think that would be a reasonable approach. Thanks, -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: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] fixed msvc 64 bit build
On 06/15/2015 07:58 AM, Stuermer, Michael SP/HZA-ZSEP wrote: This is just a one-char-bugfix, WIN32 instead of _WIN32 macro was used. Thanks. There are several instances of this in Source/*. I've fixed the one you pointed out and more: Fix preprocessor checks WIN32 = _WIN32 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=83af11d4 There is one other in Source/kwsys that I've fixed in upstream KWSys: http://review.source.kitware.com/19926 and will integrate back to CMake after testing there. Are there any regular Win64 builds done actually? Yes. We have nightly testing for it which has been clean. It is also my main Windows development architecture. The WIN32 symbol is normally defined by CMAKE_CXX_FLAGS if the default flags are used for MSVC. How did you configure the build? -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: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generator expressions for output directory/name (and install?)
On 06/12/2015 10:19 AM, Robert Goulet wrote: Here's the updated patch file with tests added. Thanks. Please also update Tests/ExportImport/Import to verify that the files are installed correctly. The test case needs to fail if it were run without the rest of your changes. Also please extend the Help/*/*.rst documentation to cover where generator expressions are now supported. Thanks, -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: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generator expressions for output directory/name (and install?)
Updated with improved tests and added docs. -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Monday, June 15, 2015 10:17 AM To: Robert Goulet Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] Generator expressions for output directory/name (and install?) On 06/12/2015 10:19 AM, Robert Goulet wrote: Here's the updated patch file with tests added. Thanks. Please also update Tests/ExportImport/Import to verify that the files are installed correctly. The test case needs to fail if it were run without the rest of your changes. Also please extend the Help/*/*.rst documentation to cover where generator expressions are now supported. Thanks, -Brad more-generator-expressions.patch Description: more-generator-expressions.patch -- 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] Custom commands with Ninja on Windows
Alright, I'll see what I can do when I find some free time to work on this then! /Florent On Mon, Jun 15, 2015 at 3:14 PM, Brad King brad.k...@kitware.com wrote: On 06/12/2015 06:01 AM, Florent Castelli wrote: So I've been thinking that on Windows, instead of concatenating everything, we should be a script that is run using a response file that just runs all the command with error checking. Eventually, we could reuse cmLocalVisualStudioGenerator::ConstructScript() for that matter. Yes, I think that would be a reasonable approach. Thanks, -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: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Compact dependency graph
So here is the patch with tests and passing the git hooks. Rgds Richard Am Dienstag, den 02.06.2015, 16:46 -0400 schrieb Brad King: On 06/02/2015 04:09 PM, Richard Ulrich wrote: thanks for looking into it. The revised version is on github and in the attachement. Thanks. Please rebase -i and squash everything down to one commit. We don't need to review work-in-progress commits. Thanks, -Brad From 763f5a70201e15aaf59a22afbb5d03c5dbdbf87d Mon Sep 17 00:00:00 2001 From: Richard Ulrich ri...@paraeasy.ch Date: Wed, 20 May 2015 22:32:59 +0200 Subject: [PATCH] Adding regex replace rules for the node names in the dependency graph. #14163 This allows to strip the path from external library names. It can also be used to group different files from the same library group into a common node. --- Modules/CMakeGraphVizOptions.cmake | 16 ++ Source/CMakeLists.txt | 2 + Source/cmGraphVizWriter.cxx| 60 ++- Source/cmGraphVizWriter.h | 3 + Source/cmRegexTools.cxx| 183 + Source/cmRegexTools.h | 65 Source/cmStringCommand.cxx | 135 ++- Source/cmStringCommand.h | 10 -- Tests/RunCMake/CMakeLists.txt | 1 + Tests/RunCMake/CommandLineGraphviz/CMakeLists.txt | 3 + .../CMakeGraphVizOptions.cmake | 7 + .../graphviz_filter_even/CMakeLists.txt| 3 + .../graphviz_filter_even/RunCMakeTest.cmake| 4 + .../graphviz_filter_even/expected.dot | 13 ++ .../graphviz_filter_even-check.cmake | 16 ++ .../graphviz_filter_even-result.txt| 1 + .../graphviz_filter_even-stderr.txt| 0 .../graphviz_filter_even.cmake | 0 .../CMakeGraphVizOptions.cmake | 6 + .../graphviz_filter_uneven/CMakeLists.txt | 3 + .../graphviz_filter_uneven/RunCMakeTest.cmake | 4 + .../graphviz_filter_uneven-stderr.txt | 1 + .../graphviz_filter_uneven.cmake | 3 + .../graphviz_no_filter/CMakeGraphVizOptions.cmake | 3 + .../graphviz_no_filter/CMakeLists.txt | 3 + .../graphviz_no_filter/RunCMakeTest.cmake | 4 + .../graphviz_no_filter/expected.dot| 15 ++ .../graphviz_no_filter-check.cmake | 16 ++ .../graphviz_no_filter-result.txt | 1 + .../graphviz_no_filter-stderr.txt | 0 .../graphviz_no_filter/graphviz_no_filter.cmake| 0 Tests/RunCMake/CommandLineGraphviz/libs.cmake | 24 +++ Tests/RunCMake/CommandLineGraphviz/myapp.cpp | 7 + Tests/RunCMake/CommandLineGraphviz/vendor_lib1.cpp | 6 + Tests/RunCMake/CommandLineGraphviz/vendor_lib2.cpp | 6 + 35 files changed, 487 insertions(+), 137 deletions(-) create mode 100644 Source/cmRegexTools.cxx create mode 100644 Source/cmRegexTools.h create mode 100644 Tests/RunCMake/CommandLineGraphviz/CMakeLists.txt create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_even/CMakeGraphVizOptions.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_even/CMakeLists.txt create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_even/RunCMakeTest.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_even/expected.dot create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_even/graphviz_filter_even-check.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_even/graphviz_filter_even-result.txt create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_even/graphviz_filter_even-stderr.txt create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_even/graphviz_filter_even.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_uneven/CMakeGraphVizOptions.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_uneven/CMakeLists.txt create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_uneven/RunCMakeTest.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_uneven/graphviz_filter_uneven-stderr.txt create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_filter_uneven/graphviz_filter_uneven.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_no_filter/CMakeGraphVizOptions.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_no_filter/CMakeLists.txt create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_no_filter/RunCMakeTest.cmake create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_no_filter/expected.dot create mode 100644 Tests/RunCMake/CommandLineGraphviz/graphviz_no_filter/graphviz_no_filter-check.cmake create mode 100644
Re: [cmake-developers] [CMake] Virtual folders in Visual studio get expanded on reload
I think I have seen this behavior in pure (non-CMake-generated) VS projects... Perhaps it's simply a Visual Studio issue, and has nothing to do with CMake. D On Fri, Jun 12, 2015 at 7:55 AM, Roman Wüger roman.wue...@gmx.at wrote: @kgt: Thank you for this great hint. :-) I had overlooked this button in Visual Studio @mjklaim: I didn't see this behavior in older CMake versions. Roman -Ursprüngliche Nachricht- Von: Thompson, KT [mailto:k...@lanl.gov] Gesendet: Dienstag, 02. Juni 2015 15:52 An: Roman Wüger; CMake MailingList Betreff: RE: [cmake-developers] Virtual folders in Visual studio get expanded on reload Roman, I have the same complaint. My project has about 300 targets arranged in two dozen folders. I use the collapse all button in Visual Studio's Solution Explorer window (looks like a stack of 3 squares in VS2013). kt -Original Message- From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of Roman Wüger Sent: Monday, June 01, 2015 5:00 PM To: CMake Developer MailingList; CMake MailingList Subject: [cmake-developers] Virtual folders in Visual studio get expanded on reload Hi, I noticed that sometimes when a target is reloaded, that the virtual folders and targets for the complete visual studio solution get expanded. For a small project this isn't a problem, but in a large project (~ 100 targets) this is a really big problem to close all targets every time. Did anybody noticed this behavior and has a solution for it? Thanks Best Regards Roman -- 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 -- 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 -- 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] CMake Build RPM for Centos/RHEL
Hi,
On my Continuous Integration (Jenkins), I'm creating a job to build (and
provide) the latest version of CMake.
Bill Hoffman kindly answered to my email and helped me to build the RPM.
Here is my script:
$ VERSION=3.2.2
$ RPM_RELEASE=0.el6
$ #
$ wget http://www.cmake.org/files/v3.2/cmake-${VERSION}.tar.gz
$ tar -xf cmake-*.tar.gz
$ cd cmake-${VERSION}
$ ./configure --prefix=/usr/local
$ gmake
$ ./bin/cpack -G RPM -D CPACK_RPM_PACKAGE_RELEASE=${RPM_RELEASE}
I have few questions:
1. What are the requirements/build procedure for the actual distro?
2. Is there a way to generate a RPM with standard name:
I mean, something like: cmake-3.2.3-1.el6.x86_64.rpm
Instead of: cmake-3.2.3-Linux-x86_64.rpm
3. I tried what I built, but:
CMake Error: Could not find CMAKE_ROOT !!!
CMake has most likely not been installed correctly.
Modules directory not found in
/usr/share/cmake-3.2
CMake Error: Error executing cmake::LoadCache(). Aborting.
Problem is that the created directory exists but it can't be read
because of permissions: drwxr-x---.
In advance, many thanks for your time and your help,
Jean
_
This message may contain confidential information and is intended for specific
recipients unless explicitly noted otherwise. If you have reason to believe you
are not an intended recipient of this message, please delete it and notify the
sender. This message may not represent the opinion of Euronext N.V. or any of
its subsidiaries or affiliates, and does not constitute a contract or
guarantee. Unencrypted electronic mail is not secure and the recipient of this
message is expected to provide safeguards from viruses and pursue alternate
means of communication where privacy or a binding message is desired.
--
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
