unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: emacs-devel@gnu.org
Subject: Re: What version of harfbuzz is required?
Date: Wed, 11 Nov 2020 16:38:24 +0000	[thread overview]
Message-ID: <87pn4jhmrj.fsf@yandex.com> (raw)
In-Reply-To: <87sg9fhoba.fsf@gmail.com> (Robert Pluim's message of "Wed, 11 Nov 2020 17:04:57 +0100")

Hello Robert,
>>>>> Robert Pluim <rpluim@gmail.com> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >> Hello,
    >> 
    >> When building emacs from master I get the warning:
    >> 
    >> WARNING: 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.
    >> 
    >> I have harfbuzz bin and dev libraries (0.9.35-2+deb8u1)
    >> installed, but presumably they are too old. I am using i686
    >> GNU/Linux 3.16.0-11-686-pae #1 SMP Debian 3.16.84-1 (2020-06-09).
    >> 
    >> What minimal harfbuzz version do I need?

    > From configure.ac:

    >     if test "${HAVE_W32}" = "yes"; then
    > EMACS_CHECK_MODULES([HARFBUZZ], [harfbuzz >= 1.2.3]) else
    > EMACS_CHECK_MODULES([HARFBUZZ], [harfbuzz >= 0.9.42]) fi

    > 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.

    > 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' :-)

Thanks.



Colin.



  reply	other threads:[~2020-11-11 16:38 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 [this message]
2020-11-12 11:06     ` Robert Pluim
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=87pn4jhmrj.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-devel@gnu.org \
    /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).