Hello,

On 5/14/17 1:17 AM, James Touton wrote:
> The Xcode generator currently attempts to set the lastKnownFileType
> attribute for every source file in a target.  There's a property that
> allows the user to set this value explicitly, but if the property is not
> set, the generator comes up with an appropriate value based on the file
> extension.  For any file extension the generator does not know about, it
> set a value of "sourcecode".
> 
> I'd like to remove all of these defaults.  In all cases I'm aware of, Xcode
> will fill in the same value that CMake does, except that it doesn't default
> to the "sourcecode" value for extensions it doesn't know about.  Xcode has
> a much wider set of known file types than CMake does, and can do a much
> better job filling in these values.
> 
> In particular, I'd most like to get rid of the "sourcecode" default,
> because that tends to completely screw up syntax highlighting for file
> types that Xcode already knows about.
> 
> Would there be any objection to me submitting a pull request for any of the
> above?

I'd welcome any attempts to simplify the Xcode generator. But before I'd
ack such a PR I'd like to know why this functionality was added in the
first place. CMake still supports (does not actively break) Xcode 3. If
there is no answer to that question: maybe you could test and limit your
changes to a newer Xcode version (like 5 or above).

Thanks,
Gregor
-- 

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

Reply via email to