[CMake] Bug for Eclipse Generator for 64-Bit Mac OS X

[Alexander Neundorf]

On Wednesday 28 August 2013, David D. Marshall wrote:
> I am a long time user of CMake, and I find it very valuable. Thanks for the
> great tool.
> 
> I recently started using Eclipse on my 64-bit Mac OS X (version 10.8.4 if
> that is important) for my projects. The problem is that every time I
> regenerate my project file (i.e., a CMakeLists.txt file changed) the
> binary parser gets set to Mach-O Parser and not the Mach-0 64 Parser. What
> results is that eclipse won't run the code via the debugger, I get the
> error "Launch failed: Binary not found". To fix it I need to go to the
> project properties and change the parser back to the 64-bit parser.
> 
> I've tracked down the problem to cmExtraEclipseCDT4Generator.cxx line 724
> (version from git). Here's the code:
> 
>     else if (systemName == "Darwin")
>       {
>       fout << "<extension id=\"org.eclipse.cdt.core.MachO\""
>               " point=\"org.eclipse.cdt.core.BinaryParser\">\n"
>               "<attribute key=\"c++filt\" value=\"c++filt\"/>\n"
>               "</extension>\n"
>               ;
>       }
> 
> This is for the old parser that apparently is going to be removed soon (see
> the eclipse bug tracker discussion
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270790). Since version 6.0.2
> the 64-bit parser has been supported and is the preferred binary parser, I
> believe. I don't know the best change to keep versions prior to 6.0.2
> supported, but I think that the following code will set the parser to the
> more recent one and stop me from having to manually set the binary parser
> every time the eclipse project gets rebuilt:
> 
>     else if (systemName == "Darwin")
>       {
>       fout << "<extension id=\"org.eclipse.cdt.core.MachO64\""
>               " point=\"org.eclipse.cdt.core.BinaryParser\">\n"
>               "<attribute key=\"c++filt\" value=\"c++filt\"/>\n"
>               "</extension>\n"
>               ;
>       }
> 
> I hope I've provided enough info to get a fix for this problem, if there's
> anything else I can do let me know.


It would be great if you could add that as a ticket to the cmake bug tracker 
at http://public.kitware.com/Bug/ , then I won't forget it.

Alex