<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<!----><br>
<blockquote
cite="mid:F5114451B5F49649A9337243D4F8E469080098D9@THHS2EXBE1X.hostedservice2.net"
type="cite">
<pre wrap="">Alas I don't think that that is going to be flexible enough. In order
to do that we would need more flexibility within cmake for the
generation of the vcproj files, as it only knows about conventional
builds. For example Xbox360 builds don't have a VCCLCompilerTool,
instead having a
VCCLX360CompilerTool.
I guess that answers my question - If I want custom vcproj files I'll
have to write them myself, somehow.
</pre>
</blockquote>
To address this issue I had to patch the cmake source files like this:<br>
<font face="Courier New, Courier, monospace"><br>
if(this->PlatformName == "XBox 360")<br>
{<br>
aCompilerTool = "VCCLX360CompilerTool";<br>
}<br>
else<br>
{<br>
aCompilerTool = "VCCLCompilerTool";<br>
}<br>
<br>
</font>Hopefully for us, the XBox 360 is the only platform that needs
this modification. The PS3 has a custom tool but it can be ignored
since it relies on settings of the default tools.<br>
<br>
There is another issue, the platform names in SLN files can have 2
different names:<br>
-one condensed name without any spaces<br>
-one full length name<br>
So you can encounter this kind of line :<br>
<font face="Courier New, Courier, monospace">{F064F4EF-CE8A-4613-885E-3E80C6683EF9}.runtime|XBox360.Build.0
= runtime|Xbox 360</font><br>
To address this we had to add a "Real name" member to the global
generator and set this real name in our top level CMakeLists.txt.<br>
<br>
Well, to handle Visual Studio nicely and completely is a big work. You
can fill a request feature here: <a class="moz-txt-link-freetext" href="http://www.cmake.org/Bug">http://www.cmake.org/Bug</a><br>
<br>
--Sylvain<br>
</body>
</html>