This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] Add --identify option to dlltool


On Sun, Nov 09, 2008 at 11:46:53AM +0100, Kai Tietz wrote:
>2008/11/9 Brian Dessent <brian@dessent.net>:
>> Kai Tietz wrote:
>>
>>> I thought about this kind of extension. But wouldn't it be better (at
>>> least for COFF targets) to use the .drectve Section in object.
>>
>> It's not an extension.  The information is already there in the import
>> lib, the new flag just provides a straightforward way to dump it out.
>> Why does it make any sense to add a .drectve section to objects in the
>> import lib and duplicate the information in two places?  And besides, it
>> would mean that you'd have to rebuild every existing import lib out
>> there in the wild in order for 'dlltool --identify' to work.  The whole
>> point of adding this flag is so that libtool can use it, and that goal
>> isn't met very well if the flag only works with import libs newly
>> created with bleeding edge tools and not all the existing regular import
>> libs.
>
>I agree that the -identify option is working with existing import
>libraries, too. Well, my thoughts were in a more general way. To add
>to each object its source dll would help even to identify all related
>.dll's by an aggregated import library (which is at least possible).
>But I have no objections against the the dlltool's --identify option.

This is possible but what you are talking about is really a separate
proposal that does not, as far as I can tell, have any impact on
implementing this option.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]