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.

To address this issue I had to patch the cmake source files like this:

          if(this->PlatformName == "XBox 360")
          {
              aCompilerTool = "VCCLX360CompilerTool";
          }
          else
          {
              aCompilerTool = "VCCLCompilerTool";
          }

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.

There is another issue, the platform names in SLN files can have 2 different names:
-one condensed name without any spaces
-one full length name
So you can encounter this kind of line :
{F064F4EF-CE8A-4613-885E-3E80C6683EF9}.runtime|XBox360.Build.0 = runtime|Xbox 360
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.

Well, to handle Visual Studio nicely and completely is a big work. You can fill a request feature here: http://www.cmake.org/Bug

--Sylvain

_______________________________________________
CMake mailing list
CMake@...
http://www.cmake.org/mailman/listinfo/cmake