[cmake-developers] [CMake 0014967]: VS 2005 Generator for OBJECT target create name.rc.res object but the compiler generates name.res files
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14967 == Reported By:Javier Assigned To: == Project:CMake Issue ID: 14967 Category: CMake Reproducibility:always Severity: major Priority: normal Status: new == Date Submitted: 2014-06-10 09:59 EDT Last Modified: 2014-06-10 09:59 EDT == Summary:VS 2005 Generator for OBJECT target create name.rc.res object but the compiler generates name.res files Description: When I add an OBJECT target with an .rc file, the VS2005 generator adds the following in the .vcproj file: File RelativePath=something\BuildDLL.rc FileConfiguration Name=Debug|Win32 Tool Name=VCResourceCompilerTool ObjectFile=$(IntDir)/BuildDLL.rc.res / However, when building this target in VS, BuildDLL.rc is compiled into BuildDLL.res, so build fails because it can't find BuildDLL.rc.res. Steps to Reproduce: 1) Create an OBJECT target with a resource file, ie name.rc. 2) Generate a solution with VS2005 geneartor. 3) Build. == Issue History Date ModifiedUsername FieldChange == 2014-06-10 09:59 Javier New 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/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] add_compile_options and link flags
On 06/10/2014 11:15 AM, Steve Wilson wrote: https://github.com/swwilso1/CMake the LinkOptionsCommand topic isn't there yet. I will try and get those uploaded today and post when they are available. Great, 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/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] add_compile_options and link flags
My apologies, I was out ill yesterday. I have a CMake repo on github that contains work in progress. I still haven’t had time to return to work on these issues, but hopefully will soon. https://github.com/swwilso1/CMake However, I need to sync the dev branches with the current master branch and the LinkOptionsCommand topic isn’t there yet. I will try and get those uploaded today and post when they are available. Steve On Jun 9, 2014, at 9:55 AM, Brad King brad.k...@kitware.com wrote: Steve W, On 06/09/2014 11:46 AM, Brad King wrote: See thread here: push of LinkOptionsCommand topic branch http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/9203 IIRC there were a couple of minor unresolved issues but it is mostly just waiting for someone to have time to take it to completion. Do you have this branch published anywhere currently? Others may be interested in picking it up. If you don't want to publish it persistently anywhere you can always post a patch series here with the current work-in-progress. Thanks, -Brad signature.asc Description: Message signed with OpenPGP using GPGMail -- 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
Re: [cmake-developers] Compiler features/extensions remaining/future issues
David Cole wrote: I'm seeing considerable performance impact of this feature, even when it isn't used: Can you create an sscce? Sounds like just downloading ParaView, ITK or Slicer, and configuring it with CMake is the reproduce case. How much simpler and more stand-alone do you want it to be? I think http://sscce.org/ explains is quite well. I want to avoid having to understand all of the ParaView CMake code and that of its dependencies, and whether python bindings need to be enabled etc. Ben, can you run your timing test with a commit before my topic and after it? Timing tests with master and your extra topics don't tell us anything on this question. Thanks, Steve. -- 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] [PATCH] Fix ProcessorCount for HPUX 11iv3
A patch to fix obtaining the number of processors in the modified output of the machinfo command for HPUX 11iv3 (at least for IA64) is attached. Eric 0001-Fix-ProcessorCount-for-HPUX-11iv3.patch Description: Binary data -- 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
Re: [cmake-developers] Compiler features/extensions remaining/future issues
Stephen Kelly wrote: Here is a dump of some notes I have accumulated regarding compile features. Any comments on the rest of this? Thanks, Steve. -- 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
Re: [cmake-developers] Compiler features/extensions remaining/future issues
On 6/10/2014 11:30 AM, Stephen Kelly wrote: I think http://sscce.org/ explains is quite well. I want to avoid having to understand all of the ParaView CMake code and that of its dependencies, and whether python bindings need to be enabled etc. The real problem is that we need to have some regression tests in CMake that test for these types of performance issues. Right now we don't have them. Creating a SSCCE for the issues we are seeing would be doing just that. However, right now we know there are issues with ParaView. It might not be too much to ask for you to give it a quick try. I am sure Ben could give you the -D options for CMake since ParaView is pretty self contained. I think basically building ParaView with Python wrapping shows the issue. So, you will need python installed and they Ben, can you run your timing test with a commit before my topic and after it? Timing tests with master and your extra topics don't tell us anything on this question. Do you think you could try ParaView and if you run into trouble give up on it. However, I would hope it would involve a git clone, and a cmake -DPARAVIEW_ENABLE_PYTHON=TRUE ../ParaViewSrc In the mean time, I will see if we can work on trying to create some better regression tests for CMake performance. Thanks. -Bill -- 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
Re: [cmake-developers] Compiler features/extensions remaining/future issues
On Tue, Jun 10, 2014 at 17:30:24 +0200, Stephen Kelly wrote: I want to avoid having to understand all of the ParaView CMake code and that of its dependencies, and whether python bindings need to be enabled etc. Well, there isn't much you need to grok from the code there; it's just a project with lots of targets with lots of interdependencies. When adding compile features, the time drops noticeably. Brad, Rob, and I looked at the code and performance output today and it looks like it is the evaluation of the generator expressions made to find the compile features, compile options, and compile definitions that takes a long time. *Each* takes ~10% of overall time and the projects I'm testing don't use the interface propagation features *at all*. It's the evaluation of the generated genex that takes a long time (parsing is now inconsequential). Using debugging messages shows that the evaluations are being cached, but that probably only saves us from even more slowdowns. Brad is going to take a deeper look at it and might have more information in the next few days. Ben, can you run your timing test with a commit before my topic and after it? Timing tests with master and your extra topics don't tell us anything on this question. Will do. Should be done in an hour or two. I'm using commits b56a9ae (before) and 593b69c (after): commit b56a9ae7f14189fd2bce2ca3e9441060ca231638 Merge: 593b69c 9eaf375 Author: Brad King brad.k...@kitware.com Date: Tue Apr 15 10:32:11 2014 -0400 Merge topic 'target_compile_features' 9eaf3755 Export: Populate INTERFACE_COMPILE_FEATURES property. 8ed59fc2 Add target_compile_features command. 4e6ca504 cmTargetPropCommandBase: Change the interface to return bool. 5412dede cmTarget: Transitively evaluate compiler features. baff4434 cmTarget: Allow populating COMPILE_FEATURES using generator expressions. f97bf437 Features: Add cxx_auto_type. 03355d6b cmTarget: Add COMPILE_FEATURES target property. faeddf64 project: Add infrastructure for recording CXX compiler features 913394af cmTarget: Add CXX_STANDARD and CXX_EXTENSION target properties. 8238a6cd Add some COMPILE_OPTIONS for specifying C++ dialect. 892243fc Tests: Require CMake 3.0 for the SystemInformation test. 59b5fdd3 Don't load Clang-CXX from AppleClang-CXX. commit 593b69c9dc9e692b198f1ddbf9251130e61a4679 Merge: 33358fd 941a140 Author: Brad King brad.k...@kitware.com Date: Tue Apr 15 10:22:41 2014 -0400 Merge topic 'aix-no-sstream' 941a1404 AIX: fix compilation error because of missing sstream --Ben -- 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
Re: [cmake-developers] Compiler features/extensions remaining/future issues
On 06/10/2014 12:09 PM, Stephen Kelly wrote: Stephen Kelly wrote: Here is a dump of some notes I have accumulated regarding compile features. Any comments on the rest of this? Someday perhaps ;) My main concern beyond the performance side right now is getting the features populated for VS = 10. Then we will have the most popular compilers on Linux, OS X, and Windows covered. -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/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] Fix ProcessorCount for HPUX 11iv3
On 06/10/2014 11:46 AM, Eric Berge wrote: A patch to fix obtaining the number of processors Applied, thanks: ProcessorCount: Update for HPUX 11iv3 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dbc0f63d -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/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Compiler features/extensions remaining/future issues
On Tue, Jun 10, 2014 at 13:17:57 -0400, Ben Boeckel wrote: Will do. Should be done in an hour or two. I'm using commits b56a9ae (before) and 593b69c (after): Attached. --Ben Running cmake build after-features from cmake-after-features... Running tests for paraview... Running make test 1... XX Timing of configure: 28.4797 XX Timing of generate: 39.1605 Running make test 2... XX Timing of configure: 28.0603 XX Timing of generate: 39.6021 Running make test 3... XX Timing of configure: 28.1262 XX Timing of generate: 39.3873 Running ninja test 1... XX Timing of configure: 28.1178 XX Timing of generate: 71.5787 Running ninja test 2... XX Timing of configure: 28.2574 XX Timing of generate: 70.8935 Running ninja test 3... XX Timing of configure: 28.9053 XX Timing of generate: 70.6467 Running tests for slicer... Running make test 1... XX Timing of configure: 9.53432 XX Timing of generate: 62.4838 Running make test 2... XX Timing of configure: 9.3675 XX Timing of generate: 62.4657 Running make test 3... XX Timing of configure: 9.35078 XX Timing of generate: 62.2783 Running ninja test 1... XX Timing of configure: 9.44152 XX Timing of generate: 74.656 Running ninja test 2... XX Timing of configure: 9.28958 XX Timing of generate: 74.7592 Running ninja test 3... XX Timing of configure: 9.33024 XX Timing of generate: 75.25 Running tests for sprokit... Running make test 1... XX Timing of configure: 3.01892 XX Timing of generate: 3.59591 Running make test 2... XX Timing of configure: 2.9013 XX Timing of generate: 3.44985 Running make test 3... XX Timing of configure: 2.96652 XX Timing of generate: 3.48186 Running ninja test 1... XX Timing of configure: 3.01794 XX Timing of generate: 1.20835 Running ninja test 2... XX Timing of configure: 2.95976 XX Timing of generate: 1.19672 Running ninja test 3... XX Timing of configure: 2.95632 XX Timing of generate: 1.19099 Running cmake build before-features from cmake-before-features... Running tests for paraview... Running make test 1... XX Timing of configure: 28.6817 XX Timing of generate: 35.5692 Running make test 2... XX Timing of configure: 28.3886 XX Timing of generate: 35.6613 Running make test 3... XX Timing of configure: 28.0809 XX Timing of generate: 35.6549 Running ninja test 1... XX Timing of configure: 28.1364 XX Timing of generate: 67.8352 Running ninja test 2... XX Timing of configure: 28.2551 XX Timing of generate: 67.2962 Running ninja test 3... XX Timing of configure: 28.7813 XX Timing of generate: 66.6906 Running tests for slicer... Running make test 1... XX Timing of configure: 8.91568 XX Timing of generate: 54.8089 Running make test 2... XX Timing of configure: 9.00928 XX Timing of generate: 54.9421 Running make test 3... XX Timing of configure: 8.93402 XX Timing of generate: 54.8247 Running ninja test 1... XX Timing of configure: 8.89655 XX Timing of generate: 67.4797 Running ninja test 2... XX Timing of configure: 8.90781 XX Timing of generate: 67.2723 Running ninja test 3... XX Timing of configure: 8.98565 XX Timing of generate: 67.2085 Running tests for sprokit... Running make test 1... XX Timing of configure: 3.00015 XX Timing of generate: 3.65421 Running make test 2... XX Timing of configure: 2.94023 XX Timing of generate: 3.4586 Running make test 3... XX Timing of configure: 2.87959 XX Timing of generate: 3.43462 Running ninja test 1... XX Timing of configure: 3.40615 XX Timing of generate: 1.28768 Running ninja test 2... XX Timing of configure: 2.91383 XX Timing of generate: 1.18895 Running ninja test 3... XX Timing of configure: 2.94707 XX Timing of generate: 1.19735 -- 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] [ANNOUNCE] CMake 3.0.0 Released.
On behalf of myself, Ken, Bill, Brad, David, Alex, Eike, Steve, Zach, Ben, Peter, Nils, and the rest of the CMake team from all around the world, we are pleased to announce that CMake 3.0.0 is now available for download at: http://www.cmake.org/files/v3.0/?C=M;O=D Documentation is available at: http://www.cmake.org/cmake/help/v3.0 Full release notes are published at http://www.cmake.org/cmake/help/v3.0/release/3.0.0.html Some of the more significant features of CMake 3.0 are: * Compatibility options supporting code written for CMake versions prior to 2.4 have been removed. * The CMake language has been extended with *Bracket Argument* and *Bracket Comment* syntax inspired by Lua long brackets. * The CMake documentation has been converted to reStructuredText and uses Sphinx generation. * Generators for Visual Studio 10 (2010) and later were renamed to include the product year like generators for older VS versions: * Visual Studio 10 - Visual Studio 10 2010 * Visual Studio 11 - Visual Studio 11 2012 * Visual Studio 12 - Visual Studio 12 2013 This clarifies which generator goes with each Visual Studio version. The old names are recognized for compatibility. * A new CodeLite extra generator is available for use with the Makefile or Ninja generators. * A new Kate extra generator is available for use with the Makefile or Ninja generators. * The add_library() command learned a new INTERFACE library type. Interface libraries have no build rules but may have properties defining usage requirements and may be installed, exported, and imported. This is useful to create header-only libraries that have concrete link dependencies on other libraries. * The export() command learned a new EXPORT mode that retrieves the list of targets to export from an export set configured by the install(TARGETS) command EXPORT option. This makes it easy to export from the build tree the same targets that are exported from the install tree. * The project() command learned to set some version variables to values specified by the new VERSION option or to empty strings. See policy CMP0048. * Several long-outdated commands that should no longer be called have been disallowed in new code by policies: * Policy CMP0029 disallows subdir_depends() * Policy CMP0030 disallows use_mangled_mesa() * Policy CMP0031 disallows load_command() * Policy CMP0032 disallows output_required_files() * Policy CMP0033 disallows export_library_dependencies() * Policy CMP0034 disallows utility_source() * Policy CMP0035 disallows variable_requires() * Policy CMP0036 disallows build_name() Bug tracker change log page for 3.0.0 is at: http://public.kitware.com/Bug/changelog_page.php?version_id=112 -- 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
