The organization name setting for a given Xcode project is primarily (only?) used to fill out copyright notices in file templates for various languages. It doesn't have any other effects to my knowledge. The only official documentation I can find seems to agree with me (https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringYourApp/ConfiguringYourApp.html): “The organization name is an attribute of the Xcode project and is used in boilerplate text throughout your project folder. For example, the organization name is used in the source and header file copyright strings.” To understand the motivation behind this change: my team's workflow generally involves creating new source files from within Xcode (and then adding those files to a target in the relevant CMakeLists.txt file) since it handily populates the new files with the aforementioned header comments—and with this change, we no longer have to manually add the copyright string. (We certainly don't intend to redistribute the CMake-generated Xcode project files.)
Updated patch attached. Thanks! Cody |
v2-0001-Add-support-for-Xcode-ORGANIZATIONNAME-project-se.patch
Description: Binary data
-- Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
