> It is (forced by backwards compatibility requirements) by design. >
> Here is the source code where I wanted to assign it to the CMakePredefinedTargetsFolder: > > #if 0 > // Can't activate this code because we want ALL_BUILD > // selected as the default "startup project" when first > // opened in Visual Studio... And if it's nested in a > // folder, then that doesn't happen. > // > // Organize in the "predefined targets" folder: > // > if (this->UseFolderProperty()) > { > allBuild->SetProperty("FOLDER", this->GetPredefinedTargetsFolder()); > } > #endif > > > Sorry, > David Is there some reason that couldn't be a property as well? Or possibly a Policy? I'm not sure I understand 1) why ALL_BUILD couldn't be the default project from within a folder, and 2) why it needs to be the default project (beyond backward compatibility.). This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake