all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: HarfBuzz is available on MS-Windows
Date: Sun, 02 Jun 2019 21:56:52 +0300	[thread overview]
Message-ID: <837ea3vmrv.fsf@gnu.org> (raw)
In-Reply-To: <87a7ezn7uj.fsf@russet.org.uk> (phillip.lord@russet.org.uk)

> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: emacs-devel@gnu.org
> Date: Sun, 02 Jun 2019 19:46:28 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > The harfbuzz branch can now be built on MS-Windows, and will support
> > the new 'harfbuzz' font backend if the requisite DLLs are installed.
> >
> > HarfBuzz DLLs are available from the MSYS2 project and from ezwinports
> > (the latter only for 32-bit builds).
> 
> What are those dependencies? I'd like to add them the scripts that build
> the dependency zips for windows on that branch, so that I don't have to
> remember to do it when the merge happens!

Sorry, I don't understand the question.  The HarfBuzz DLLs aren't
different from any other DLL you download from MSYS2, so the same
procedure should do, and should bring you all the DLLs on which
HarfBuzz depends.  Which are those depends on how the MSYS2 people
built HarfBuzz; they generally specify everything that's possible,
even if it makes little sense on Windows, but that's their decision.

If you refer to "the requisite DLLs" I mentioned, that was a reference
to libharfbuzz-0.dll itself, not to its dependencies.  The code loads
only that single DLL.



  reply	other threads:[~2019-06-02 18:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 13:57 HarfBuzz is available on MS-Windows Eli Zaretskii
2019-05-31 14:25 ` Óscar Fuentes
2019-05-31 14:59   ` Eli Zaretskii
2019-05-31 16:44     ` Óscar Fuentes
2019-05-31 17:13       ` Óscar Fuentes
2019-05-31 18:04         ` Eli Zaretskii
2019-05-31 19:35           ` Óscar Fuentes
2019-05-31 18:00       ` Eli Zaretskii
2019-05-31 20:53 ` Óscar Fuentes
2019-05-31 22:10   ` Óscar Fuentes
2019-06-01  6:36     ` Eli Zaretskii
2019-06-02 18:46 ` Phillip Lord
2019-06-02 18:56   ` Eli Zaretskii [this message]
2019-06-02 19:07     ` Phillip Lord
2019-06-02 20:36       ` Óscar Fuentes
2019-06-03  2:42         ` Eli Zaretskii
2019-06-03  3:27           ` Óscar Fuentes
2019-06-03  3:52             ` Eli Zaretskii
2019-06-03  4:07               ` Óscar Fuentes
2019-06-03  6:49                 ` Eli Zaretskii
2019-06-04  4:51 ` Tak Kunihiro
2019-06-04 14:16   ` Eli Zaretskii
2019-06-07 17:05 ` Andy Moreton
2019-06-07 20:00   ` Eli Zaretskii
2019-06-07 21:13     ` Andy Moreton
2019-06-08  6:18       ` Eli Zaretskii
2019-06-08 12:11         ` Andy Moreton
2019-06-08 12:45           ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2019-05-31 20:24 Angelo Graziosi
2019-06-01  6:13 ` Eli Zaretskii

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=837ea3vmrv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    /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.