From: Corwin Brust <corwin@bru.st>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65188@debbugs.gnu.org, awrhygty@outlook.com
Subject: bug#65188: 29.1; WEBP image not displayed
Date: Thu, 10 Aug 2023 03:04:45 -0500 [thread overview]
Message-ID: <CAJf-WoQX0gTUh2h_tGR74Xh+0cGaFkbA8kssj2N4_31zoXxf_A@mail.gmail.com> (raw)
In-Reply-To: <83edkbjq6m.fsf@gnu.org>
On Thu, Aug 10, 2023 at 2:45 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Corwin Brust <corwin@bru.st>
> > Date: Thu, 10 Aug 2023 02:24:38 -0500
> > Cc: awrhygty@outlook.com, 65188@debbugs.gnu.org
> >
> > On Thu, Aug 10, 2023 at 1:34 AM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > Yes, AFAICT it is working as expected. I used ProcessExplorer
Hang on a minute...
I played with ProcessExplorer a little bit more, this time exporting
the list of DLLs for emacs-29.1.exe instead of the search/filter
approach looking specifically for libwebp-7. Here I can see two webp
related DLLs (but I'm fairly sure we only include one of them). The
one I didn't expect to find (libwebpdemux) is found from install of
MSYS, and seems to be about container parsing.
libwebpdemux-2.dll C:\msys2\mingw64\bin\libwebpdemux-2.dll
libwebp-7.dll H:\packaging-test\emacs-29.1_1\bin\libwebp-7.dll
Problem, yes? Packaging problem only?
I'm sorry, I wasn't aware I needed this. I'm happy to start on
updating the deps/deps-sources and making a new set of binaries "this
should have been included" is the correct surmise.
next prev parent reply other threads:[~2023-08-10 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 0:20 bug#65188: 29.1; WEBP image not displayed awrhygty
2023-08-10 6:34 ` Eli Zaretskii
2023-08-10 7:24 ` Corwin Brust
2023-08-10 7:45 ` Eli Zaretskii
2023-08-10 8:04 ` Corwin Brust [this message]
2023-08-10 9:16 ` Corwin Brust
2023-08-10 9:32 ` Eli Zaretskii
2023-08-10 11:40 ` Corwin Brust
2023-08-10 11:44 ` Corwin Brust
2023-08-10 13:39 ` awrhygty
2023-08-10 13:58 ` Eli Zaretskii
2023-08-10 9:25 ` 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=CAJf-WoQX0gTUh2h_tGR74Xh+0cGaFkbA8kssj2N4_31zoXxf_A@mail.gmail.com \
--to=corwin@bru.st \
--cc=65188@debbugs.gnu.org \
--cc=awrhygty@outlook.com \
--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 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).