Neal Meyer a écrit :
Richard,This project organization is much better, Kudos. However, most of our directories include only a single project file so there seems to be a lot of redundant folders in this type of layout, so maybe a little additional feature that if there is only a single project in the directory don't add it's directory to the list as well (the project name is usually pretty close to the directory names). Also I'd like to see the CMake generated projects in their own folder to seperate them from the rest of the projects. A nice addition to this type of functionality might be to add functionality similar to SOURCE_GROUP() (i.e. PROJECT_GROUP), so that I can design the whacky project groupings that make sense for my project. -Neal
Hello,
I've already done this by creating a new command that is similar to SOURCE_GROUP. But it requires some work to be able to submit it to the CMake community. I put the work I've done, feel free to adapt it to your need and make it compilant to the CMake releases if you want.
The package includes: -the command cmSolutionGroupMPCommand -the modified global generator for VS2003 and VS2005-the GUID_Pool.txt used to always get the same GUIDs even when the CMakeCache.txt has been deleted (useful for projects under a CVS)
-an example (example.mpu) of our list where the projects are added.-the CMake script which reads this CMakeLists.txt in order to invoke and encapsulate the SOLUTION_GROUP command to the regular users.
--Sylvain
SolutionGroupMP.rar
Description: Binary data
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
