From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] giflib: fix description about compatibility with libungif
Date: Sun, 12 Apr 2015 12:08:34 +0300 [thread overview]
Message-ID: <20150412090834.GI2279@tarshish> (raw)
In-Reply-To: <CAHkwnC8W0A+GTHiVuTo1D5ViNzbr8NjvZd-hO5+YGDAB+RhTHA@mail.gmail.com>
Hi Fabio,
On Sun, Apr 12, 2015 at 10:57:40AM +0200, Fabio Porcedda wrote:
> On Sun, Apr 12, 2015 at 10:47 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Sun, Apr 12, 2015 at 10:43:05AM +0200, Fabio Porcedda wrote:
> >> Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
> >> ---
> >> package/giflib/Config.in | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/package/giflib/Config.in b/package/giflib/Config.in
> >> index 70368dc..bb5741a 100644
> >> --- a/package/giflib/Config.in
> >> +++ b/package/giflib/Config.in
> >> @@ -1,7 +1,7 @@
> >> config BR2_PACKAGE_GIFLIB
> >> bool "giflib"
> >> help
> >> - giflib is a library for reading and writing gif images. It is API and
> >> + giflib is a library for reading and writing gif images. It was API and
> >> ABI compatible with libungif which was in wide use while the LZW
> >> compression algorithm was patented.
> >
> > So giflib is not compatible to libungif anymore?
>
> Just comparing the gif_lib.h header you can see that the definition of
> some functions changes:
>
> git diff --no-index libungif-4.1.4/lib/gif_lib.h giflib-5.1.1/lib/gif_lib.h
>
> GifFileType *EGifOpenFileName(const char *GifFileName,
> - int GifTestExistance);
> -GifFileType *EGifOpenFileHandle(int GifFileHandle);
> -GifFileType *EGifOpen(void *userPtr, OutputFunc writeFunc);
> -
> + const bool GifTestExistence, int *Error);
> +GifFileType *EGifOpenFileHandle(const int GifFileHandle, int *Error);
> +GifFileType *EGifOpen(void *userPtr, OutputFunc writeFunc, int *Error);
> int EGifSpew(GifFileType * GifFile);
If this is the case I would use a more explicit language. Something like:
giflib used to be API and ABI compatible with libungif which ... Note that
recent gitlib versions are no longer compatible with libungif.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-04-12 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 8:43 [Buildroot] [PATCH] giflib: fix description about compatibility with libungif Fabio Porcedda
2015-04-12 8:47 ` Baruch Siach
2015-04-12 8:57 ` Fabio Porcedda
2015-04-12 9:08 ` Baruch Siach [this message]
2015-04-12 9:13 ` Yann E. MORIN
2015-04-12 10:04 ` Fabio Porcedda
2015-04-12 9:10 ` Yann E. MORIN
2015-04-12 10:21 ` Fabio Porcedda
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=20150412090834.GI2279@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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