Re: [cmake-developers] Using -g3 in Debug config?

2013-11-12 Thread Brad King
On 11/12/2013 05:20 AM, Stephen Kelly wrote: KDE adds a DebugFull configuration which uses -g3 instead of -g. Would a patch changing Debug to use -g3 be accepted? I am told it adds support for macro expansion in the debugger. Just about every default flag in one of standard CMake

Re: [cmake-developers] Using -g3 in Debug config?

2013-11-12 Thread Stephen Kelly
Brad King wrote: Alternatively, perhaps it is time to generalize debugging and optimizing flags like preprocessor defs, -fPIC, etc. have been generalized. ... and warnings/errors etc http://public.kitware.com/Bug/view.php?id=3811 That could be done/justified independently of other suggested

Re: [cmake-developers] Using -g3 in Debug config?

2013-11-12 Thread Brad King
On 11/12/2013 05:20 AM, Stephen Kelly wrote: KDE adds a DebugFull configuration which uses -g3 instead of -g. Would a patch changing Debug to use -g3 be accepted? I am told it adds support for macro expansion in the debugger. Regardless of the generalizations suggested in my sibling

Re: [cmake-developers] CMake variable documentation containing

2013-11-12 Thread Brad King
On 11/10/2013 03:29 PM, Nils Gladitz wrote: After adding documentation for new variables I noticed that for e.g.: CPACK_WIX_TOOL_EXTENSIONS only CPACK_WIX__EXTENSIONS shows up in the search results. Same seems to be the case for existing documentation for variables like

Re: [CMake] CPack WIX: Using FirewallException

2013-11-12 Thread Nils Gladitz
On 11/12/2013 03:46 AM, Daiwei Li wrote: Hello, I'm having trouble adding a FirewallException (http://wixtoolset.org/documentation/manual/v3/xsd%5Cfirewall%5Cfirewallexception.html) element for my main executable. The documentation says that it must have a File or Component parent, both of

Re: [CMake] CPack WIX: Using FirewallException

2013-11-12 Thread Daiwei Li
Hi Nils, Yes, I was happy to see that you just added the ability to specify WIX Light and Candle extensions to CMake. I built the next branch from source and adding WixFirewallExtension worked just fine. I would be agreeable to a CMake list variable with key-value (target - xml snippet?) pairs

[CMake] Keep folder structure in Visual Studio Project generated with CMake

2013-11-12 Thread Luca Gherardi
I have a projects in which the sources file are organizes in a hierarchy of directories. For example: - Src | - Folder A | - 1.cpp | - 1.hpp | - FolderA1 | - 2.cpp | - 2.hpp | - Folder B | - 3.cpp | - 3.hpp I wrote a CMakeLists.txt for generating a

[CMake] Read memory tests results with jenkins

2013-11-12 Thread Bogdan Cristea
Hi I am running memory leak tests using ctest as follows ctest -D ExperimentalMemCheck I have already in place a jenkins server for continuous build and I am wondering if it is possible to read the memory check report from Jenkins. I am aware of the existence of a Jenkins plugin for

Re: [CMake] Read memory tests results with jenkins

2013-11-12 Thread Gregoire Aujay
Hello Bogdan, I know there is a valgrind plugin for Jenkins but I do not know if it integrates well with CTest outputs. https://wiki.jenkins-ci.org/display/JENKINS/Valgrind+Plugin Regards, Gregoire -Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On

Re: [CMake] Read memory tests results with jenkins

2013-11-12 Thread Nils Gladitz
On 11/12/2013 12:37 PM, Bogdan Cristea wrote: Hi I am running memory leak tests using ctest as follows ctest -D ExperimentalMemCheck Did you find the XML report yet that CTest creates for CDash? DynamicAnalysis.xml should be created in a timestamped subdirectory of Testing/ within your

Re: [CMake] Keep folder structure in Visual Studio Project generated with CMake

2013-11-12 Thread Magnus Therning
When I am forced to use VS for development work I tend to only use it as an editor and bild tool, i.e. I don't create files in it or add things to the project. Instead the sequence I use to add a file is: 1. touch the file I want created 2. modify the relevant CMakeLists.txt to include the

[CMake] ExternalData on unmounted Windows shares?

2013-11-12 Thread Magnus Therning
I'm trying to put some large-ish data files on a windows share and then reference them using the ExternalData module. I'm running into problems setting the ExternalData_URL_TEMPLATES properly. Neither smb://share.host/foo/bar/%(algo)/%(hash) nor //share.host/foo/bar/%(algo)/%(hash) work. For

