From: Robert Pluim <rpluim@gmail.com>
To: emacs-devel@gnu.org
Cc: Ari Roponen <ari.roponen@gmail.com>
Subject: Re: harfbuzz 2f72162: Fix crash in the Cairo build
Date: Fri, 14 Dec 2018 13:18:41 +0100 [thread overview]
Message-ID: <m2y38scndq.fsf@gmail.com> (raw)
In-Reply-To: <20181214085418.6616820538@vcs0.savannah.gnu.org> (Eli Zaretskii's message of "Fri, 14 Dec 2018 03:54:18 -0500 (EST)")
eliz@gnu.org (Eli Zaretskii) writes:
> diff --git a/src/ftcrfont.c b/src/ftcrfont.c
> index e2f84d4..6d74d93 100644
> --- a/src/ftcrfont.c
> +++ b/src/ftcrfont.c
> @@ -41,6 +41,9 @@ struct ftcrfont_info
> bool maybe_otf; /* Flag to tell if this may be OTF or not. */
> OTF *otf;
> #endif /* HAVE_LIBOTF */
> +#ifdef HAVE_HARFBUZZ
> + hb_font_t *hb_font;
> +#endif /* HAVE_HARFBUZZ */
> FT_Size ft_size;
> int index;
> FT_Matrix matrix;
Eli, what would be your preferred type of solution to avoid this in
future? A #define of the common portion of the structs in ftfont.h? An
embedded 'struct ft_font_fixed' member inside struct ft{,cr}font_info?
Something else? At the very least I propose syncing the comments:
diff --git i/src/ftcrfont.c w/src/ftcrfont.c
index e2f84d44fc..7d63a344ec 100644
--- i/src/ftcrfont.c
+++ w/src/ftcrfont.c
@@ -35,12 +35,16 @@ along with GNU Emacs. If not, see <https://www.gnu.org/licenses/>. */
struct ftcrfont_info
{
struct font font;
- /* The following six members must be here in this order to be
- compatible with struct ftfont_info (in ftfont.c). */
+ /* The following members up to and including 'matrix' must be here
+ in this order to be compatible with struct ftfont_info (in
+ ftfont.c). */
#ifdef HAVE_LIBOTF
bool maybe_otf; /* Flag to tell if this may be OTF or not. */
OTF *otf;
#endif /* HAVE_LIBOTF */
+#ifdef HAVE_HARFBUZZ
+ hb_font_t *hb_font;
+#endif /* HAVE_HARFBUZZ */
FT_Size ft_size;
int index;
FT_Matrix matrix;
diff --git i/src/ftfont.c w/src/ftfont.c
index a645bbf029..ef4ccab3ec 100644
--- i/src/ftfont.c
+++ w/src/ftfont.c
@@ -56,8 +56,9 @@ struct ftfont_info
{
struct font font;
#ifdef HAVE_LIBOTF
- /* The following four members must be here in this order to be
- compatible with struct xftfont_info (in xftfont.c). */
+ /* The following members up to and including 'matrix' must be here in
+ this order to be compatible with struct xftfont_info (in
+ xftfont.c). */
bool maybe_otf; /* Flag to tell if this may be OTF or not. */
OTF *otf;
#endif /* HAVE_LIBOTF */
next parent reply other threads:[~2018-12-14 12:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181214085417.15440.18845@vcs0.savannah.gnu.org>
[not found] ` <20181214085418.6616820538@vcs0.savannah.gnu.org>
2018-12-14 12:18 ` Robert Pluim [this message]
2018-12-14 13:29 ` harfbuzz 2f72162: Fix crash in the Cairo build Eli Zaretskii
2018-12-14 14:09 ` Robert Pluim
2018-12-14 16:16 ` Robert Pluim
2018-12-14 16:45 ` Eli Zaretskii
2018-12-17 12:41 ` Robert Pluim
2018-12-17 17:39 ` Eli Zaretskii
2018-12-18 8:49 ` Robert Pluim
2018-12-18 13:01 ` Robert Pluim
2019-02-08 8:01 ` Robert Pluim
2019-02-08 8:04 ` Robert Pluim
2019-02-08 8:06 ` Robert Pluim
2019-02-08 9:37 ` Eli Zaretskii
2019-02-08 11:46 ` Robert Pluim
2019-02-08 13:14 ` Eli Zaretskii
2019-02-08 14:38 ` Robert Pluim
2019-02-08 16:11 ` Eli Zaretskii
2019-02-08 16:41 ` Robert Pluim
2019-02-08 21:29 ` Eli Zaretskii
2019-02-09 19:20 ` Glenn Morris
2019-02-09 19:34 ` Eli Zaretskii
2019-02-10 14:47 ` Stefan Monnier
2019-02-10 15:28 ` Eli Zaretskii
2019-02-10 18:18 ` Stefan Monnier
2019-02-10 18:48 ` Eli Zaretskii
2019-02-10 18:52 ` Stefan Monnier
2019-02-11 9:56 ` Robert Pluim
2019-02-10 18:30 ` Glenn Morris
2019-02-10 14:57 ` Eli Zaretskii
2019-02-10 18:36 ` Glenn Morris
2019-02-11 15:33 ` Eli Zaretskii
2018-12-17 21:49 ` Paul Eggert
2018-12-18 8:23 ` Robert Pluim
2018-12-19 8:32 ` Robert Pluim
2018-12-19 15:06 ` Eli Zaretskii
2018-12-14 20:25 ` Stefan Monnier
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=m2y38scndq.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ari.roponen@gmail.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 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.