Re: [CMake] How to build a target on install (only)?
On Mon, 2015-02-16 at 09:55 -0500, David Cole wrote: Ah ha! Back to the simpler approach with install(CODE! Good idea, Nils. Then you just need a stamp/sentinel file associated with running the operation, and you can check it against your input. Aha, that works well. I don't need a sentinel file since I can just test against one of the files that dsymutil generates. And, I discovered I can have a multi-line CODE just by adding newlines into the string, so that works well. Nice! Thanks all! -- 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
Re: [cmake-developers] [PATCH] User may now specify toolset through CMake GUI
On Monday, February 16, 2015 11:35:47 AM Brad King wrote: On 02/15/2015 03:27 PM, rcdailey.li...@gmail.com wrote: From: Robert Dailey rcdai...@gmail.com The -T parameter to CMake may now be specified through QtDialog (cmake-gui) via a new text field in the first-time configure wizard (below the generator chooser). Thanks for working on this. I think QCMake::setBinaryDirectory also needs to check for CMAKE_GENERATOR_TOOLSET from an existing cache file much like it already does for CMAKE_GENERATOR. One may currently use the Add Entry button to pre-define an entry for CMAKE_GENERATOR_TOOLSET to set this from the GUI indirectly. Since not all generators support this field, we should not present it when a non-supporting generator is selected. This will need some type of query on the selected generator to be added. Thanks, -Brad In addition to Brad's comments, QCMake::deleteCache() should reset the Toolset member. Thanks, Clint -- 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] User may now specify toolset through CMake GUI
On 02/15/2015 03:27 PM, rcdailey.li...@gmail.com wrote: From: Robert Dailey rcdai...@gmail.com The -T parameter to CMake may now be specified through QtDialog (cmake-gui) via a new text field in the first-time configure wizard (below the generator chooser). Thanks for working on this. I think QCMake::setBinaryDirectory also needs to check for CMAKE_GENERATOR_TOOLSET from an existing cache file much like it already does for CMAKE_GENERATOR. One may currently use the Add Entry button to pre-define an entry for CMAKE_GENERATOR_TOOLSET to set this from the GUI indirectly. Since not all generators support this field, we should not present it when a non-supporting generator is selected. This will need some type of query on the selected generator to be added. 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
[Cmake-commits] CMake branch, next, updated. v3.2.0-rc1-363-g4607c51
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 4607c510ae328a90efd2c7af6671315251333553 (commit)
via fa8b30ebb57da8ddc3e3616c4d212811abc19335 (commit)
via aa2ba12164046cd1812c3f3b67cadca856d51846 (commit)
from 3935a0116c39fe760d7100de04e912be25985d5b (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4607c510ae328a90efd2c7af6671315251333553
commit 4607c510ae328a90efd2c7af6671315251333553
Merge: 3935a01 fa8b30e
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Feb 16 13:00:36 2015 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Feb 16 13:00:36 2015 -0500
Merge topic 'vs7-OutputDirectory' into next
fa8b30eb VS: Fix .vcproj and .vfproj file OutputDirectory generation
aa2ba121 VS: Use $(ConfigurationName) as CMAKE_CFG_INTDIR in VS 7, 8, 9
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fa8b30ebb57da8ddc3e3616c4d212811abc19335
commit fa8b30ebb57da8ddc3e3616c4d212811abc19335
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Feb 16 11:13:43 2015 -0500
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Feb 16 11:48:16 2015 -0500
VS: Fix .vcproj and .vfproj file OutputDirectory generation
Teach cmLocalVisualStudio7Generator to set 'OutputDirectory' using the
same method as is used to set the 'OutputFile' in the generated project
file. Also, OutputDirectory only needs to be set for targets that run the
linker or librarian. These two changes make the VS 7 OutputDirectory
consistent with what cmVisualStudio10TargetGenerator generates for OutDir.
Without this, since the VS Intel Fortran plugin for VS = 10 still uses
the VS 7 .vfproj file format, when executing test VSGNUFortran using
Intel Fortran Compiler 15.xx, the following warning is issued just
before compilation:
TargetPath(...) does not match the Linker's OutputFile property value
(...).
This may cause your project to build incorrectly.
To correct this, please make sure that $(OutDir), $(TargetName) and
$(TargetExt)
property values match the value specified in %(Link.OutputFile).
Subsequently, an error is reported during linking.
Inspired-by: Vincent Newsum vynew...@gmail.com
diff --git a/Source/cmLocalVisualStudio7Generator.cxx
b/Source/cmLocalVisualStudio7Generator.cxx
index 88c5284..ed560aa 100644
--- a/Source/cmLocalVisualStudio7Generator.cxx
+++ b/Source/cmLocalVisualStudio7Generator.cxx
@@ -669,8 +669,7 @@ void
cmLocalVisualStudio7Generator::WriteConfiguration(std::ostream fout,
static_castcmGlobalVisualStudio7Generator*(this-GlobalGenerator);
fout \t\tConfiguration\n
\t\t\tName=\ configName
-| gg-GetPlatformName() \\n
-\t\t\tOutputDirectory=\ configName \\n;
+| gg-GetPlatformName() \\n;
// This is an internal type to Visual Studio, it seems that:
// 4 == static library
// 2 == dll
@@ -798,6 +797,16 @@ void
cmLocalVisualStudio7Generator::WriteConfiguration(std::ostream fout,
std::string intermediateDir = this-GetTargetDirectory(target);
intermediateDir += /;
intermediateDir += configName;
+
+ if (target.GetType() cmTarget::UTILITY)
+{
+std::string const outDir =
+ target.GetType() == cmTarget::OBJECT_LIBRARY?
+ intermediateDir : target.GetDirectory(configName);
+fout \t\t\tOutputDirectory=\
+ this-ConvertToXMLOutputPathSingle(outDir.c_str()) \\n;
+}
+
fout \t\t\tIntermediateDirectory=\
this-ConvertToXMLOutputPath(intermediateDir.c_str())
\\n
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aa2ba12164046cd1812c3f3b67cadca856d51846
commit aa2ba12164046cd1812c3f3b67cadca856d51846
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Feb 16 11:11:37 2015 -0500
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Feb 16 11:48:04 2015 -0500
VS: Use $(ConfigurationName) as CMAKE_CFG_INTDIR in VS 7, 8, 9
This will allow us to use a value other than just the config name
for the project OutputDirectory setting used for $(OutDir).
Also use $(ConfigurationName) instead of $(OutDir) for the link
directory configuration suffix since that is a hard-coded instance of
a use case for CMAKE_CFG_INTDIR.
diff --git a/Help/release/dev/vs7-OutputDirectory.rst
b/Help/release/dev/vs7-OutputDirectory.rst
new file mode 100644
index 000..2725d0c
--- /dev/null
+++ b/Help/release/dev/vs7-OutputDirectory.rst
@@ -0,0 +1,10 @@
+vs7-OutputDirectory
+---
+
+* The :variable:`CMAKE_CFG_INTDIR`
Re: [cmake-developers] [PATCH] User may now specify toolset through CMake GUI
Fair points, I will make the changes. What is the recommended practice for updating patches on mailing lists? With pull requests it's easy because it picks up my changes I push to my branch automatically. I think if I push another patch to the mailing list it will start another email thread, which may cause lost context since this email chain won't be connected to the new one (not sure if that matters). Thanks Brad. On Mon, Feb 16, 2015 at 10:35 AM, Brad King brad.k...@kitware.com wrote: On 02/15/2015 03:27 PM, rcdailey.li...@gmail.com wrote: From: Robert Dailey rcdai...@gmail.com The -T parameter to CMake may now be specified through QtDialog (cmake-gui) via a new text field in the first-time configure wizard (below the generator chooser). Thanks for working on this. I think QCMake::setBinaryDirectory also needs to check for CMAKE_GENERATOR_TOOLSET from an existing cache file much like it already does for CMAKE_GENERATOR. One may currently use the Add Entry button to pre-define an entry for CMAKE_GENERATOR_TOOLSET to set this from the GUI indirectly. Since not all generators support this field, we should not present it when a non-supporting generator is selected. This will need some type of query on the selected generator to be added. 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] [ANNOUNCE] CMake 3.2.0-rc1 now ready for testing!
On 02/13/2015 01:12 PM, Robert Maynard wrote: I am proud to announce that CMake 3.2 has entered the release candidate stage. We're getting a fair number of test failures on Fedora Rawhide (with gcc 5 c++11): The following tests FAILED: 25 - FindPackageTest (Failed) 27 - StringFileTest (Failed) 44 - ObjectLibrary (Failed) 60 - ExportImport (Failed) 142 - ExternalProject (Failed) 143 - ExternalProjectLocal (Failed) 162 - Plugin (Failed) 264 - CMakeOnly.MajorVersionSelection-PythonLibs_2 (Failed) 265 - CMakeOnly.MajorVersionSelection-PythonLibs_3 (Failed) 280 - RunCMake.CMP0043 (Failed) 287 - RunCMake.CMP0054 (Failed) 292 - RunCMake.CompilerChange (Failed) 298 - RunCMake.FPHSA (Failed) 301 - RunCMake.GeneratorToolset (Failed) 308 - RunCMake.CompileFeatures (Failed) 309 - RunCMake.WriteCompilerDetectionHeader (Failed) 317 - RunCMake.build_command (Failed) 325 - RunCMake.get_property (Failed) 328 - RunCMake.include_directories (Failed) 342 - RunCMake.no_install_prefix (Failed) 344 - RunCMake.ObsoleteQtMacros (Failed) 346 - RunCMake.File_Generate (Failed) 351 - RunCMake.CommandLine (Failed) 367 - CMake.ImplicitLinkInfo (Failed) Full logs here: https://kojipkgs.fedoraproject.org//work/tasks/2902/8952902/build.log It builds fine on F22 which also has gcc 5, but not the c++11 ABI, so that seems like the likely culprit. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- 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] User may now specify toolset through CMake GUI
On 02/16/2015 11:59 AM, Robert Dailey wrote: What is the recommended practice for updating patches on mailing lists? With pull requests it's easy because it picks up my changes I push to my branch automatically. I think if I push another patch to the mailing list it will start another email thread, which may cause lost context since this email chain won't be connected to the new one (not sure if that matters). Please squash the changes and send a revised patch. You can just use the normal Reply operation in your mailer and attach the patch. You don't have to use git send-email. If you do want to use git send-email then with git format-patch you can pass -v 2 --in-reply-to='Message-ID' where Message-ID is the value of the Message-ID: ... header field in the message to which you're replying. That will keep it in the same thread. 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
[CMake] Cmake and devkitpro
Hi, I'm looking for a way to use CMake with the devkitpro toolchain ( http://sourceforge.net/projects/devkitpro/files/ ) I would like to be able to compile nds and 3ds homebrews. It is a gcc based toolchain, and users have to define DEVKITPRO and DEVKITARM env variables, giving the location of the devkitpro files. the DEVKITARM folder contains the bin and lib folders, but those platforms need specific commands to build the final files. All the rules are based on makefiles available here : https://github.com/devkitPro/buildscripts/tree/master/dkarm-eabi/rules I started by looking at the cmake toolchain stuff (CMAKE_SYSTEM_NAME, CMAKE_FIND_ROOT_PATH etc) but I don't think it will work well. Any suggestions ? -- 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
Re: [cmake-developers] GCC5 and C++11 ABI (was: CMake 3.2.0-rc1 now ready for testing)
On 02/16/2015 12:27 PM, Orion Poplawski wrote: We're getting a fair number of test failures on Fedora Rawhide (with gcc 5 c++11): It builds fine on F22 which also has gcc 5, but not the c++11 ABI, so that seems like the likely culprit. To see if this has anything to do with the way CMake itself is compiled, please add this to the end of the bootstrap command line: -- -DCMAKE_C_STANDARD=90 -DCMAKE_CXX_STANDARD=98 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] KWSys patches
I'll get the KWSys patch through. Once it is integrated into CMake then you can rebase the CMake part of the change on that. However, please revise the logic in the KWSys patch to avoid using exceptions. I've noticed that exceptions are not used but was not certain how else to handle this (and CMake at least printed out the error message before exiting - did not know that this is common code for different projects at the time). I have a few ideas but they all seem semi optimal to me so I'll need some guidance regarding this... One option would be to return empty string from Directory::GetCanonicalPath if an error occurs but currently when Glob::FindFiles returns false error checking in CMake code treats it as if no files were found so I don't think that returning false would be the way to go. Other option would be to call exit() inside the Directory::GetCanonicalPath function but I guess that this would be even worse than throwing an exception... Third option that came to mid was to return empty string Directory::GetCanonicalPath if an error occurs and simply ignore it in Glob class - since the error should occur only rarely/never and circular recursion is a corner case this is probably the best solution... One more question... When I first started writing the patch I thought about printing out a warning if circular recursion is detected but was not certain if it would be OK to just write the output to std::cerr (or the kwsys wrapper equivalent) with canonical paths that caused it. Should I leave out such message or would it be better to add it and how? Thanks, Domen -- 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] Extracting target metadata, IDE integration
On Sat, Feb 14, 2015 at 1:02 PM, Stephen Kelly steve...@gmail.com wrote: Aleix Pol wrote: Hi guys, It's been since August with this. I understand we're all busy but this step is important for KDevelop as well as for other IDE's and I wouldn't like this to rot. Please, let's keep it moving forward. As far as I'm aware, it needs to move forward from this point: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/10711/focus=12151 I'm not certain the design is finished (eg what the file should contain now or eventually). I asked for tests/documentation as a way to trigger getting the design finished. Having either would give us a list of use-cases and we would know what's in scope and what's not in scope (eg whether compile options/link options are in scope and why). I can look further into documentation, if that's what holding us back. Another question: do you have any opinion about whether this should be one global file or one file per directory? I don't know - it seems like something that might or might not be relevant for tooling. Is the size of the generated file a consideration? I think the best is to have it all in 1 directory. You don't really want to have watchers on many files over there. How well does this feature work with large projects like VTK or a combined build of LLVM/Clang/lldb/libcxx/other ll projects. I just generated the file for LLVM: https://paste.kde.org/pxl8ozwah It's a 127KiB file, I don't think it's too mental considering it's a 330 MiB repository. Aleix -- 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] creating start menu items
This seems to match what I've seen in my so-far light experimentation. What's the fix? Use wix XML patches? I'm betting my money on the WiX train as this is what we use elsewhere in my organization. Also I can live without the start menu items in the very worst case. cheers Paul On 13. feb. 2015, at 22.11, Iosif Neitzke iosif.neitzke+cm...@gmail.com wrote: As a side note, remember that CPACK_PACKAGE_EXECUTABLES is problematic in another way too; it requires listed executables to be installed to PACKAGING_INSTALL_DIR/bin/. On Fri, Feb 13, 2015 at 1:56 AM, Nils Gladitz nilsglad...@gmail.com wrote: On 02/13/2015 07:52 AM, Paul Anton Letnes wrote: I have been unable to come across any documentation on how the WiX CPack generator can create start menu items. I'll need to create items both for a few PDFs (documentation) and for an executable or two. Is this supported, or do I need to write my own XML patch file and give that to WiX? The WIX generator implements the generic CPACK_PACKAGE_EXECUTABLES [1] which like the name suggests is only for executables though. I was pondering adding another installed file property [2] for the creation of start menu / desktop shortcuts for convenience but for now CPACK_WIX_PATCH_FILE [3] should work for non-executables. Nils [1] http://www.cmake.org/cmake/help/v3.1/module/CPack.html [2] http://www.cmake.org/cmake/help/v3.1/manual/cmake-properties.7.html#properties-on-installed-files [3] http://www.cmake.org/cmake/help/v3.1/module/CPackWIX.html -- 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 -- 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
Re: [cmake-developers] KWSys patches
On 02/16/2015 02:47 PM, Domen Vrankar wrote: I've noticed that exceptions are not used but was not certain how else to handle this FYI, the proposed GetCanonicalPath already exists in KWSys as SystemTools::GetRealPath. It returns the unchanged path on error. That could be extended to take an optional second argument as a pointer to a buffer describing the error. If the argument is NULL use the current behavior. Otherwise return an empty string and populate the error info. Then make your new call sites use the new argument. One more question... When I first started writing the patch I thought about printing out a warning if circular recursion is detected but was not certain if it would be OK to just write the output to std::cerr (or the kwsys wrapper equivalent) with canonical paths that caused it. Should I leave out such message or would it be better to add it and how? Since KWSys is a library it shouldn't print anything on behalf of the application. The Glob API could also take an optional pointer to an error description buffer. 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] VS Fortran project file: Fix mismatch between OutputDirectory and OutputFile
On 02/14/2015 03:56 PM, Vincent Newsum wrote: -\t\t\tOutputDirectory=\ configName \\n; +\t\t\tOutputDirectory=\ target.GetDirectory(configName) \\n; Thanks. The OutputFile is computed differently for different target types. We also need to encode the value for XML. Furthermore the value of OutputDirectory is used for $(OutDir), and that is used as CMAKE_CFG_INTDIR. The latter should be $(ConfigurationName) instead so that we can change $(OutDir). I've fixed both problems: VS: Use $(ConfigurationName) as CMAKE_CFG_INTDIR in VS 7, 8, 9 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aa2ba121 VS: Fix .vcproj and .vfproj file OutputDirectory generation http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fa8b30eb -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] GCC5 and C++11 ABI
On 02/16/2015 11:07 AM, Brad King wrote: On 02/16/2015 12:27 PM, Orion Poplawski wrote: We're getting a fair number of test failures on Fedora Rawhide (with gcc 5 c++11): It builds fine on F22 which also has gcc 5, but not the c++11 ABI, so that seems like the likely culprit. To see if this has anything to do with the way CMake itself is compiled, please add this to the end of the bootstrap command line: -- -DCMAKE_C_STANDARD=90 -DCMAKE_CXX_STANDARD=98 Thanks, -Brad That does indeed make the tests succeed. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- 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] Extracting target metadata, IDE integration
On Monday, February 16, 2015 21:31:45 Aleix Pol wrote:
On Sat, Feb 14, 2015 at 1:02 PM, Stephen Kelly steve...@gmail.com wrote:
Aleix Pol wrote:
Hi guys,
It's been since August with this. I understand we're all busy but this
step is important for KDevelop as well as for other IDE's and I
wouldn't like this to rot.
Please, let's keep it moving forward.
As far as I'm aware, it needs to move forward from this point:
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/10711/fo
cus=12151
I'm not certain the design is finished (eg what the file should contain
now
or eventually). I asked for tests/documentation as a way to trigger
getting
the design finished. Having either would give us a list of use-cases and
we
would know what's in scope and what's not in scope (eg whether compile
options/link options are in scope and why).
I can look further into documentation, if that's what holding us back.
Another question: do you have any opinion about whether this should be one
global file or one file per directory? I don't know - it seems like
something that might or might not be relevant for tooling. Is the size of
the generated file a consideration?
I think the best is to have it all in 1 directory. You don't really
want to have watchers on many files over there.
How well does this feature work with large projects like VTK or a combined
build of LLVM/Clang/lldb/libcxx/other ll projects.
I just generated the file for LLVM: https://paste.kde.org/pxl8ozwah
It's a 127KiB file, I don't think it's too mental considering it's a
330 MiB repository.
I didn't follow the whole thread, just a few quick questions from looking at
the file:
{
name: obj2yaml,
type: EXECUTABLE,
configs: [
],
directory: /home/kde-devel/tmp/llvm/build/bin,
location: /home/kde-devel/tmp/llvm/build/bin/obj2yaml,
backtrace: [/home/kde-devel/tmp/llvm/cmake/modules/AddLLVM.cmake:452,
/home/kde-devel/tmp/llvm/cmake/modules/AddLLVM.cmake:485,
/home/kde-devel/tmp/llvm/tools/obj2yaml/CMakeLists.txt:6],
installed: true
},
I guess name is the name of the target, type, configs, location, backtrace
and installed seem to be clear.
What about directory ?
This is not the build dir where the target is defined (i.e.
cmake_binary_dir(llvm/tools/obj2yaml/), is it ?
This directory would seem useful to me, e.g. you can run make help there to
get the list of targets to compile/assemble/preprocess the files for that
target. Or you can run the clean-script for that target.
Alex
--
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] GCC5 and C++11 ABI
On 02/16/2015 02:48 PM, Brad King wrote: On 02/16/2015 04:26 PM, Orion Poplawski wrote: On 02/16/2015 11:07 AM, Brad King wrote: To see if this has anything to do with the way CMake itself is compiled, please add this to the end of the bootstrap command line: -- -DCMAKE_C_STANDARD=90 -DCMAKE_CXX_STANDARD=98 That does indeed make the tests succeed. Great. It *is* safe for you to package that way while we figure this out upstream. Thanks, -Brad Thanks, will do. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- 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] GCC5 and C++11 ABI
On 02/16/2015 04:26 PM, Orion Poplawski wrote: On 02/16/2015 11:07 AM, Brad King wrote: To see if this has anything to do with the way CMake itself is compiled, please add this to the end of the bootstrap command line: -- -DCMAKE_C_STANDARD=90 -DCMAKE_CXX_STANDARD=98 That does indeed make the tests succeed. Great. It *is* safe for you to package that way while we figure this out upstream. 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
[Cmake-commits] CMake branch, next, updated. v3.2.0-rc1-365-g6561f10
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 6561f105fe1c8c5d262c501a086afca0508ca8af (commit)
via aaad0bf35263643c42ae715ef2621a9b1fbaed72 (commit)
from 4607c510ae328a90efd2c7af6671315251333553 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6561f105fe1c8c5d262c501a086afca0508ca8af
commit 6561f105fe1c8c5d262c501a086afca0508ca8af
Merge: 4607c51 aaad0bf
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Tue Feb 17 02:39:49 2015 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 17 02:39:49 2015 -0500
Merge topic 'fix-GNU-5.0-corruption' into next
aaad0bf3 Work around bug in pre-release GNU CXX 5.0.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aaad0bf35263643c42ae715ef2621a9b1fbaed72
commit aaad0bf35263643c42ae715ef2621a9b1fbaed72
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Tue Feb 17 08:32:48 2015 +0100
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Tue Feb 17 08:33:24 2015 +0100
Work around bug in pre-release GNU CXX 5.0.
diff --git a/CompileFlags.cmake b/CompileFlags.cmake
index 3c053fa..5444062 100644
--- a/CompileFlags.cmake
+++ b/CompileFlags.cmake
@@ -72,6 +72,12 @@ if(CMAKE_SYSTEM_PROCESSOR MATCHES ^parisc)
endif()
endif()
+if (CMAKE_CXX_COMPILER_ID STREQUAL GNU AND
+NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 5.0)
+ # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65085
+ set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} -D_GLIBCXX_USE_CXX11_ABI=0)
+endif()
+
if (CMAKE_CXX_COMPILER_ID STREQUAL SunPro)
if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 5.13)
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} -std=c++03)
---
Summary of changes:
CompileFlags.cmake |6 ++
1 file changed, 6 insertions(+)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v3.2.0-rc1-353-g2134fab
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 2134fab0806beb1f0872e37ff7388e062370c476 (commit)
via c23c9083f7c349188df0067fbc685d76983d2b34 (commit)
from f0bc1843730bff040cd5bbdd09e1ccffd47ecb80 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2134fab0806beb1f0872e37ff7388e062370c476
commit 2134fab0806beb1f0872e37ff7388e062370c476
Merge: f0bc184 c23c908
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Feb 16 09:21:07 2015 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Feb 16 09:21:07 2015 -0500
Merge topic 'FindMatlab-rewrite' into next
c23c9083 FindMatlab: Hide 'reg' tool stderr output
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c23c9083f7c349188df0067fbc685d76983d2b34
commit c23c9083f7c349188df0067fbc685d76983d2b34
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Feb 16 09:18:29 2015 -0500
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Feb 16 09:18:29 2015 -0500
FindMatlab: Hide 'reg' tool stderr output
diff --git a/Modules/FindMatlab.cmake b/Modules/FindMatlab.cmake
index 3af4252..c30ca37 100644
--- a/Modules/FindMatlab.cmake
+++ b/Modules/FindMatlab.cmake
@@ -370,7 +370,9 @@
function(matlab_extract_all_installed_versions_from_registry win64 matlab_versio
execute_process(
COMMAND ${MATLAB_REG_EXE_LOCATION} query
HKEY_LOCAL_MACHINE\\SOFTWARE\\Mathworks\\MATLAB /f * /k ${APPEND_REG}
RESULT_VARIABLE resultMatlab
-OUTPUT_VARIABLE varMatlab)
+OUTPUT_VARIABLE varMatlab
+ERROR_VARIABLE errMatlab
+)
#message(Matlabs = ${varMatlab} | ${resultMatlab})
---
Summary of changes:
Modules/FindMatlab.cmake |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
Re: [CMake] How to build a target on install (only)?
On Sun, 2015-02-15 at 18:26 -0600, Iosif Neitzke wrote:
For conditional file install, you could try something like cmake -E
copy_if_different.
That won't work; I don't have any files to copy. What I want is to run
the dsymutil command during install only, not during the normal build
(because it's slow), but only if the binary that was installed has
changed.
copy_if_different won't help here.
On Sun, Feb 15, 2015 at 1:59 PM, Paul Smith p...@mad-scientist.net wrote:
install(CODE message(STATUS \Creating dSYM for ${target} in ${dir}\))
install(CODE execute_process(COMMAND dsymutil \${dir}/${target}\
OUTPUT_QUIET))
--
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
[Cmake-commits] CMake branch, master, updated. v3.2.0-rc1-159-g034f8e0
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 034f8e0bd9a2b8a319fead5042ee5782a0df03fd (commit) from ec1ec47193fcab7084e8edd977d3bebd1e8c73cb (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=034f8e0bd9a2b8a319fead5042ee5782a0df03fd commit 034f8e0bd9a2b8a319fead5042ee5782a0df03fd Author: Kitware Robot kwro...@kitware.com AuthorDate: Tue Feb 17 00:01:08 2015 -0500 Commit: Kitware Robot kwro...@kitware.com CommitDate: Tue Feb 17 00:01:08 2015 -0500 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 46d0888..6c4deca 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 2) -set(CMake_VERSION_PATCH 20150216) +set(CMake_VERSION_PATCH 20150217) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.2.0-rc1-146-g7632dae
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 7632daebd3b8378a17b302528d0690da97cb8cb5 (commit) via d891d47434a181f14554622118c39c954d6a9466 (commit) from 7747e1a7f6414e1d6308cd2b469246ed8e1a66c5 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7632daebd3b8378a17b302528d0690da97cb8cb5 commit 7632daebd3b8378a17b302528d0690da97cb8cb5 Merge: 7747e1a d891d47 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Feb 16 09:44:42 2015 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Feb 16 09:44:42 2015 -0500 Merge topic 'test-rpmbuild-cleanup' d891d474 Tests: Consolidate detection of 'rpmbuild' --- Summary of changes: Tests/CMakeLists.txt | 25 +++-- Tests/RunCMake/CMakeLists.txt |2 +- 2 files changed, 16 insertions(+), 11 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.2.0-rc1-158-gec1ec47
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via ec1ec47193fcab7084e8edd977d3bebd1e8c73cb (commit) via 116459d34fab6327906e901753611636f84a16c1 (commit) via 1c7c35c3723abfb91f5e9a986ccd4f7e70683baf (commit) via cebeed248606ba92597b7e32a5b0be1f474f7a91 (commit) via 3cfe7a4ca876c496f9b491e4175fd1c9be24f3d7 (commit) via 050958a3286f69c577fe5d03407800cbe0367898 (commit) via a77af8f1301b6a9964c1877a1893a80fbe90 (commit) via 6a22e40147b7df5285a67b63249562ecbeff112e (commit) via 0b5cf0dabd430dfe1289e865b1b51c41066338a7 (commit) via 069f2440c471e89dfe2ecf6778bbab16e9fbe491 (commit) via 67a26764b536992a966cacab4811c2d30624405c (commit) via 1cecd3a53107f7f670cf011201c1da3a33b795b6 (commit) from 7632daebd3b8378a17b302528d0690da97cb8cb5 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ec1ec47193fcab7084e8edd977d3bebd1e8c73cb commit ec1ec47193fcab7084e8edd977d3bebd1e8c73cb Merge: 7632dae 116459d Author: Brad King brad.k...@kitware.com AuthorDate: Mon Feb 16 09:44:44 2015 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Feb 16 09:44:44 2015 -0500 Merge topic 'cmListCommand-algorithms' 116459d3 cmListCommand: Avoid needlessly erasing from vectors. 1c7c35c3 cmListCommand: Replace remove duplicates loop with algorithm. cebeed24 cmAlgorithms: Add cmRemoveDuplicates algorithm. 3cfe7a4c cmListCommand: Implement REMOVE_ITEM in terms of cmRemoveMatching. 050958a3 cmAlgorithms: Add cmRemoveMatching algorithm. a77af8f1 cmListCommand: Replace joining loop with cmJoin algorithm. 6a22e401 cmListCommand: Use cmRemoveIndices for REMOVE_AT subcommand. 0b5cf0da cmAlgorithms: Implement algorithm for removing indexes. 069f2440 cmListCommand: Convert loop to find algorithm. 67a26764 cmListCommand: Implement REVERSE subcommand with std::reverse. 1cecd3a5 cmListCommand: Use std::find algorithm for FIND subcommand. --- Summary of changes: Source/cmAlgorithms.h| 91 +++ Source/cmListCommand.cxx | 120 +- 2 files changed, 123 insertions(+), 88 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.2.0-rc1-144-g7747e1a
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 7747e1a7f6414e1d6308cd2b469246ed8e1a66c5 (commit) via a2ccbffd8b4191f7b8b888fafde85eb5e7dbb2e4 (commit) from f724ab5e78ec71b22c8b5dc9e894d3feb288c620 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7747e1a7f6414e1d6308cd2b469246ed8e1a66c5 commit 7747e1a7f6414e1d6308cd2b469246ed8e1a66c5 Merge: f724ab5 a2ccbff Author: Brad King brad.k...@kitware.com AuthorDate: Mon Feb 16 09:44:40 2015 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Feb 16 09:44:40 2015 -0500 Merge topic 'wix-product-fragment' a2ccbffd CPackWIX: Extend the patching mechanism to allow adding content to Product. --- Summary of changes: Modules/CPackWIX.cmake |5 - Modules/WIX.template.in |1 + Source/CPack/WiX/cmCPackWIXGenerator.cxx | 14 +- Source/CPack/WiX/cmCPackWIXGenerator.h |4 +++- 4 files changed, 21 insertions(+), 3 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v3.2.0-rc1-360-g3935a01
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 3935a0116c39fe760d7100de04e912be25985d5b (commit) via ec1ec47193fcab7084e8edd977d3bebd1e8c73cb (commit) via 7632daebd3b8378a17b302528d0690da97cb8cb5 (commit) via 7747e1a7f6414e1d6308cd2b469246ed8e1a66c5 (commit) via f724ab5e78ec71b22c8b5dc9e894d3feb288c620 (commit) via fd8112ea7c594c8e24230f08aa8bebc6117a1cf2 (commit) via feb76254c5c9c078f0a66e27f6d5a6a964001e44 (commit) from 2134fab0806beb1f0872e37ff7388e062370c476 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3935a0116c39fe760d7100de04e912be25985d5b commit 3935a0116c39fe760d7100de04e912be25985d5b Merge: 2134fab ec1ec47 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Feb 16 09:45:00 2015 -0500 Commit: Brad King brad.k...@kitware.com CommitDate: Mon Feb 16 09:45:00 2015 -0500 Merge branch 'master' into next --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
Re: [CMake] How to build a target on install (only)?
On 02/16/2015 03:25 PM, Paul Smith wrote:
On Sun, 2015-02-15 at 18:26 -0600, Iosif Neitzke wrote:
For conditional file install, you could try something like cmake -E
copy_if_different.
That won't work; I don't have any files to copy. What I want is to run
the dsymutil command during install only, not during the normal build
(because it's slow), but only if the binary that was installed has
changed.
copy_if_different won't help here.
How about custom dependency checking?
e.g. something like:
if(${dependency} IS_NEWER_THAN ${output})
execute_process(...)
endif()
Nils
--
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
Re: [CMake] How to build a target on install (only)?
Ah ha! Back to the simpler approach with install(CODE!
Good idea, Nils.
Then you just need a stamp/sentinel file associated with running the
operation, and you can check it against your input.
For your comment line, you could use cmake -E echo to spit out a
comment before running the dSYM tool, and for your stamp files, after
the operation is done, you can use cmake -E touch to update the time
stamp on the sentinel files.
D
On Mon, Feb 16, 2015 at 9:49 AM, Nils Gladitz nilsglad...@gmail.com wrote:
On 02/16/2015 03:25 PM, Paul Smith wrote:
On Sun, 2015-02-15 at 18:26 -0600, Iosif Neitzke wrote:
For conditional file install, you could try something like cmake -E
copy_if_different.
That won't work; I don't have any files to copy. What I want is to run
the dsymutil command during install only, not during the normal build
(because it's slow), but only if the binary that was installed has
changed.
copy_if_different won't help here.
How about custom dependency checking?
e.g. something like:
if(${dependency} IS_NEWER_THAN ${output})
execute_process(...)
endif()
Nils
--
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
Re: [cmake-developers] KWSys patches
On 02/15/2015 03:04 PM, Domen Vrankar wrote: I tried to register to http://review.source.kitware.com so that I would be able to commit patches to KWSys repository but after I put in my OpenID I got a Not Found error. I'll be in touch off-list about this. How can I contribute this patch? Attached are KWSys patch and KWSys+CMake patch. I'll get the KWSys patch through. Once it is integrated into CMake then you can rebase the CMake part of the change on that. However, please revise the logic in the KWSys patch to avoid using exceptions. 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] How to build a target on install (only)?
The other way you could approach this, but which would not be as
simple would be to invent *your own* custom install target
(install_with_dSYM, or whatever name makes sense to you). Then you
could have that target depend on all the custom targets that build the
dSYM files. When you build this custom install_with_DSYM target, it
would first build all the dSYM files via add_custom_command rules, and
*then* run the same command that make install runs to install all
the other files. Or vice versa, if the dSYM needs to be run on stuff
in the install tree...
HTH,
D
On Mon, Feb 16, 2015 at 9:25 AM, Paul Smith p...@mad-scientist.net wrote:
On Sun, 2015-02-15 at 18:26 -0600, Iosif Neitzke wrote:
For conditional file install, you could try something like cmake -E
copy_if_different.
That won't work; I don't have any files to copy. What I want is to run
the dsymutil command during install only, not during the normal build
(because it's slow), but only if the binary that was installed has
changed.
copy_if_different won't help here.
On Sun, Feb 15, 2015 at 1:59 PM, Paul Smith p...@mad-scientist.net wrote:
install(CODE message(STATUS \Creating dSYM for ${target} in ${dir}\))
install(CODE execute_process(COMMAND dsymutil \${dir}/${target}\
OUTPUT_QUIET))
--
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