Re: [CMake] ExternalData on unmounted Windows shares?

2013-11-12 Thread Jakub Zakrzewski
Did you try: \\share.host/foo/bar/%(algo)/%(hash)? (probably you gonna need proper escaping). Note, that UNC paths begin with \\ and in this case they cannot be substitued with //. Also - this is windows-only. -- Gruesse, Jakub -Original Message- From: cmake-boun...@cmake.org

Re: [CMake] ExternalData on unmounted Windows shares?

2013-11-12 Thread Magnus Therning
On Tue, Nov 12, 2013 at 3:06 PM, Jakub Zakrzewski jzakrzew...@e2e.ch wrote: Did you try: \\share.host/foo/bar/%(algo)/%(hash)? (probably you gonna need proper escaping). Note, that UNC paths begin with \\ and in this case they cannot be substitued with //. Also - this is windows-only. This

Re: [CMake] ExternalData on unmounted Windows shares?

2013-11-12 Thread Brad King
On 11/12/2013 08:43 AM, Magnus Therning wrote: Is there some way to point to an unmounted Windows share? Add to ExternalData_URL_TEMPLATES the entry file:share.host/foo/bar/%(algo)/%(hash) Since it is accessible through filesystem APIs you could also set ExternalData_OBJECT_STORES to

[CMake] can non cmake projects be added by externalproject_add?

2013-11-12 Thread Witold E Wolski
And if so how would I do it? I am actually trying to do it for glog (google log). regards Witold -- Witold Eryk Wolski -- 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

Re: [CMake] can non cmake projects be added by externalproject_add?

2013-11-12 Thread Pau Garcia i Quiles
Hello, Of course you can. Take a look at winstng for instance, which builds a lot of non-CMake projects with ExternalProject: https://elpauer.assembla.com/code/winstng/git/nodes/master/cmake/CMakeLists.txt On Tue, Nov 12, 2013 at 6:01 PM, Witold E Wolski wewol...@gmail.com wrote: And if so

Re: [CMake] can non cmake projects be added by externalproject_add?

2013-11-12 Thread Jean-Christophe Fillion-Robin
And also: https://github.com/Slicer/Slicer/tree/master/SuperBuild Hth Jc On Tue, Nov 12, 2013 at 12:04 PM, Pau Garcia i Quiles pgqui...@elpauer.orgwrote: Hello, Of course you can. Take a look at winstng for instance, which builds a lot of non-CMake projects with ExternalProject:

Re: [CMake] can non cmake projects be added by externalproject_add?

2013-11-12 Thread Bill Hoffman
On 11/12/2013 1:21 PM, Jean-Christophe Fillion-Robin wrote: And also: https://github.com/Slicer/Slicer/tree/master/SuperBuild Hth Jc You may also want to look here: http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html -Bill -- Powered by www.kitware.com Please keep

[CMake] Patch for cmake-mode.el

2013-11-12 Thread Roy Crihfield
I have a patch the the CMake emacs mode I'd like to have reviewed and push. What is the preferred way to do this - should I just send the patch, or fork and push to the repository? Roy -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-5073-g4b82282

2013-11-12 Thread Brad King
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 4b82282e25b84e06889d358f620e6bcd4a3372d2 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-5075-g420325d

2013-11-12 Thread Brad King
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 420325de45e2ce785f192bf252d29e89846dea1e (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-600-ga1e22f6

2013-11-12 Thread Brad King
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 a1e22f691792d0c3bcc895ae30f676c6e90167fa (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-604-ga4b9ade

2013-11-12 Thread Brad King
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 a4b9adec893b7cbce41fbffe65564f80b05e5746 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-607-gd3f7fa2

2013-11-12 Thread Brad King
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 d3f7fa22ed8150eb030255adc4470578f1cc71e3 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-5086-gb7d4cf5

2013-11-12 Thread Brad King
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 b7d4cf5e6c29cda3b7d5b8ddb142aedaaab3792e (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-5103-gab72946

2013-11-12 Thread Brad King
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 ab729468f655c94b6471cc9c0fd69ebf6babdf2b (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-5108-g4f961c7

2013-11-12 Thread Brad King
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 4f961c752d9e4ee67cec0ce41e1f7ebd7d84f828 (commit) via