[CMake] Fwd: [cmake-developers] Bugs on the roadmap
Forgot the list, sorry. -- Forwarded message -- From: Eric Noulard Date: 2012/10/17 Subject: Re: [cmake-developers] Bugs on the roadmap To: Rolf Eike Beer 2012/10/16 Rolf Eike Beer : > David Cole wrote: > > Those sound like Alex should have a look. > >> 0011785: [CPack] CPack no stripping with MinGW and NSIS - new. > > Probably Eric. I already did and put some request for feedback on the tracker No answer since then. Unfortunately I'm so seldomly working on a Windows box that Windows specific test needs Windows tester... I'll try again to reproduce the problem on Linux (as Andreas did). In any case, I pushed it to 2.8.11. >> 0012373: [Documentation] Specify version changes with each >> commands/variables - new. > > This could be done by everyone that is bored I think. How do we want to have > it? I found "(since 2.8.x)" and "[Since 2.8.x]", but only for variables in > Find*.cmake modules. We could add a "since" and "last modified in" doc entry for each var/command but I agree that this is a painful and boring task. The idea I think would be to have some builtin support for: http://www.cmake.org/Wiki/CMake_Version_Compatibility_Matrix I think we should discuss and define the way we want to do that and then put this as a [possibly endless] improving loop. -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Ralph Barth/AEH/DBS/GDB ist außer Haus.
Ralph Barth will be out of the office starting 17/10/2012 and will be returning on 23/10/2012. Ich werde Ihre Nachrichten nach meiner Rückkehr beantworten. WLLM related questions pls. contact Sebastian Neusüß and Jens Keil. Theo Price Feed from EDRE pls contact Jens Keil - Deutsche Börse AG Chairman of the Supervisory Board/ Vorsitzender des Aufsichtsrats: Dr. Joachim Faber Executive Board/Vorstand: Dr. Reto Francioni (Chief Executive Officer/Vorsitzender), Andreas Preuss (Deputy Chief Executive Officer/ stellv. Vorsitzender), Frank Gerstenschläger, Dr. Michael Kuhn, Gregor Pottmeyer, Jeffrey Tessler. Aktiengesellschaft with registered seat in/mit Sitz in Frankfurt am Main. Commercial register/Handelsregister: Local court/Amtsgericht Frankfurt am Main HRB 32232. - Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. Legally required information for business correspondence/ Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz: http://deutsche-boerse.com/letterhead -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] how to build cmake with mingw and msys?
On 2012-08-16 08:42-0700 Alan W. Irwin wrote: I am not in a position to do MinGW/MSYS experiments on the Wine platform at the moment, but once that is possible (should be a couple of weeks from now) I will attempt to confirm on that platform that the bootstrap method of building CMake works for MinGW/MSYS provided that the correct PATH to the MSYS version of make.exe is set. I finally got a chance to work on this so to take up this thread where it left off two months ago I just now tried that experiment with wine-1.3.15 which I recently built and installed under Linux (Debian wheezy). After some default configuration of Wine with winecfg, I continued with the following steps: * Used the latest version of the MinGW/MSYS installer obtained with wget \ http://prdownloads.sourceforge.net/mingw/Installer/mingw-get-inst/mingw-get-inst-20120426/mingw-get-inst-20120426.exe N.B. This installer appears to give reliable downloads and installs of MinGW/MSYS from scratch, but it is alpha software so some of its updating functionality does not appear to work correctly. For example, others here have used the update function with no obvious issues, but it turned out the installer silently did not update to the latest MinGW/MSYS. Thus, to get MinGW/MSYS results comparable to mine, they had to use the "from scratch" method. * Ran that Windows installer under wine to download and install essentially all of the latest MinGW/MSYS versions on the Wine platform. That only took a few minutes! I then confirmed bash.exe worked under wine, and then I put the MinGW binary directory above the MSYS binary directory on the PATH, e.g., bash.exe-3.1$ echo $PATH /z/home/wine/newstart/MinGW/bin/:/z/home/wine/newstart/MinGW/msys/1.0/bin/:/c/windows/system32:/c/windows:/c/windows/system32/wbem * I unpacked a Unix version (the Unix line endings make no difference for MinGW/MSYS, and I had this tarball downloaded already) of the CMake-2.8.9 tarball under Linux. Then I switched to the Wine platform, changed to the unpacked CMake-2.8.9 directory, and ran (--no-qt-gui for simplicity) ./bootstrap --no-qt-gui \ --prefix=/z/home/wine/newstart/bootstrap_cmake/install \ --parallel=8 >& bootstrap.out make -j8 >& make.out make -j8 install >& make_install.out No errors or warnings showed up in those *.out files. Also, the Windows file command (available from MSYS) gives the following information about that CMake executable that was built on MinGW/MSYS/wine: bash.exe-3.1$ file install/bin/cmake install/bin/cmake: PE32 executable for MS Windows (console) Intel 80386 32-bit Note this is a 32-bit executable on my 64-bit hardware because I built and installed the 32-bit version of wine which corresponds to a 32-bit version of Windows. I could have built a 64-bit version of wine, but the 32-bit version is more heavily tested by wine users, that's the version that has been a success for me in the past, and therefore I stuck with it this time as well. I then tested that Windows version of cmake that I had built with the bootstrap method by using it to build and test one of my projects (ephcom2, part of the Time Ephemerides project) on Wine. That test went well and produced results equivalent to the corresponding test results for ephcom on Linux. So it appears the bootstrap build of CMake works fine for MinGW/MSYS on the Wine version of Windows. Therefore I expect it will also work fine for MinGW/MSYS on the Microsoft version of Windows even though for now http://www.cmake.org/cmake/help/install.html ignores this bootstrap build possibility for Windows. Note, this was all in the spirit of an experiment to see whether cmake bootstrap builds actually work for MinGW/MSYS on a Windows platform. An obvious alternative is just to download the binary CMake version for Windows and use that instead. But the experiment is also a good test of the Windows build tools I installed with the latest MinGW/MSYS installer on my Wine platform so I am glad I tried the experiment, and I plan to use the resulting CMake executable for a number of software builds on the Wine platform beyond the current ephcom one. Alan _ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscrib
Re: [CMake] set_target_properties called twice
David and Frank,
Thank you so much! That worked perfectly! I really really appreciate your help,
I have been pounding away at this for days now... I should have just asked you
guys in the first place.
Thanks,
Eric
> -Original Message-
> From: David Cole [mailto:david.c...@kitware.com]
> Sent: Tuesday, October 16, 2012 3:25 PM
> To: Eric Clark
> Cc: CMake Mailing List (cmake@cmake.org)
> Subject: Re: [CMake] set_target_properties called twice
>
> Try APPEND_STRING with a leading space in the string...
>
> On Tue, Oct 16, 2012 at 4:19 PM, Eric Clark wrote:
> > Frank,
> >
> >
> >
> > Thank you for such a quick reply. However, this is not working either.
> > It is correctly adding the value to my list for that property, but now
> > it is using it as the whole value in Visual Studio. Here is what I
> > have now for the first call:
> >
> >
> >
> > set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
> > "/ENTRY:\"mainCRTStartup\"")
> >
> >
> >
> > And, now for the second call, I have this:
> >
> >
> >
> > set_property(TARGET ${PROJECT_NAME} APPEND PROPERTY LINK_FLAGS
> > "/INCREMENTAL:NO")
> >
> >
> >
> > But, when I open Visual Studio, instead of setting them both, it now
> > has "mainCRTStartup;/INCREMENTAL:NO" as the property value. Is there
> > something I am doing wrong here? By the way, I tried both APPEND and
> > APPEND_STRING, the only difference is the semi-colon goes away with
> APPEND_STRING.
> >
> >
> >
> > Thanks,
> >
> > Eric
> >
> >
> >
> > From: Miller, Frank [mailto:fmil...@sjm.com]
> > Sent: Tuesday, October 16, 2012 2:58 PM
> > To: Eric Clark; CMake Mailing List (cmake@cmake.org)
> > Subject: RE: set_target_properties called twice
> >
> >
> >
> > I think this is intended. The semantics are the same as the set function.
> > You can use set_property with the APPEND or APPEND_STRING option to
> do
> > what you want.
> >
> >
> >
> > Frank
> >
> >
> >
> > From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org]
> On
> > Behalf Of Eric Clark
> > Sent: Tuesday, October 16, 2012 2:53 PM
> > To: CMake Mailing List (cmake@cmake.org)
> > Subject: [CMake] set_target_properties called twice
> >
> >
> >
> > Hello,
> >
> >
> >
> > I am currently having trouble with set_target_properties(...). I am
> > trying to call it twice to set two different values for the same
> > property. The first call I make looks like this:
> >
> >
> >
> > set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
> > "/ENTRY:mainCRTStartup")
> >
> >
> >
> > Then, I call it again with the following signature:
> >
> >
> >
> > set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
> > "/INCREMENTAL:NO")
> >
> >
> >
> > When I do this, the second call seems to override the previous call.
> > Can anyone tell me if this is intended or a bug? And, if so, does
> > anyone know of a work-around for this?
> >
> >
> >
> > Thank You,
> >
> > Eric
> >
> >
> >
> > To be fond of something is better than merely to know it, and to find
> > joy in it is better than merely to be fond of it. -- The Analects,
> > Confucius
> >
> >
> >
> >
> > This communication, including any attachments, may contain information
> > that is proprietary, privileged, confidential or legally exempt from
> disclosure.
> > If you are not a named addressee, you are hereby notified that you are
> > not authorized to read, print, retain a copy of or disseminate any
> > portion of this communication without the consent of the sender and
> > that doing so may be unlawful. If you have received this communication
> > in error, please immediately notify the sender via return e-mail and
> > delete it from your system.
> >
> >
> > --
> >
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the CMake FAQ at:
> > http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] set_target_properties called twice
Try APPEND_STRING with a leading space in the string...
On Tue, Oct 16, 2012 at 4:19 PM, Eric Clark wrote:
> Frank,
>
>
>
> Thank you for such a quick reply. However, this is not working either. It is
> correctly adding the value to my list for that property, but now it is using
> it as the whole value in Visual Studio. Here is what I have now for the
> first call:
>
>
>
> set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
> "/ENTRY:\"mainCRTStartup\"")
>
>
>
> And, now for the second call, I have this:
>
>
>
> set_property(TARGET ${PROJECT_NAME} APPEND PROPERTY LINK_FLAGS
> "/INCREMENTAL:NO")
>
>
>
> But, when I open Visual Studio, instead of setting them both, it now has
> “mainCRTStartup;/INCREMENTAL:NO” as the property value. Is there something I
> am doing wrong here? By the way, I tried both APPEND and APPEND_STRING, the
> only difference is the semi-colon goes away with APPEND_STRING.
>
>
>
> Thanks,
>
> Eric
>
>
>
> From: Miller, Frank [mailto:fmil...@sjm.com]
> Sent: Tuesday, October 16, 2012 2:58 PM
> To: Eric Clark; CMake Mailing List (cmake@cmake.org)
> Subject: RE: set_target_properties called twice
>
>
>
> I think this is intended. The semantics are the same as the set function.
> You can use set_property with the APPEND or APPEND_STRING option to do what
> you want.
>
>
>
> Frank
>
>
>
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
> Eric Clark
> Sent: Tuesday, October 16, 2012 2:53 PM
> To: CMake Mailing List (cmake@cmake.org)
> Subject: [CMake] set_target_properties called twice
>
>
>
> Hello,
>
>
>
> I am currently having trouble with set_target_properties(…). I am trying to
> call it twice to set two different values for the same property. The first
> call I make looks like this:
>
>
>
> set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
> "/ENTRY:mainCRTStartup")
>
>
>
> Then, I call it again with the following signature:
>
>
>
> set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
> "/INCREMENTAL:NO")
>
>
>
> When I do this, the second call seems to override the previous call. Can
> anyone tell me if this is intended or a bug? And, if so, does anyone know of
> a work-around for this?
>
>
>
> Thank You,
>
> Eric
>
>
>
> To be fond of something is better than merely to know it, and to find joy in
> it is better than merely to be fond of it. -- The Analects, Confucius
>
>
>
>
> This communication, including any attachments, may contain information that
> is proprietary, privileged, confidential or legally exempt from disclosure.
> If you are not a named addressee, you are hereby notified that you are not
> authorized to read, print, retain a copy of or disseminate any portion of
> this communication without the consent of the sender and that doing so may
> be unlawful. If you have received this communication in error, please
> immediately notify the sender via return e-mail and delete it from your
> system.
>
>
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] set_target_properties called twice
Frank,
Thank you for such a quick reply. However, this is not working either. It is
correctly adding the value to my list for that property, but now it is using it
as the whole value in Visual Studio. Here is what I have now for the first call:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
"/ENTRY:\"mainCRTStartup\"")
And, now for the second call, I have this:
set_property(TARGET ${PROJECT_NAME} APPEND PROPERTY LINK_FLAGS
"/INCREMENTAL:NO")
But, when I open Visual Studio, instead of setting them both, it now has
"mainCRTStartup;/INCREMENTAL:NO" as the property value. Is there something I am
doing wrong here? By the way, I tried both APPEND and APPEND_STRING, the only
difference is the semi-colon goes away with APPEND_STRING.
Thanks,
Eric
From: Miller, Frank [mailto:fmil...@sjm.com]
Sent: Tuesday, October 16, 2012 2:58 PM
To: Eric Clark; CMake Mailing List (cmake@cmake.org)
Subject: RE: set_target_properties called twice
I think this is intended. The semantics are the same as the set function. You
can use set_property with the APPEND or APPEND_STRING option to do what you
want.
Frank
From: cmake-boun...@cmake.org
[mailto:cmake-boun...@cmake.org] On Behalf Of Eric Clark
Sent: Tuesday, October 16, 2012 2:53 PM
To: CMake Mailing List (cmake@cmake.org)
Subject: [CMake] set_target_properties called twice
Hello,
I am currently having trouble with set_target_properties(...). I am trying to
call it twice to set two different values for the same property. The first call
I make looks like this:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
"/ENTRY:mainCRTStartup")
Then, I call it again with the following signature:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS "/INCREMENTAL:NO")
When I do this, the second call seems to override the previous call. Can anyone
tell me if this is intended or a bug? And, if so, does anyone know of a
work-around for this?
Thank You,
Eric
To be fond of something is better than merely to know it, and to find joy in it
is better than merely to be fond of it. -- The Analects, Confucius
This communication, including any attachments, may contain information that is
proprietary, privileged, confidential or legally exempt from disclosure. If you
are not a named addressee, you are hereby notified that you are not authorized
to read, print, retain a copy of or disseminate any portion of this
communication without the consent of the sender and that doing so may be
unlawful. If you have received this communication in error, please immediately
notify the sender via return e-mail and delete it from your system.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] set_target_properties called twice
On Tue, Oct 16, 2012 at 3:53 PM, Eric Clark wrote:
> Hello,
>
>
>
> I am currently having trouble with set_target_properties(…). I am trying to
> call it twice to set two different values for the same property. The first
> call I make looks like this:
>
>
>
> set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
> "/ENTRY:mainCRTStartup")
>
>
>
> Then, I call it again with the following signature:
>
>
>
> set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
> "/INCREMENTAL:NO")
>
>
>
> When I do this, the second call seems to override the previous call. Can
> anyone tell me if this is intended or a bug? And, if so, does anyone know of
> a work-around for this?
>
>
>
> Thank You,
>
> Eric
>
>
>
> To be fond of something is better than merely to know it, and to find joy in
> it is better than merely to be fond of it. -- The Analects, Confucius
>
>
>
>
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
It's intended, and can't be changed for backwards compatibility reasons.
Instead, use the set_property command with the APPEND keyword.
http://cmake.org/cmake/help/v2.8.9/cmake.html#command:set_property
HTH,
David
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] set_target_properties called twice
I think this is intended. The semantics are the same as the set function. You
can use set_property with the APPEND or APPEND_STRING option to do what you
want.
Frank
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Eric Clark
Sent: Tuesday, October 16, 2012 2:53 PM
To: CMake Mailing List (cmake@cmake.org)
Subject: [CMake] set_target_properties called twice
Hello,
I am currently having trouble with set_target_properties(...). I am trying to
call it twice to set two different values for the same property. The first call
I make looks like this:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
"/ENTRY:mainCRTStartup")
Then, I call it again with the following signature:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS "/INCREMENTAL:NO")
When I do this, the second call seems to override the previous call. Can anyone
tell me if this is intended or a bug? And, if so, does anyone know of a
work-around for this?
Thank You,
Eric
To be fond of something is better than merely to know it, and to find joy in it
is better than merely to be fond of it. -- The Analects, Confucius
This communication, including any attachments, may contain information that is
proprietary, privileged, confidential or legally exempt from disclosure. If you
are not a named addressee, you are hereby notified that you are not authorized
to read, print, retain a copy of or disseminate any portion of this
communication without the consent of the sender and that doing so may be
unlawful. If you have received this communication in error, please immediately
notify the sender via return e-mail and delete it from your system.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] set_target_properties called twice
Hello,
I am currently having trouble with set_target_properties(...). I am trying to
call it twice to set two different values for the same property. The first call
I make looks like this:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
"/ENTRY:mainCRTStartup")
Then, I call it again with the following signature:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS "/INCREMENTAL:NO")
When I do this, the second call seems to override the previous call. Can anyone
tell me if this is intended or a bug? And, if so, does anyone know of a
work-around for this?
Thank You,
Eric
To be fond of something is better than merely to know it, and to find joy in it
is better than merely to be fond of it. -- The Analects, Confucius
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Adding dependencies for static libraries
Titus von Boxberg skrev 2012-10-16 19:11: That wasn't clear from your first post. Yes, your're right, sorry 'bout that. I doubt that this is the intended behaviour of target_link_libraries. Nominally target_link_libraries isn't used at all for static libs, but if it should be, I'd expect the same behavior as that for shared libraries, which is to add the dependency libs to "Additional Dependencies". It just seems that no one thought of implementing it for the VS generators in the static lib case. If you want the librarian to combine A and B into a single A+ than you might as well add a post build step of A to do so. Yup, true, I don't know yet how to do it though, I had hopes that CMake would come to the rescue... Regards, /Rob -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ExternalProjects with Visual Studio
If you want "real" vcxproj references, then use add_subdirectory instead of ExternalProject to build things directly. Or is there some reason you can't do that? If we made "real" vcxproj files directly, then we'd have to run configure on all the sub-projects at the outer project configure time. (Which is nigh impossible seeing as how even downloading the source code is deferred to build time...) This would be directly opposed to one of the main design goals of ExternalProject: defer ALL time-consuming operations to build time. HTH, David On Mon, Oct 15, 2012 at 9:31 AM, Titus von Boxberg wrote: > Hi all, > > my C++ sources are split into several (static) libraries and > an executable that uses the static libs. > All of those source modules have CMake configurations. > > I'm using ExternalProject_Add in the executable's CMakeLists.txt > together with target_link_libraries > to add the static libs to the executable's project. > > All that works well under UNIX and Windows. > > However, when opening the sln with Visual Studio, the project files > of the libraries do not contain the sources; they are only placeholders > to build the libraries for the executable. > That's clear to me since the "real" vcxproj files within the > libraries are generated during the configure step of the > ExternalProject build and are unavailable at the time the > executable's sln or vcxproj are generated by cmake. > > My question is: Is there an automatic way to get sln and vcxproj > files for the executable that reference the "real" vcxproj files > of the libraries instead of the placeholders? > > Thanks in advance > > Regards > Titus > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Setting test environment on windows
The following example demonstrates a way for you to achieve what you need:
cmake_minimum_required(VERSION 2.8)
project(t1)
include(CTest)
add_test(NAME test01 COMMAND ${CMAKE_COMMAND} -E environment)
set_property(TEST test01 APPEND PROPERTY ENVIRONMENT Z1ENV=1;2;3 Z2ENV=a;b;c)
add_test(NAME test02 COMMAND ${CMAKE_COMMAND} -E environment)
set_property(TEST test02 APPEND PROPERTY ENVIRONMENT Z1ENV=1\;2\;3
Z2ENV=a\;b\;c)
add_test(NAME test03 COMMAND ${CMAKE_COMMAND} -E environment)
set_property(TEST test03 APPEND PROPERTY ENVIRONMENT "Z1ENV=1\;2\;3"
"Z2ENV=a\;b\;c")
Only test03 actually produces the sort of results you want with
semi-colons embedded in the env variable value.
So:
escape the semi-colons in the PATH value
and
enclose "PATH=${path_value}" in double quotes
That should give you what you need.
To escape the semi-colons, use:
string(REPLACE ";" "\\;" path_value "${path_value}")
Let us know if this works for you and what your final code looks like
so others can reference it too.
HTH,
David
On Wed, Oct 10, 2012 at 8:57 AM, Jakub Zakrzewski wrote:
> Hi, thanks for response.
>
> Unfotunatly:
>
> set(THIRD_PARTY_LIBS "${THIRD_PARTY_LIBS}\;${JAVA_JVM_LIBRARY_PATH}");
>
> SET_TESTS_PROPERTIES(ut PROPERTIES ENVIRONMENT
> "BRIDGESERVER_BIN=D:/Projects/e2e_bridge/server/head/src/AddOns/PersistentState;PATH=\"D:/Projects/e2e_bridge/server/head/bin/win64-debug;C:/Program
>
> Files/Java/jdk1.6.0_30/lib/../jre/bin/server\";INSTANCES_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug;INSTANCE_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug")
>
> This looks correct at first glance, but doesn't work. I mean the PATH is
> definatly not set correctly as jvm.dll is not found. When I set it manually
> before running the "ut" executable, it's OK.
>
> --
> Gruesse,
> Jakub
>
>
>
>
> From: Petr Kmoch [mailto:petr.km...@gmail.com]
> Sent: Mittwoch, 10. Oktober 2012 14:40
> To: Jakub Zakrzewski
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Setting test environment on windows
>
> Hi Jakub.
>
> I would try adding quotes around the dereference of THIRD_PARTY_LIBS. That is:
> set_properties(... PATH="${THIRD_PARTY_LIBS}" ...)
>
> Petr
> On Wed, Oct 10, 2012 at 2:13 PM, Jakub Zakrzewski wrote:
> Hi All.
>
> Could someone explain to me, how properly set environment for CTest from
> CMakeLists.txt?
>
> Ihave something like:
>
> set(THIRD_PARTY_LIBS "${THIRD_PARTY_LIBS};${JAVA_JVM_LIBRARY_PATH}");
> set_properties(TEST myTest PROPERTY ENVIRONMENT
> BRIDGESERVER_BIN=${PROJECT_SOURCE_DIR}/src/AddOns/PersistentState
> PATH=${THIRD_PARTY_LIBS}
> INSTANCES_HOME=${CMAKE_BINARY_DIR}
> INSTANCE_HOME=${CMAKE_BINARY_DIR}
> )
>
> This gets expanded to:
> SET_TESTS_PROPERTIES(ut PROPERTIES ENVIRONMENT
> "BRIDGESERVER_BIN=D:/Projects/e2e_bridge/server/head/src/AddOns/PersistentState;PATH=D:/Projects/e2e_bridge/server/head/bin/win64-debug;C:/Program
>
> Files/Java/jdk1.6.0_30/lib/../jre/bin/server;INSTANCES_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug;INSTANCE_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug")
>
> Which is wrong (note the semicolon). Below are my trials and their results:
>
>
> #1st
> set(THIRD_PARTY_LIBS "${THIRD_PARTY_LIBS}\;${JAVA_JVM_LIBRARY_PATH}");
>
> SET_TESTS_PROPERTIES(ut PROPERTIES ENVIRONMENT
> "BRIDGESERVER_BIN=D:/Projects/e2e_bridge/server/head/src/AddOns/PersistentState;PATH=D:/Projects/e2e_bridge/server/head/bin/win64-debug;C:/Program
>
> Files/Java/jdk1.6.0_30/lib/../jre/bin/server;INSTANCES_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug;INSTANCE_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug")
>
> #2nd
> set(THIRD_PARTY_LIBS "${THIRD_PARTY_LIBS}\\;${JAVA_JVM_LIBRARY_PATH}");
>
> SET_TESTS_PROPERTIES(ut PROPERTIES ENVIRONMENT
> "BRIDGESERVER_BIN=D:/Projects/e2e_bridge/server/head/src/AddOns/PersistentState;PATH=D:/Projects/e2e_bridge/server/head/bin/win64-debug;C:/Program
>
> Files/Java/jdk1.6.0_30/lib/../jre/bin/server;INSTANCES_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug;INSTANCE_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug")
>
> #3rd
> set(THIRD_PARTY_LIBS "${THIRD_PARTY_LIBS}\\\;${JAVA_JVM_LIBRARY_PATH}");
>
> SET_TESTS_PROPERTIES(ut PROPERTIES ENVIRONMENT
> "BRIDGESERVER_BIN=D:/Projects/e2e_bridge/server/head/src/AddOns/PersistentState;PATH=D:/Projects/e2e_bridge/server/head/bin/win64-debug;C:/Program
>
> Files/Java/jdk1.6.0_30/lib/../jre/bin/server;INSTANCES_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug;INSTANCE_HOME=D:/Projects/e2e_bridge/server/head/build/win64-debug")
>
> #4th
> set(THIRD_PARTY_LIBS "${THIRD_PARTY_LIBS};${JAVA_JVM_LIBRARY_PATH}");
>
> SET_TESTS_PROPERTIES(ut PROPERTIES ENVIRONMENT
> "BRIDGESERVER_BIN=D:/Projects/e2e_bridge/server/head/src/AddOns/PersistentState;PATH=D:/Projects/e2e_bridge/server/head/bin/win64-debug;C:/Program
>
> Files/Java/jdk1.6.0_30/lib/../jre/bin/server;INSTANCES_HOME=D:/Projects/e2e
Re: [CMake] Adding dependencies for static libraries
Am 16.10.2012 17:53, schrieb Robert Bielik: Titus von Boxberg skrev 2012-10-16 13:20: Actually, "target_link_libraries(C B)" puts B into the Additional Dependencies of the VC project generated for C. Unfortunately that doesn't cut it. target_link_libraries adds the build dependency, but it does not list the lib files in "Additional Dependecies", which I think shuld be default behavior with static libraries (just as it does for a shared library). Well, I'm using target_link_libraries and it does what I described: Add the libraries to Additional Dependencies of the EXE project. I'll file a bug report for this. My whole aim is to be able to create a single static library file that contains everything it needs, so that an executable linking statically won't have to bother. Using a shared library is an option, but we'd like to be able to offer customers both dynamic and static linking options. That wasn't clear from your first post. I doubt that this is the intended behaviour of target_link_libraries. If you want the librarian to combine A and B into a single A+ than you might as well add a post build step of A to do so. Regards Titus -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Adding dependencies for static libraries
Titus von Boxberg skrev 2012-10-16 13:20: Actually, "target_link_libraries(C B)" puts B into the Additional Dependencies of the VC project generated for C. Unfortunately that doesn't cut it. target_link_libraries adds the build dependency, but it does not list the lib files in "Additional Dependecies", which I think shuld be default behavior with static libraries (just as it does for a shared library). I'll file a bug report for this. My whole aim is to be able to create a single static library file that contains everything it needs, so that an executable linking statically won't have to bother. Using a shared library is an option, but we'd like to be able to offer customers both dynamic and static linking options. Regards /Rob -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake rebuilds every time
What does your CMakeLists look like? Only the necessary rebuild steps should be taken on an incremental build. How do you invoke a rebuild? (Just typing 'make' or some other mechanism?) On Mon, Oct 15, 2012 at 6:22 AM, Arindam Mukherjee wrote: > Hi, > > I have a cross-platform build setup using cmake 2.8.9 which builds on > 5 different OSs. However it rebuilds every time even when neither the > Makefile timestamps nor the source file timastamps had changed. > Examining the generated Makefiles I can see that all .o, .i and .s > targets have been marked .PHONY. Don't know if this is the reason for > it. How to fix this to not rebuild every time but do incremental > builds? > > Thanks, > Arindam > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] How to specify that install target doesn't depend on some test targets
In my edit/compile/install/test process (where test is out of the CMake scope), I would like to be able to do a: make mylib && make install without building all the test suite. BUT (there's a but), "make all" still have to build the test suite. Is there a way to do that? My understanding is that "all" target depends on tests build; and "install" target depends on "all". I am afraid the answer will be no :( -- Jérôme -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Adding dependencies for static libraries
Am 16.10.2012 12:43, schrieb Robert Bielik: Hi all, I haven't found the answer to this: I have a static library A that uses static library B, but when I create an executable C I only want to link with A. AFAIK you have to link C also with B. You might add a target_link_libraries(C B) in C's configuration. A non portable way to avoid this configuration could be to use automatic linking directives in A's headers included by C. In Visual Studio this is accomplished by adding library B to "Additional Dependencies" (Librarian/General), but how can I make CMake create that dependency ? When you add B to the Additional Dependencies, C is linked with B. Actually, "target_link_libraries(C B)" puts B into the Additional Dependencies of the VC project generated for C. HTH Titus -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Adding dependencies for static libraries
Hi all, I haven't found the answer to this: I have a static library A that uses static library B, but when I create an executable C I only want to link with A. In Visual Studio this is accomplished by adding library B to "Additional Dependencies" (Librarian/General), but how can I make CMake create that dependency ? TIA /Rob -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Same effect as g++ -bundle ?
On 10/16/2012 02:06 AM, digitalriptide wrote: > I need to create a Mach-o bundle format file. With g++, for example, I > can do the following > > g++ -o helloWorld.bundle -bundle helloWorld.o > > given some object file. > > Is there some way to do this from cmake? I've looked at the > documentation for add_library but I can't seem to find anything. > > Any hints or pointers are greatly appreciated. Cheers! add_library(helloWorld helloWorld.m) set_taget_properties(helloWorld PROPERTIES BUNDLE TRUE) HTH Michael -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] add_custom_command
On 10/15/2012 08:20 PM, Totte Karlsson wrote:
>
> set( resultFileFolder "${PROJECT_SOURCE_DIR}/wiki/reports") set(
> resultFile "${resFileFolder}/tests_auto.xml")
>
>> First things first: You should *never* pollute your source tree, always
>> output to the build tree.
> This is part of a google code project and the output file is a report in
> the wiki. It belongs in the repository. Actually, its not an output from
> the build itself, but output from a test, run just after the build.
>
>>
>> You need a top-level target that DEPENDS on the output, that's all. E.g.
>>
>> add_custom_target(createWikiReports ALL DEPENDS ${resultFile})
> I ended up doing this instead;
> set( resultFileFolder "${CMAKE_SOURCE_DIR}/wiki/reports")
>
> add_custom_target(test PACKAGE
> COMMAND ${exe_path}/${target}.exe ${resultFileFolder}
> )
>
> This seem to work well with borland, but with visual studio it is
> executed before the target is built, which is a problem, obviously.
You need a "DEPENDS ${target}", otherwise the build order of top-level
targets is determined by the build system. The drawback is, that custom
targets are always considedered to be out-of-date, i.e. will be invoked
on every single build. After all, they don't know anything about the
output...
>
> So perhaps the combination of add_custom_command and add_custom_target
> is needed?
If you want to run the command only if any of the dependencies
(executable, input files) changes, yes.
>
> Weird that it behaves differently using borland and visual studio though?
As mentioned, top-level targets without explicit dependencies are built
in which-ever order they please.
>> BTW: You don't need to specify the full path to the executable in the
>> COMMAND, and also no DEPENDS on it in the custom command. Just use the
>> target name, and CMake will handle the rest for you.
> I always seem to have problem with the paths regarding targets, because
> of Visual Studios addition of Debug and Release.
> -totte
It's not clear what you want to say here... Does it work with the target
name, or does it no?
This will always work:
add_executable(frobnicate frobnicate.c)
add_custom_command(OUTPUT ${resultFile}
COMMAND frobnicate ${resultFileFolder}
WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
COMMENT "Generating Wiki reports"
VERBATIM)
add_custom_target(generateReports ALL DEPENDS ${resultFile})
Michael
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] cmake + ninja + CMAKE_TOOLCHAIN_FILE fails
Hi!
When using 'cmake .. -DCMAKE_TOOLCHAIN_FILE=../cmake/m3.cmake' with
the makefile generator this works prefectly but when using it with
'cmake -GNinja .. -DCMAKE_TOOLCHAIN_FILE=../cmake/m3.cmake' it fails
with the following message:
cmake -GNinja -DCMAKE_TOOLCHAIN_FILE=../cmake/m3.cmake ../
-- The C compiler identification is GNU 4.6.3
-- Check for working C compiler using: Ninja
-- Check for working C compiler using: Ninja -- broken
CMake Error at
/usr/local/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61
(message):
The C compiler "/srv/scratch/ARM_EABI/bin/arm-none-eabi-gcc" is not
able to
compile a simple test program.
It fails with the following output:
Change Dir: /srv/scratch/sigubufo/m3bare/ninja/CMakeFiles/CMakeTmp
Run Build Command:/usr/bin/ninja cmTryCompileExec1450194663
[1/2] Building C object
CMakeFiles/cmTryCompileExec1450194663.dir/testCCompiler.c.o
[2/2] Linking C executable cmTryCompileExec1450194663
FAILED: : && /srv/scratch/ARM_EABI/bin/arm-none-eabi-gcc
CMakeFiles/cmTryCompileExec1450194663.dir/testCCompiler.c.o -o
cmTryCompileExec1450194663 -rdynamic && :
arm-none-eabi-gcc: error: unrecognized option '-rdynamic'
ninja: build stopped: subcommand failed.
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:5 (Project)
CMake Error: Error required internal CMake variable not set, cmake may
be not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILER_ENV_VAR
CMake Error: Error required internal CMake variable not set, cmake may
be not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILER
CMake Error: Could not find cmake module
file:/srv/scratch/sigubufo/m3bare/ninja/CMakeFiles/2.8.9.20120918-g56154/CMakeCXXCompiler.cmake
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
This is the m3.cmake file:
set(CMAKE_SYSTEM_NAME Generic)
set(COMPILER_PREFIX "arm-none-eabi-")
set(LAUTERBACH_EXE "t32marm")
set(COMMON_FLAGS "-ffunction-sections -fdata-sections -fno-builtin
-fno-unwind-tables -Wall -Wpointer-arith -Wundef -Wno-write-strings
-mcpu=cortex-m3 -mthumb -mfix-cortex-m3-ldrd -ffunction-sections
-fdata-sections ")
set(CMAKE_C_FLAGS " ${COMMON_FLAGS}")
set(CMAKE_CXX_FLAGS "${COMMON_FLAGS} -ffunction-sections
-fdata-sections -fno-builtin -fno-rtti -fno-exceptions
-fno-unwind-tables -Woverloaded-virtual" )
add_definitions("${COMMON_FLAGS}")
find_program(ELFSIZE "${COMPILER_PREFIX}size")
find_program(OBJCOPY "${COMPILER_PREFIX}objcopy")
find_program(MKIMAGE "mkimage")
# Set C/C++ Compiler and binutils
set(CMAKE_C_COMPILER ${COMPILER_PREFIX}gcc)
set(CMAKE_CXX_COMPILER ${COMPILER_PREFIX}g++)
# search for programs in the build host directories
SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
# for libraries and headers in the target directories
SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
I already posted this in the ninja mailing list and they told me to come
here.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Cross compiling from linux to windows using wine-based visual studio compilers
On 2012-10-15 21:46-0700 Daniel Russel wrote: On Oct 15, 2012, at 9:35 PM, "Alan W. Irwin" wrote: On 2012-10-15 21:02-0700 Daniel Russel wrote: I'm trying to get cross compilation of a simple library working to build a windows library on a linux box using the visual studio compilers. I don't get it. How can visual studio compilers execute properly on Linux? Don't they need to be run on a Windows platform? Using Wine. I probably should have mentioned it. Actually you did right in the subject line, but my eyes focussed on cross-compilation and just plain missed it. :-) And perhaps cross-compilation is not quite the right term. Is there a better one? I just call it building software on the Wine platform. We have been using them to compile other projects built with scons. That's cool that the visual studio compilers work with scons on the Wine platform. I think that and my good results with the Windows version of CMake on Wine (albeit with a different Windows compiler) is a pretty good indication that CMake + visual studio compilers will probably work on the Wine platform for you as well. Alan __ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
