From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Randy Taylor <dev@rjt.dev>
Cc: Eli Zaretskii <eliz@gnu.org>, 54633@debbugs.gnu.org
Subject: bug#54633: [PATCH] * configure.ac: Fix --without-gif for W32, NS, Haiku, and PGTK.
Date: Wed, 30 Mar 2022 21:39:36 +0800 [thread overview]
Message-ID: <87h77fv9t3.fsf@yahoo.com> (raw)
In-Reply-To: <_VSsAZMe_TBK2D6Qs_LdHklodsyPeP8VC78M4YpEYWj7A3aRh6aDMeccUkdVqw7hjZ2QXxWAxBf_MqYBp8VI_3Q_gqL0B-Gl79AQPpwXFhY=@rjt.dev> (Randy Taylor's message of "Wed, 30 Mar 2022 13:34:22 +0000")
Randy Taylor <dev@rjt.dev> writes:
> If someone specifies "--without-gif", then Emacs should not build with
> gif support. That is why I made the check to apply for all
> systems. The same behaviour already applies to all the other formats,
> like SVG which I mentioned.
Emacs built without libgif on NS or Haiku will still result in a build
that can display GIF files, since native image APIs are enabled by
default on both those platforms. (On Haiku the relevant translator also
has to be installed, but it comes in a default installation.)
next prev parent reply other threads:[~2022-03-30 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 1:45 bug#54633: [PATCH] * configure.ac: Fix --without-gif for W32, NS, Haiku, and PGTK Randy Taylor
2022-03-30 5:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-30 12:13 ` Eli Zaretskii
2022-03-30 12:42 ` Randy Taylor
2022-03-30 13:27 ` Eli Zaretskii
2022-03-30 13:34 ` Randy Taylor
2022-03-30 13:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-03-30 13:46 ` Eli Zaretskii
2022-03-30 13:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-30 14:55 ` Randy Taylor
2022-04-04 14:09 ` Randy Taylor
2022-04-05 1:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87h77fv9t3.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54633@debbugs.gnu.org \
--cc=dev@rjt.dev \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.