delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/04/16/11:59:18

From: cgf AT cygnus DOT com (Christopher G. Faylor)
Subject: Re: New import library format proposal.
16 Apr 1998 11:59:18 -0400 :
Distribution: cygnus
Message-ID: <6h59sm$4uu$1@tweedledumb.cygnus.com>
References: <6h575d$3g0$1 AT tweedledumb DOT cygnus DOT com> <199804161546 DOT LAA22622 DOT cygnus DOT cygwin32 DOT developers AT subrogation DOT cygnus DOT com>

In article <199804161546 DOT LAA22622 DOT cygnus DOT cygwin32 DOT developers AT subrogation DOT cygnus DOT com>,
Ian Lance Taylor <ian AT cygnus DOT com> wrote:
>   Date: 16 Apr 1998 11:12:45 -0400
>   From: cgf AT cygnus DOT com (Christopher G. Faylor)
>
>   I've been dreaming about this for a while, too.  Is there any reason,
>   other than speed, that dlltool couldn't emit C code to generate its
>   import library?  That would make this slightly easier to play with.
>
>It would make it a lot harder to incorporate the dlltool functionality
>into the linker.  The linker can't reasonably invoke the compiler.  It
>leads into a lot of problems about locating the precise compiler to
>use and the precise set of options to pass it.

Yeah.  I realized that about ten seconds after I sent the email.

Is it even acceptable for the linker to invoke as?
-- 
cgf AT cygnus DOT com             "Everything has a boolean value, if you stand
http://www.cygnus.com/      far enough away from it."  -- Galena Alyson Canada

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019