From: phillip.lord@russet.org.uk (Phillip Lord)
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: New windows builds
Date: Wed, 25 Oct 2017 22:51:46 +0100 [thread overview]
Message-ID: <87lgjyew0d.fsf@russet.org.uk> (raw)
In-Reply-To: <b4f502f0-abcc-4896-a392-3debdb8d85a7@default> (Drew Adams's message of "Wed, 25 Oct 2017 08:48:25 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
>> The new scripts automate both the build of the Emacs zip files
>> themselves and the "dependencies" binaries and source zip files. I've
>> added one new feature (already mentioned) which is the ability to build
>> a snapshot from an arbitrary branch.
>
> Thanks. Do I understand correctly that the result of this build
> is expected to be the same as the result of the previous build,
> and that the only difference is that you now use a different
> build procedure (e.g., different scripts)? IOW, should users
> expect any difference in the resulting builds?
There weren't any scripts before, I just ran through the instructions in
an .org file. Surprised it too me so long to get irritated with this.
But, as it's a new release, I have also change the packaging somewhat,
both from Emacs-25, and also from Emacs-26.0.90. The "default" one
(i.e. one with the shortest name) now contains all the dependencies;
that is, you don't have to unzip the deps file over the top of an
installation for yourself. The "-no-deps" version is the same as the
Emacs-25 releases.
The new files are described in
admin/nt/dist-build/README-windows-binaries.
Phil
prev parent reply other threads:[~2017-10-25 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 8:51 New windows builds Phillip Lord
2017-10-25 13:00 ` Aurélien Aptel
2017-10-25 15:49 ` Phillip Lord
2017-10-25 15:48 ` Drew Adams
2017-10-25 21:51 ` Phillip Lord [this message]
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=87lgjyew0d.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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 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.