these projects will need to use code from the current VC++ 2010 generator. In this situation: (1) C++ projects need to be generated using the C++ project generation code in the existing VS2008 generator, (2) C# projects need to be generated using an MSBuild generator, which is very different from the VS2008 C++ project format - i.e. So they pick the normal VS2008 generator. To elaborate on the C# example some more, suppose the user wants to generate a Visual Studio 2008 solution. all MSBuild, or not), and this is not true. Right now, CMake makes the assumption that the language project file format of each VS version is basically identical (e.g. And to do that I think requires decoupling the language from the project file generator. Ideally you really want to be able to: (1) build C# 2005/2008 projects, (2) use more efficient tools like Ninja. IIRC the author's code works for generating Visual C# 2013 projects using the Visual C++ 2013 generator, but that's it. I skimmed through some of the commits to see how he is doing it while helpful, I think there are some shortcomings that may not be easy to fix without some preliminary work related to Visual Studio project generation. Another feature I would use tomorrow if it worked well. * Recently there have been mailings from Michael Stuermer about adding C# as a language CMake. The MSBuild system has serious concurrency issues resulting in serious over/undersubscription. I would be very happy if this feature existed and would use it tomorrow. Presumably this generator will have to share a lot of code with the regular VS2015 generator. This would run Ninja in background to do the building, while retaining the IDE. For example, specification of "Visual Studio 2015 - Ninja" (much like how you can do "CodeBlocks - Ninja" today, etc.). In this case, it would be useful to have Visual Studio available as an "Extra" CMake generator. If a C# 2008 project is needed, the back-end MSBuild generator is used. If a VC++ 2008 project is needed, the back-end VC2008 generator is used. (Perhaps the back-end generators could be tools reused by existing normal "Visual Studio 2008" CMake generators and so on). Then instead of Visual C++ 2010 generator, we have back-end MSBuild generator. Example: instead of Visual C++ 2008 generator, we have a back-end generator for VC++2005/2008 projects. Not that I have time to work on it right now, and I have not studied this section of CMake code in detail, so I may be a little off base with some of this - please bear with me. Recently I have wondered if it would be useful if the Visual Studio generators in CMake were refactored somewhat (to what degree, I am not sure). Previous message: Visual Studio - Ninja Generator.Visual Studio - Ninja Generator James Johnston JamesJ at
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |