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

[Sean Evoy <sevoy@xxxxxxxxxx>]

Alain,
You have it exactly right. Please raise
a bugzilla report and we'll add it to the work items for 2.0. Thanks and
good catch.


Sean Evoy
Rational Software - IBM Software Group
Ottawa, Ontario, Canada

"Alain Magloire" <alain@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx

11/26/2003 11:41 AM

Please respond to
cdt-dev

To	cdt-dev@xxxxxxxxxxx
cc
Subject	Re: [cdt-dev] managed make & binary parser problem

> 
> 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.


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev