help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 64 bit official Windows builds


From: Sam Halliday
Subject: Re: 64 bit official Windows builds
Date: Sat, 9 Jan 2016 05:04:49 -0800 (PST)
User-agent: G2/1.0

Arash,

It sounds like you know how to do this a lot better than I do.

Is there any chance you could package this up so that everybody can get your 64 
bit builds of Emacs for Windows from the FSF site? If the sources are listed 
already, maybe you could just create a tarball containing all the sources of 
the compiler and required libraries? 

It would be really good from an automation point of view if you could write a 
little recipe (maybe an appveyor script?) that could be triggered when new 
versions of emacs (or the compiler) are released.

Best regards,
Sam

On Thursday, 7 January 2016 22:48:10 UTC, Arash Esbati  wrote:
> Eli Zaretskii <address@hidden> writes:
> 
> >> From: Óscar Fuentes <address@hidden>
> >> Date: Fri, 25 Dec 2015 14:35:46 +0100
> >> 
> >> IIRC the problematic part is to create and distribute a source tarball
> >> with all the libraries included on the binary package (graphic
> >> libraries, SSL, etc). This was discussed on the past and can't recall
> >> the outcome.
> >
> > It's up to the person who volunteers for the job.  It's quite okay to
> > upload only the Emacs binary that was compiled with support for the
> > optional libraries, and expect the end users to download and itsall
> > the DLLs separately.  It is also okay to upload the DLLs as part of
> > the binary distro, but then the corresponding sources should be on the
> > same site.
> 
> I think that providing bare Emacs binaries without the corresponding
> dll's is not really user friendly.  I build Emacs on my Win 64bit
> machine with Msys2/MinGW-w64 and it would be pain if I had to collect all
> dll's myself somehow.  OTOH, collecting and providing all the sources
> along with the dll's is also not fun.  Can there be a compromise?  For
> Msys2/MinGW-w64, all PKGBUILD files contain references the sources, e.g.:
> 
>     
> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-libidn/PKGBUILD
> 
> So one could say: Consult the PKGBUILD files for the sources
> (incl. dependencies) for
> 
> - mingw-w64-libtiff
> - mingw-w64-giflib
> - mingw-w64-libpng
> - mingw-w64-libjpeg-turbo
> - mingw-w64-librsvg
> - mingw-w64-libxml2
> - mingw-w64-gnutls
> - mingw-w64-xpm-nox
> 
> Best, Arash



reply via email to

[Prev in Thread] Current Thread [Next in Thread]