From: Robert Pluim <rpluim@gmail.com>
To: Colin Baxter <m43cap@yandex.com>
Cc: emacs-devel@gnu.org
Subject: Re: What version of harfbuzz is required?
Date: Thu, 12 Nov 2020 12:06:49 +0100 [thread overview]
Message-ID: <87o8k2hm0m.fsf@gmail.com> (raw)
In-Reply-To: <87pn4jhmrj.fsf@yandex.com> (Colin Baxter's message of "Wed, 11 Nov 2020 16:38:24 +0000")
Colin Baxter <m43cap@yandex.com> writes:
> > and the configure output says: checking for harfbuzz >=
> > 0.9.42... yes
>
> Ok, 0.9.42. I suppose it's time to bite the bullet and upgrade my
> Debian.
The non-HarfBuzz code is still functional, and won't go away for a
while yet.
>
> > I guess we could put the version in the warning as well, but it
> > seems a little excessive.
>
> It could be useful in avoiding eye strain in searching the configure
> output for a mention of 'harfbuzz' :-)
You donʼt run ./configure in a shell inside emacs? ;-)
Eli, something like this OK for master?
diff --git i/configure.ac w/configure.ac
index f0c8e5210f..888b415148 100644
--- i/configure.ac
+++ w/configure.ac
@@ -3444,16 +3444,17 @@ AC_DEFUN
fi # "${HAVE_X11}" != "yes"
HAVE_HARFBUZZ=no
+### On MS-Windows we use hb_font_get_nominal_glyph, which appeared
+### in HarfBuzz version 1.2.3
+if test "${HAVE_W32}" = "yes"; then
+ harfbuzz_required_ver=1.2.3
+else
+ harfbuzz_required_ver=0.9.42
+fi
if test "${HAVE_X11}" = "yes" && test "${HAVE_FREETYPE}" = "yes" \
|| test "${HAVE_W32}" = "yes"; then
if test "${with_harfbuzz}" != "no"; then
- ### On MS-Windows we use hb_font_get_nominal_glyph, which appeared
- ### in HarfBuzz version 1.2.3
- if test "${HAVE_W32}" = "yes"; then
- EMACS_CHECK_MODULES([HARFBUZZ], [harfbuzz >= 1.2.3])
- else
- EMACS_CHECK_MODULES([HARFBUZZ], [harfbuzz >= 0.9.42])
- fi
+ EMACS_CHECK_MODULES([HARFBUZZ], [harfbuzz >= $harfbuzz_required_ver])
if test "$HAVE_HARFBUZZ" = "yes"; then
AC_DEFINE(HAVE_HARFBUZZ, 1, [Define to 1 if using HarfBuzz.])
### mingw32 and Cygwin-w32 don't use -lharfbuzz, since they load
@@ -5918,9 +5919,9 @@ m4_define
if test "${HAVE_CAIRO}" = "yes" && test "${HAVE_HARFBUZZ}" = no; then
AC_MSG_WARN([This configuration uses the Cairo graphics library,
- but not the HarfBuzz font shaping library. We recommend the use
- of HarfBuzz when using Cairo, please install HarfBuzz development
- packages.])
+ but not the HarfBuzz font shaping library (minimum version $harfbuzz_required_ver).
+ We recommend the use of HarfBuzz when using Cairo, please install
+ appropriate HarfBuzz development packages.])
fi
# Let plain 'make' work.
next prev parent reply other threads:[~2020-11-12 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 15:51 What version of harfbuzz is required? Colin Baxter
2020-11-11 16:04 ` Robert Pluim
2020-11-11 16:38 ` Colin Baxter
2020-11-12 11:06 ` Robert Pluim [this message]
2020-11-12 12:00 ` Colin Baxter
2020-11-12 14:44 ` Eli Zaretskii
2020-11-12 15:56 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8k2hm0m.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=m43cap@yandex.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).