all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Cecilio Pardo <cpardo@imayhem.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73730@debbugs.gnu.org
Subject: bug#73730: 31.0.50; Support for color fonts on MS-Windows
Date: Tue, 29 Oct 2024 09:57:11 +0100	[thread overview]
Message-ID: <9f9d0445-b53c-408c-ba1d-6e9c1b4eaf17@imayhem.com> (raw)
In-Reply-To: <86a5ep8ihi.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 158 bytes --]

I've built HarfBuzz with the attached patch with mingw, using

g++ src/harfbuzz.cc --shared -o libharfbuzz-0.dll --no-exceptions

and it seems to work fine.


[-- Attachment #2: 0001-harbuzz-mingw.patch --]
[-- Type: text/plain, Size: 950 bytes --]

From a5902ab42ae6dcfa8cded0b0e731691e4d8f7105 Mon Sep 17 00:00:00 2001
From: Cecilio Pardo <cpardo@imayhem.com>
Date: Tue, 29 Oct 2024 09:21:14 +0100
Subject: [PATCH] ..

---
 src/harfbuzz.cc | 4 ++++
 src/hb.hh       | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/harfbuzz.cc b/src/harfbuzz.cc
index 9ff800daa..486e44bf3 100644
--- a/src/harfbuzz.cc
+++ b/src/harfbuzz.cc
@@ -1,3 +1,6 @@
+#define WINAPI_PARTITION_DESKTOP 1
+#define WINAPI_FAMILY_PARTITION(x) (x)
+
 #include "OT/Var/VARC/VARC.cc"
 #include "hb-aat-layout.cc"
 #include "hb-aat-map.cc"
@@ -62,3 +65,4 @@
 #include "hb-uniscribe.cc"
 #include "hb-wasm-api.cc"
 #include "hb-wasm-shape.cc"
+
diff --git a/src/hb.hh b/src/hb.hh
index fe466fe1f..9c54bc3bd 100644
--- a/src/hb.hh
+++ b/src/hb.hh
@@ -216,7 +216,7 @@
 
 #ifdef _WIN32
 #include <windows.h>
-#include <winapifamily.h>
+// #include <winapifamily.h>
 #endif
 
 #ifndef PRId32
-- 
2.35.1.windows.2


  reply	other threads:[~2024-10-29  8:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 11:16 bug#73730: 31.0.50; Support for color fonts on MS-Windows Cecilio Pardo
2024-10-10 13:08 ` Eli Zaretskii
2024-10-10 15:14   ` Cecilio Pardo
2024-10-10 16:33     ` Eli Zaretskii
2024-10-10 16:46       ` Cecilio Pardo
2024-10-15 22:18   ` Cecilio Pardo
2024-10-16 11:01     ` Eli Zaretskii
2024-10-16 11:32       ` Eli Zaretskii
2024-10-16 21:35       ` Cecilio Pardo
2024-10-17  6:21         ` Eli Zaretskii
2024-10-17 10:38           ` Cecilio Pardo
2024-10-20 13:35             ` Cecilio Pardo
2024-10-20 13:55               ` Eli Zaretskii
2024-10-22 22:14                 ` Cecilio Pardo
2024-10-23 10:03                   ` Eli Zaretskii
2024-10-23 14:17                     ` Cecilio Pardo
2024-10-23 17:53                       ` Eli Zaretskii
2024-10-24 20:19                         ` Cecilio Pardo
2024-10-25  7:26                           ` Eli Zaretskii
2024-10-25 10:17                             ` Cecilio Pardo
2024-10-25 12:00                               ` Eli Zaretskii
2024-10-26 20:13                                 ` Cecilio Pardo
2024-10-27  6:36                                   ` Eli Zaretskii
2024-10-27 13:32                                     ` Eli Zaretskii
2024-10-27 13:41                                       ` Cecilio Pardo
2024-10-27 15:44                                       ` Cecilio Pardo
2024-10-27 16:54                                         ` Eli Zaretskii
2024-10-27 17:50                                           ` Cecilio Pardo
2024-10-27 19:15                                             ` Eli Zaretskii
2024-10-29  8:57                                               ` Cecilio Pardo [this message]
2024-10-25 11:51                           ` Eli Zaretskii
2024-10-25 13:43                             ` Cecilio Pardo
2024-10-20 16:17               ` Eli Zaretskii
2024-10-20 18:20                 ` Cecilio Pardo
2024-10-20 18:33                   ` Eli Zaretskii
2024-10-20 18:37                     ` Cecilio Pardo
2024-10-10 21:50 ` Cecilio Pardo
2024-10-11  3:36   ` Eli Zaretskii
2024-10-11  6:28     ` Eli Zaretskii
2024-10-11  7:19       ` Cecilio Pardo

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=9f9d0445-b53c-408c-ba1d-6e9c1b4eaf17@imayhem.com \
    --to=cpardo@imayhem.com \
    --cc=73730@debbugs.gnu.org \
    --cc=eliz@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.