This is the mail archive of the
mailing list for the binutils project.
Re: [RFC PATCH, binutils, ELF 9/11] Add support for creating import libraries
- From: Thomas Preudhomme <thomas dot preudhomme at foss dot arm dot com>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>, binutils at sourceware dot org
- Date: Thu, 14 Jul 2016 16:30:45 +0100
- Subject: Re: [RFC PATCH, binutils, ELF 9/11] Add support for creating import libraries
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <4727760.r7lFBcU4UC@e108577-lin> <firstname.lastname@example.org>
On Thursday 14 July 2016 14:41:10 Nick Clifton wrote:
> Hi Thomas,
> > +* Add support for creating an ELF import library when generating an
> > executable. + The import library can then be used by applications to
> > link against the + generated executable. The existing --out-implib
> > option is now available to + ELF targets for that purpose.
> Not to be a pedant, but to me that paragraph implies that "--out-implib" is
> the option to be used when an application wants to link against an import
> library, rather than the option to be used when creating an import library.
> How about this slight rewording ?
> * Extended the --out-implib=<file> option, previously restricted to x86 PE
> targets, to any ELF based target. This allows the generation of an
> import library for an ELF executable, which can then be used by another
> application to link against the executable.
Looks good, thanks.