This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [Patch] Add --identify option to dlltool
- From: Kai Tietz <Kai dot Tietz at onevision dot com>
- To: Christopher Faylor <cgf at sourceware dot org>
- Cc: binutils at sourceware dot org, cygwin at cwilson dot fastmail dot fm, Kai Tietz <ktietz70 at googlemail dot com>
- Date: Mon, 10 Nov 2008 09:20:26 +0100
- Subject: Re: [Patch] Add --identify option to dlltool
binutils-owner@sourceware.org wrote on 10.11.2008 02:39:13:
> 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
>
Well, I think I mixed-up here something. The --identify option to dlltool
is fine (as long as there are just import symbols from one dll within the
import-library). I am currently working on delayed dll loading feature an
so this kind of tag in COFF comments would be helpful.
Sorry for the noise,
Kai
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.