Re: [cdt-dev] managed make & binary parser problem

["Alain Magloire" <alain@xxxxxxx>]

> 
> I'm working on a binary parser for Mach-O, and I've run into a small 
> problem.  When I create a managed make project, my parser can't locate 
> addr2line or c++filt.  The tools addr2line and c++filt are not in my 
> search path, but are fully qualified on the preferences page.  If I 
> create a standard make project, my parser can locate the tools just 
> fine.  Tracing through the code to the lines:
> 
> 		ICExtensionReference ref = getExtensionReference();
> 		String value =  ref.getExtensionData("addr2line"); //$NON-NLS-1
> 
> shows that value == null when I create a managed make project, and 
> non-null for a standard make project.  It appears that the managed make 
> project is not using the values set in the binary parser perference 
> page.  Is there something I missed with the managed make code?
> 

(Sean could correct me on this):
I do not think that the managed make takes advantage of this.
Probably  lacking time, when the features were push in.
ManagedMake already defines the type of binary parser for the platform/target, (see
org.eclipse.cdt.managedbuilder.ui/plugin.xml), so it discard any global preferences.

I suggest a PR on this, so I could reassign to the owner.