This is the mail archive of the
mailing list for the GCC project.
Re: Specifying command line arguments in a file?
- To: gcc at gcc dot gnu dot org
- Subject: Re: Specifying command line arguments in a file?
- From: Albert Chin-A-Young <china at thewrittenword dot com>
- Date: Tue, 1 May 2001 13:37:52 -0500
- Cc: Robert Boehne <rboehne at ricardo-us dot com>
- References: <firstname.lastname@example.org> <20010430140708D.email@example.com>
On Mon, Apr 30, 2001 at 02:07:08PM -0700, Mark Mitchell wrote:
> >>>>> "Geoff" == Geoff Keating <firstname.lastname@example.org> writes:
> Geoff> Robert Schweikert <email@example.com> writes:
> >> IS there a secret handshake between gcc and ld to get a large
> >> number of object files to be linked to ld without going through
> >> exce and without trying to mangle up a linker script?
> Geoff> Typically you put the object files in a .a library.
> Yeah, but if there are really tons of them then you can't build *that*
> command-line either, so you end up building the library .o file by .o
> file, which is a pain, too. And anyhow a .a has different semantics,
> unless you have --full-archive available.
> For full generality, you just can't get around this problem.
> We need to bite the bullet and implement -@. In fact, we should do it
> in libiberty: write a routine to transform a file into an argv array.
> Then, we can bury whatever weird quoting semantics we want in there,
> and use this code everywhere.
I think Robert Boehne <firstname.lastname@example.org> fixed such a problem in
libtool. Maybe he can comment on his solution?
albert chin (email@example.com)