Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Tue, 18 Jun 2002 21:03:43 +0200 From: Corinna Vinschen To: cygwin-apps AT cygwin DOT com Subject: Re: RFD: gettext, iconv, packaging... Message-ID: <20020618210343.V30892@cygbert.vinschen.de> Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <3D0F798E DOT 70101 AT ece DOT gatech DOT edu> <3D0F7B37 DOT 4000501 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D0F7B37.4000501@ece.gatech.edu> User-Agent: Mutt/1.3.22.1i On Tue, Jun 18, 2002 at 02:25:59PM -0400, Charles Wilson wrote: > FYI, the new gettext package is NOT imminent. There are some variables > exported from cyggettext*.dll to the msg*.exe programs that are not > auto-importable. (direct access to elements in an array of structs). > > So, I need to muck with the code some -- and add accessor functions or > something. So this will take a while. Fortunately, since these are > "private" DLLs, I'm not changing the "external API" outside of the > gettext package itself. If only these two tools are using cyggettext*.dll and the other one, why not linking statically against them? I don't see a reason to have dlls hanging around for that purpose. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.