Re: Native compilation on Windows, was Re: Bootstrap Compilation Speed

[H. Dieter Wilhelm]

Corwin Brust <corwin@bru.st> writes:

> On Sat, Jan 29, 2022 at 3:32 PM H. Dieter Wilhelm
> <dieter@duenenhof-wilhelm.de> wrote:
>>
>>
>>    libXpm-noX4.dll
>>
>> provides a nicer logo and icons.  (I didn't test much functionality
>> yet.)
>
> Thanks! I'll see if that could be a gap somewhere in the build
> process.  The windows release builds seem to have a pretty ugly logo
> on the splash.

Stange, the ugly logo didn't occurred to me with Emacs from your
installer?

(And Phil mentioned this dependency explicitly in
admin/nt/dist-build/README-scripts.)


>> In /nt/README.W32 is a list of further dependencies provided in MSYS2
>> packages:
>>
>>     mingw-w64-x86_64-giflib
>>     mingw-w64-x86_64-gnutls
>>     mingw-w64-x86_64-libjpeg-turbo
>>     mingw-w64-x86_64-libpng
>>     mingw-w64-x86_64-librsvg
>>     mingw-w64-x86_64-libtiff
>>     mingw-w64-x86_64-libxml2
>>     mingw-w64-x86_64-xpm-nox
>>     mingw-w64-x86_64-lcms2
>>
>
> Here is the list from build-deps-zips.  I'm fairly sure at least
> harfbuzz and jansson should be added, but I strongly suspect the list
> in the script is a good one (at least, I like the emacs release
> packages Phillip has been creating).
>
> mingw-w64-x86_64-giflib
> mingw-w64-x86_64-gnutls
> mingw-w64-x86_64-harfbuzz
> mingw-w64-x86_64-jansson
> mingw-w64-x86_64-lcms2
> mingw-w64-x86_64-libjpeg-turbo
> mingw-w64-x86_64-libpng
> mingw-w64-x86_64-librsvg
> mingw-w64-x86_64-libtiff
> mingw-w64-x86_64-libxml2
> mingw-w64-x86_64-xpm-nox
>
> Removing the intersection of these gives me:
>
> mingw-w64-x86_64-harfbuzz
> mingw-w64-x86_64-jansson

Thanks, do you know what jannson is needed for?

> However, when I look a little further down the script at the DLLs that
> we'll bundle, I note that xpm-nox is missing from the latter list, so
> that probably confirms the change needed per comments above.
>
> I will test that I confirm back.
>
>> are above dependencies considered as the absolut minimal set for a state
>> of the art Emacs under Windows?
>
> Do you want to patch the documentation while I further mangle Phillips 
> scripts?
>
> PS, not intending to side track the "simpler path" conversation you
> are having with Eli, here, but I do think we should carry what we
> learn back to the scripts that appear to do the job now.   In all
> events, I suspect jannsson and harbuzz should be documented in
> README.W32 in *some* fashion.

It would be good if you document your changes and when I'm ready I can
proofread them.

I don't see your files on
   https://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-28/

didn't the GNU administration respond to your request yet?

--
       Dieter