unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Casey Banner <kcbanner@gmail.com>
To: 73159@debbugs.gnu.org
Subject: bug#73159: Fwd: bug#73159: 30.0.90; uniscribe / harfbuzz are not initialized on Windows, resulting in fallback to gdi
Date: Tue, 10 Sep 2024 14:56:28 -0400	[thread overview]
Message-ID: <CAKHgf3D=YdhBCz9fBAMwzA9Tvt026HUfuxiLv1tTZxn=igZh-A@mail.gmail.com> (raw)
In-Reply-To: <CAKHgf3AXx1F0oUU5UJZJOo9GfieEJTuHRx14oqwH+bsoiKtW7A@mail.gmail.com>

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

> OK, so that's one mystery down.  We are left with the HarfBuzz issue;
> please answer the questions I asked about that.

Ah, yes sorry -  I acquired the DLLs from the
mingw64/mingw-w64-x86_64-harfbuzz package.

$ objdump -x /mingw64/bin/libharfbuzz-0.dll | grep "DLL Name":
        DLL Name: libgcc_s_seh-1.dll
        DLL Name: GDI32.dll
        DLL Name: KERNEL32.dll
        DLL Name: msvcrt.dll
        DLL Name: RPCRT4.dll
        DLL Name: libstdc++-6.dll
        DLL Name: USER32.dll
        DLL Name: USP10.dll
        DLL Name: libfreetype-6.dll
        DLL Name: libglib-2.0-0.dll
        DLL Name: libgraphite2.dll
        DLL Name: libintl-8.dll

harfbuzz does load correctly now that the pdmp is being loaded correctly -
I believe because now it passes the `intialized` check and so actually
attempts to load them.

describe-char shows me: harfbuzz:-outline-Iosevka Fixed
SS02-regular-normal-normal-mono-14-*-*-*-c-*-iso8859-1 (#x56)

On Tue, Sep 10, 2024 at 2:47 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Casey Banner <kcbanner@gmail.com>
> > Date: Tue, 10 Sep 2024 14:31:07 -0400
> > Cc: 73159@debbugs.gnu.org
> >
> > > How come your LANG is set to en_US.UTF-8?  Did you set this in the
> > > environment or something.  Using UTF-8 as the default encoding on
> > > Windows is not a good idea.
> >
> > It seems that the msys2 .profile has `export LANG=$(locale -uU)`, and
> that returns en_US.UTF-8 for me.
>
> I don't recommend running Emacs from the MSYS2 Bash prompt.  Instead,
> run it from a desktop shortcut or pin it to the task bar and run from
> there.
>
> > > Please look at src/epaths.h and see how PATH_EXEC is defined there.
> >
> > It is indeed  #define PATH_EXEC
> "%emacs_dir%/libexec/emacs/30.0.50/x86_64-w64-mingw32"
> >
> > src/epaths.in has #define PATH_EXEC "/usr/local/libexec/emacs"
> >
> > I had been running configure and make in a subdirectory. If I run them
> in the top-level directory,
> > then it does update PATH_EXEC to the correct version. I think I made the
> wrong assumption that
> >  running configure in a subdirectory would leave the main source clean.
> >
> > Thank you for your help debugging this!
>
> OK, so that's one mystery down.  We are left with the HarfBuzz issue;
> please answer the questions I asked about that.
>

[-- Attachment #2: Type: text/html, Size: 3264 bytes --]

  parent reply	other threads:[~2024-09-10 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10  4:15 bug#73159: 30.0.90; uniscribe / harfbuzz are not initialized on Windows, resulting in fallback to gdi Casey Banner
2024-09-10  5:50 ` bug#73159: Casey Banner
2024-09-10  9:29   ` bug#73159: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 12:41     ` bug#73159: exec/configure.ac Eli Zaretskii
2024-09-10 13:08       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 12:33   ` bug#73159: 30.0.90; uniscribe / harfbuzz are not initialized on Windows, resulting in fallback to gdi Eli Zaretskii
2024-09-10 18:31     ` Casey Banner
2024-09-10 18:47       ` Eli Zaretskii
     [not found]         ` <CAKHgf3AXx1F0oUU5UJZJOo9GfieEJTuHRx14oqwH+bsoiKtW7A@mail.gmail.com>
2024-09-10 18:56           ` Casey Banner [this message]
2024-09-11  2:25             ` Eli Zaretskii
2024-09-10 12:20 ` 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

  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='CAKHgf3D=YdhBCz9fBAMwzA9Tvt026HUfuxiLv1tTZxn=igZh-A@mail.gmail.com' \
    --to=kcbanner@gmail.com \
    --cc=73159@debbugs.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).