On Tuesday 10 April 2012, David Cole wrote: > If you would like to construct a git commit (based on the present > 'master' branch), and then attach the patch produced by: > > git format-patch -1 > > to the issue at http://public.kitware.com/Bug/view.php?id=9126, then > we will consider it for inclusion in a future CMake release. > > Seems like the easiest thing to do, at least for your case, would > simply be add the "nasm" file extension to the code in the recently > factored-out function GetSourcecodeValueFromFileExtension in > Source/cmGlobalXCodeGenerator.cxx. Adding more known file types to > that function will help us keep CMakeLists from being cluttered with > too many required source file properties.
Handling of nasm files should be coupled to having the ASM_NASM language enabled, that's what has to be done for the makefile-based generators. I think the CMakeLists.txt for xcode should do the same. Modules/CMakeASM_NASMInformation.cmake lists .nasm and .asm as known file extensions. Alex -- 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
