<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Is there a possibility of adding VS2008 support? VS2008 supports compilation for 64 bit platforms. Albeit I am still to figure 64 bit compilation using gcc/MinGW with CMake itself.<br><br>I have heard that VS2010 has changed the file-formats for project files. I am not keen on VS2010 support as yet though.<br><br>Best regards - Alok<br><br>> Date: Thu, 10 Jun 2010 19:26:21 +0200<br>> From: andi@lisas.de<br>> To: cmake@cmake.org<br>> CC: jesper.eskilson@iar.se<br>> Subject: [CMake] vcproj2cmake.rb script: announcing new version / hosting questions<br>> <br>> Hello all,<br>> <br>> given great vcproj2cmake.rb work done by Jesper Eskilson (openly added in CC<br>> given his previous mailing list activity), I was able to enhance<br>> this wonderful script with certain extensions:<br>> <br>> - list _all_ configuration types<br>> - add indenting<br>> - add per-platform configuration of definitions, dependencies and includes<br>> - add optional includes to provide static content, thus allowing for a nice<br>> on-the-fly generation mode of operation _side-by-side_ existing and _updated_<br>> .vcproj files<br>> - fully support recursive handling of all .vcproj file groups (filters)<br>> - many other improvements and fixes<br>> <br>> I also created a rough vcproj2cmake_recursive.rb to parse an existing<br>> sub project hierarchy (this one should probably get changed<br>> to have separate modes, either recursive directory parsing into a list file<br>> _or_ acting on a pre-created / modified directory list file).<br>> <br>> Given these implementations (and some hook script work, to Find / Use dependencies),<br>> I'm now actually able to build an entire pretty large VS2005 project<br>> (around 40 sub projects etc.) on Linux without trouble, directly after each<br>> vcproj2cmake conversion run (since the plan is - as listed above - to be able<br>> to get on-the-fly access to any project updates whatsoever that happen<br>> on the Windows side).<br>> <br>> A full-scale, final conversion of .vcproj to CMakeLists.txt isn't really feasible<br>> in many cases (many Windows people would very understandably like to keep<br>> proper MSVS integration of source files etc.), thus it was important to me<br>> to write a converter which fully supports side-by-side operation<br>> on non-Windows platforms.<br>> <br>> I'm not certain whether the current enhanced script is self-contained,<br>> i.e. whether the generated CMakeLists.txt is able to run<br>> without any external configuration files present as it should (to be fixed).<br>> It will need some more love before being distributed properly anyway, methinks.<br>> <br>> <br>> Which leads me to the important part of my mail:<br>> <br>> I believe that the scripts should be handled in a more prominent way now than simply<br>> having them mentioned in the Wiki.<br>> Thus:<br>> <br>> a) where to host them?<br>> - CMake repository<br>> - SourceForge, gitorious, Berlios, ...<br>> <br>> b) which license to use?<br>> Jesper tended towards GPL-like, and I'm also less of a BSD/X11 fan<br>> <br>> <br>> For hosting, I think it would actually be a good idea to have them in CMake repository as well,<br>> since one could argue that there's a pretty strong match.<br>> <br>> Coming from a proprietary project (carrying my "proprietary project" hat ;),<br>> my preference is to be able to freely use the scripts in any proprietary project,<br>> but to make sure that any further proprietary use is required to contribute back<br>> any modifications once delivered to customers.<br>> Thus licensing as GPL seems out of the question (though not entirely sure<br>> how a special "script project" would be affected by GPL regulations),<br>> and LGPL seems to be the goal. Rrrright!?<br>> <br>> Both scripts are attached.<br>> <br>> Any comments or ideas?<br>> <br>> Thank you for a great build environment,<br>> <br>> Andreas Mohr<br> <br /><hr />Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. <a href='http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1' target='_new'>Learn more.</a></body>
</html>