public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tor Lillqvist <tml@iki.fi>
To: cygwin@sources.redhat.com
Subject: Re[2]: DLL naming conventions
Date: Thu, 31 Aug 2000 11:28:00 -0000	[thread overview]
Message-ID: <14766.41758.390000.471560@gargle.gargle.HOWL> (raw)
In-Reply-To: <3623.000831@is.lg.ua>

Paul Sokolovsky writes:
 > GIMP's stupid shrink-wrapped installer drop its to
 > windows/system).

No it doesn't. (It did at some point, a long time ago.) Currently it
puts the DLLs in \Program Files\Common Files\GNU.

Currently the GIMP for Windows does not use DLLs for the JPEG, Zlib or
TIFF libraries, precisely because of the lack of consensus in naming
etc. And if there is anything to learn from this discussion, it is
that it is best to stick to static libraries in the future, too...

One point that has not been brought up here is that it is not enough
that some library's API is stable, like for instance zlib. The ABI
must also be identical in order to be able to share the same DLL
between applications from different sources. With this I am thinking
of struct packing issues, i.e. whether gcc compilations use
-fnative-struct (MSVC-compatible bitfield packing) or not.

Sorry that this is mostly off-topic to the cygwin list.

--tml


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  parent reply	other threads:[~2000-08-31 11:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-30  3:36 Paul Sokolovsky
2000-08-30  7:26 ` Chris Faylor
2000-08-31  4:21   ` Re[2]: " Paul Sokolovsky
2000-08-31  8:56     ` Chris Faylor
2000-09-01  9:10       ` Re[2]: " Paul Sokolovsky
2000-08-31 18:05     ` Gary V. Vaughan
2000-08-30  7:48 ` Charles Wilson
2000-08-30  7:52   ` Chris Faylor
2000-08-30  8:07     ` Norman Vine
2000-08-30  8:17       ` Charles Wilson
2000-08-30  8:19         ` Charles Wilson
2000-08-30 11:37         ` Chris Faylor
2000-08-31  5:14           ` Re[2]: " Paul Sokolovsky
2000-08-30  8:11     ` Charles Wilson
2000-08-31  5:07   ` Re[2]: " Paul Sokolovsky
2000-08-31  8:58     ` Charles S. Wilson
2000-08-31 11:28     ` Tor Lillqvist [this message]
2000-08-31 11:47       ` Chris Faylor
2000-08-31 12:07         ` Larry Hall (RFK Partners, Inc)
     [not found]   ` <20000831230822.R7695@demon.co.uk>
2000-08-31 18:58     ` Charles S. Wilson
2000-09-02  6:56       ` Gary V. Vaughan
2000-08-31 20:27 ` Charles S. Wilson
2000-08-31  6:52 Re[2]: " Earnie Boyd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14766.41758.390000.471560@gargle.gargle.HOWL \
    --to=tml@iki.fi \
    --cc=cygwin@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).