[CMake] CMake 2.8.7 + XCode generator + nasm files

[David Cole]

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.


HTH,
David


On Tue, Apr 10, 2012 at 12:39 PM, Damien Chavarria <roy204 at gmail.com> wrote:
>
> Hi all,
>
> Nobody has any insigth on this ? Should I give up ?
>
> Cheers,
> Damien.
>
>
>
> On Fri, Apr 6, 2012 at 9:36 AM, Damien Chavarria <roy204 at gmail.com> wrote:
>>
>>
>> Hi all,
>>
>> Sorry for reviving what seems like a previously discussed issue, but I've
>> been unable to find whether a resolution was reached.
>>
>> Here is the problem:
>>
>> I have .nasm files in my project, and when I add them to a target and then
>> use the XCode generator on a mac, they appear in the list of source files to
>> be compiled for that target in the XCode project but they don't actually do
>> when building it (XCode complains to the effect of "no rule to build
>> xxx.nasm for architecture yyy"). I noticed that the "file type" for the NASM
>> file in XCode (select the .nasm file in the target and right-click -> "Get
>> Info") shows as "sourcecode". Simply setting this to "sourcecode.nasm" makes
>> XCode happy and the file then builds.
>>
>> I later found a previous post about this problem in the list :
>> http://www.cmake.org/pipermail/cmake/2009-June/030017.html
>> And a subsequent feature request :
>> http://public.kitware.com/Bug/view.php?id=9126
>>
>> All this dates back from 2009 and I see no resolution on the feature
>> request so I'm not sure what was decided.
>> Is there a way to fix this from CMakeLists.txt that I missed ?
>>
>> If not, I'd be more than happy to submit a patch for the feature, if
>> that's desirable.
>>
>> Thanks all and have a nice day,
>> Damien.
>>
>>
>
>
> --
>
> 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