public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: [BUG ?] Re: [ANNOUNCEMENT] Updated: {libpng/libpng14/libpng14-devel}-1.4.8-1
Date: Tue, 15 Nov 2011 02:21:00 -0000	[thread overview]
Message-ID: <4EC1CCA9.1000803@cwilson.fastmail.fm> (raw)
In-Reply-To: <1321304963.7884.1.camel@YAAKOV04>

On 11/14/2011 4:09 PM, Yaakov (Cygwin/X) wrote:
> On Sun, 2011-11-13 at 15:35 +0100, Dr. Volker Zell wrote:
>> This version dosn't export png_info_init
>> whereas libpng-1.2 does
>> Is this intednded ?
>
> http://www.libpng.org/pub/png/src/libpng-1.2.x-to-1.4.x-summary.txt

To expand on Yaakov's answer, yes -- this is intended.  The libpng API 
changes with each major release, which is why the DLL name gets "bumped" 
in each case.  libpng14-1.4.x-y provides cygpng14-14.dll, while 
libpng12-1.2.x-y provided cygpng12.dll.

FWIW, the png team has abandoned even/odd numbering to designate 
stable/development releases. Hence, the 1.5.x series is now the 
"current" stable release -- our "new" libpng-1.4.x is already obsolete. 
I'll publish libpng15 before Christmas (by which time, of course, 
libpng-1.6 will be stable).

--
Chuck


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2011-11-15  2:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201107280609.p6S69LDG005105@rcsinet12.oracle.com>
2011-11-13 14:34 ` Dr. Volker Zell
2011-11-14 21:09   ` Yaakov (Cygwin/X)
2011-11-15  2:21     ` Charles Wilson [this message]

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=4EC1CCA9.1000803@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin@cygwin.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).