From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Compilation speed
Date: Wed, 19 Aug 2020 11:43:05 +0200 [thread overview]
Message-ID: <20200819094305.GB31976@tuxteam.de> (raw)
In-Reply-To: <87d03n7zse.fsf@tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On Wed, Aug 19, 2020 at 11:25:37AM +0200, Mario Lang wrote:
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
> > On 8/6/20 8:20 AM, Lars Ingebrigtsen wrote:
> >
> >> And then ./configure takes 19 seconds, and that's fully single-threaded,
> >> I believe? And... I'm guessing there's no way to get that to be
> >> multi-threaded?
[...]
> The "speed" of autoconf is probably the reason why its adoption rate is
> falling. I remember insisting on using autoconf for many years, just
> because. Until I figured out CMake 3.x. I will never write an autoconf
> script again, never.
I used to consider CMake as "just another build system, why not". Until
I saw its cross-compilation story. Since then, I appreciate autoconf
even more.
Speed (more precisely: parallelizability) isn't that important to me.
Usually I've got other nice things to do while Emacs compiles (i.e.
I schedule such jobs) -- although I do understand that other peoples's
workflows are different.
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-08-19 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 15:20 Compilation speed Lars Ingebrigtsen
2020-08-06 19:07 ` Paul Eggert
2020-08-19 9:25 ` Mario Lang
2020-08-19 9:43 ` tomas [this message]
2020-08-19 12:37 ` Ergus
2020-08-06 22:14 ` Stefan Monnier
2020-08-07 6:55 ` Lars Ingebrigtsen
2020-08-07 16:26 ` Andrea Corallo via Emacs development discussions.
2020-08-10 14:33 ` Arthur Miller
2020-08-12 2:11 ` Paul Eggert
2020-08-12 12:53 ` Arthur Miller
2020-08-12 16:08 ` Stefan Monnier
2020-08-12 16:59 ` Paul Eggert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200819094305.GB31976@tuxteam.de \
--to=tomas@tuxteam.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).