From: phillip.lord@russet.org.uk (Phillip Lord)
To: Drew Adams <drew.adams@oracle.com>
Cc: jostein@secure.kjonigsen.net, Eli Zaretskii <eliz@gnu.org>,
jostein@kjonigsen.net, emacs-devel@gnu.org
Subject: Re: windows installer
Date: Thu, 16 Nov 2017 16:15:03 +0000 [thread overview]
Message-ID: <87375eqjy0.fsf@russet.org.uk> (raw)
In-Reply-To: <ae87257b-1532-42e0-b040-8156c94b98f2@default> (Drew Adams's message of "Tue, 14 Nov 2017 06:54:44 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
>> > Such binaries used to be delivered more often. If there
>> > were a simple "push-button" command to create them locally,
>> > which didn't require anything else, I might well take
>> > advantage of that too.
>>
>> It's not going to get any simpler than "./configure;make install"
>> complete with all the environment that this entails.
>
> Does that work on out-of-the-box MS Windows? I doubt it.
>
> Emacs users on Windows are not necessarily developers
> of/on Windows. A "builder" that contained everything
> it needed, and kept it contained, tossing afterward
> whatever is not needed to run the built Emacs, would
> be what I'm talking about.
Yeah, that's not going to happen. Essentially, the build proceedure at
the moment is this:
Install msys
Run pacman to install dependencies
git clone emacs
./configure;make
The last step takes an hour.
Alternatively, installer a snapshot via an installer. I'm struggling to
see a substantial user community who would want something in between the
two.
> Other binaries (e.g. Msys stuff) are less the problem
> that a C compiler, `make', etc. Push-button building
> without depending on a separate development environment.
> I.e., the builder would bring its own build tools, and
> clean them out when done building.
>
>> > But is it not the case that this "installer"
>> > also _builds_ Emacs for Windows? If not then apologies
>> > for misunderstanding.
>>
>> No. The builder builds the installer. It's a self-extracting
>> zip file on steroids.
>
> IIUC, none of those steroids help me, IIUC. I don't care
> to "install" this or that Emacs build. I just want to get
> builds or be able to push-button-create them. I don't want
> something messing with my Windows registry, menus, HOME,
> PATH, or anything else. Get the build job done without
> depending on anything else pre-existing, and leave no
> footprints behind.
The "leave no footprints" behind means "start-from-scratch". Currently,
building the Emacs zip (including extracting the dependencies) takes
about 3 hours and requires half a gig of downloads.
>> I think we are good here. I put support for snapshot building in, and
>> I've automated as much of the stuff around that as I can. So, I
>> should be able to do it more frequently; probably monthly, as I
>> haven't managed to automate things from start to finish.
>
> Great. It will be good to return to periodically uploaded builds.
Up sometime soon!
Phil
next prev parent reply other threads:[~2017-11-16 16:15 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 23:11 windows installer Phillip Lord
2017-10-28 21:47 ` Richard Stallman
2017-11-06 8:11 ` Jostein Kjønigsen
[not found] ` <87h8u6bae3.fsf@russet.org.uk>
[not found] ` <WM!524810e63610127669556b68fb62cde560daf19be50fc52d4d63dd232af7bdb0490810e03b84a6559c9b2017d8462cc3!@mailhub-mx4.ncl.ac.uk>
2017-11-08 7:31 ` Jostein Kjønigsen
2017-11-10 17:01 ` Phillip Lord
2017-11-10 18:52 ` Eli Zaretskii
2017-11-10 20:46 ` Stefan Monnier
2017-11-10 21:22 ` John Mastro
2017-11-10 21:35 ` Fabrice Popineau
2017-11-11 7:33 ` Eli Zaretskii
2017-11-11 11:34 ` Phillip Lord
2017-11-11 14:57 ` Stefan Monnier
2017-11-12 11:21 ` Jostein Kjønigsen
2017-11-10 21:33 ` Fabrice Popineau
2017-11-11 7:35 ` Eli Zaretskii
2017-11-10 23:27 ` Phillip Lord
2017-11-11 0:25 ` Fabrice Popineau
2017-11-11 11:25 ` Phillip Lord
2017-11-12 0:30 ` Fabrice Popineau
2017-11-12 4:30 ` Eli Zaretskii
[not found] ` <87fu9hbytq.fsf@russet.org.uk>
2017-11-13 22:25 ` Phillip Lord
2017-11-14 13:08 ` Fabrice Popineau
2017-11-16 16:15 ` Phillip Lord
2017-11-11 7:48 ` Eli Zaretskii
2017-11-11 11:24 ` Phillip Lord
2017-11-11 12:01 ` Eli Zaretskii
[not found] ` <<83ineiotjr.fsf@gnu.org>
2017-11-10 21:43 ` Drew Adams
2017-11-10 23:35 ` Phillip Lord
2017-11-11 7:49 ` Eli Zaretskii
2017-11-11 7:40 ` Eli Zaretskii
2017-11-11 9:42 ` Yuri Khan
2017-11-11 10:37 ` Eli Zaretskii
2017-11-11 16:39 ` Drew Adams
[not found] ` <87a7zpbxza.fsf@russet.org.uk>
2017-11-13 22:44 ` Phillip Lord
2017-11-14 14:54 ` Drew Adams
2017-11-16 16:15 ` Phillip Lord [this message]
2017-11-16 16:23 ` Eli Zaretskii
2017-11-16 16:31 ` Fabrice Popineau
2017-11-16 16:57 ` Eli Zaretskii
2017-11-16 17:35 ` Fabrice Popineau
2017-11-16 17:39 ` Eli Zaretskii
2017-11-16 18:10 ` Fabrice Popineau
2017-11-16 20:45 ` Richard Copley
2017-11-17 7:14 ` Eli Zaretskii
2017-11-17 7:22 ` Fabrice Popineau
2017-11-17 7:35 ` Eli Zaretskii
2017-11-17 7:25 ` Fabrice Popineau
2017-11-16 17:42 ` Noam Postavsky
2017-11-16 17:45 ` Fabrice Popineau
2017-11-22 22:39 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2017-11-12 8:56 Angelo Graziosi
2017-11-12 9:03 ` Fabrice Popineau
2017-11-12 11:30 ` Eli Zaretskii
2017-11-12 12:39 ` Fabrice Popineau
[not found] ` <8760adbxw6.fsf@russet.org.uk>
2017-11-13 22:46 ` Phillip Lord
2017-11-14 14:36 ` Angelo Graziosi
2017-11-14 16:31 ` Fabrice Popineau
2017-11-14 20:12 ` Angelo Graziosi
2017-11-20 8:46 ` Jostein Kjønigsen
2017-11-20 18:07 ` Eli Zaretskii
2017-11-22 23:01 ` Phillip Lord
2017-11-23 3:43 ` Eli Zaretskii
2017-11-23 18:06 ` Phillip Lord
2017-11-23 20:09 ` Eli Zaretskii
2017-11-24 19:13 ` Phillip Lord
2017-11-24 19:56 ` Eli Zaretskii
2017-11-25 11:08 ` Phillip Lord
2017-11-25 12:56 ` Eli Zaretskii
2017-11-27 17:56 ` Phillip Lord
2017-11-12 14:14 ` Angelo Graziosi
2017-11-12 11:28 ` Eli Zaretskii
2017-11-12 14:27 ` Angelo Graziosi
2017-11-12 15:04 ` Eli Zaretskii
2017-11-12 17:32 ` Angelo Graziosi
2017-11-12 18:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87375eqjy0.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jostein@kjonigsen.net \
--cc=jostein@secure.kjonigsen.net \
/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.