Re: emacs-26 3fc05cf: Scripts to automate windows binary distribution

[phillip.lord@russet.org.uk (Phillip Lord)]

Noam Postavsky <npostavs@users.sourceforge.net> writes:

> On Wed, Oct 25, 2017 at 4:37 AM, Phillip Lord
> <phillip.lord@russet.org.uk> wrote:
>
>> I started off writing this in bash, but it's such a pain that I ported
>> it to python which ended up much nicer. Given that this file has about a
>> 15-20 minute run time, this seemed a useful thing to me. As it happens
>> it was also easy to make it go quicker which is important because it
>> means that I can do the build in the evening, rather than over two
>> evenings.
>
> Hmm, looking at the python, I don't see anything that couldn't be
> easily done in bash, and if it was me, I would probably use bash for
> this; but if you prefer python I don't see a problem with that.

Oh, it was just the parallellisation step for the source download. It
wasn't a big deal one way or the other, and I am entirely happy to
accept that my ignorance about bash scripting is a major factor.

>> I'll probably port build-zips.sh at some point as well.
>
> Python seems even less advantageous there, since it's mostly calling
> external commands, no?

Yes, that's why I didn't port it.

> PS: With regards to making things run quicker, you might want to
> consider passing --cache-file=../../config.cache.$ARCH to configure.
> It would probably save a minute or two per build.

Good idea; for the pre-test and release builds, I do them clean anyway,
but for snapshots (assuming I start doing these), it would be a
significant win.

Phil