unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: replacing ldefs-boot.el
Date: Fri, 25 Nov 2016 11:23:25 +0000	[thread overview]
Message-ID: <8737ifu7ki.fsf@russet.org.uk> (raw)
In-Reply-To: <87a8csij8c.fsf@russet.org.uk> (Phillip Lord's message of "Mon, 21 Nov 2016 22:03:15 +0000")

phillip.lord@russet.org.uk (Phillip Lord) writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: phillip.lord@russet.org.uk (Phillip Lord)
>>> Cc: emacs-devel@gnu.org
>>> Date: Sun, 20 Nov 2016 21:28:49 +0000
>>> 
>>> This is a reasonable significant change in the bootstrap build, and
>>> there may be implications that I have not foreseen. Hence it makes sense
>>> to ask first.
>>
>> Then please describe the bootstrap and the normal build in detail,
>> because I'm not sure I understood the implications by just looking at
>> the diffs.
>
> Currently, emacs builds like so (in f make syntax)-- 
>
> temacs: *.c
>
> bootstrap-emacs: temacs
>       ## temacs loads ldefs-boot.el during loadup or it crashes
>
> compile-first: bootstrap-emacs
>
> loaddefs.el: compile-first
>      ## now we generate loaddefs.el
>
>
> Afterwards, we do:
>
> temacs: *.c
>
> bootstrap-emacs: temacs
>       ## temacs loads ldefs-boot-manual.el and -auto.el during
>       ## loadup or it crashes
>
> loaddefs.el: bootstrap-emacs
>      ## now we generate loaddefs.el
>
> compile-first: loaddefs.el
>
>
> So, loaddefs.el is available before compile-first happens.
>
>
>> What are those additional files, and how and when they are
>> generated?
>
> ldefs-boot-auto.el is now autogenerated from a make target at top level.
> It works but augmenting eval.c, so that when an autoload happens, Emacs
> writes to system stdout the equivalent autoload form. A complete
> bootstrap build will, therefore, print all the autoloads that are
> actually used. There's some lisp in admin/ldefs-clean.el which removes
> everything except these lisp forms.
>
> Advantages:
>
>  - we still have an autogenerated file in the repo, but it is very much
>    smaller (160 lines vs 40k).
>
> Disadvantages:
>
>  - generating ldefs-boot-auto is a lot slower (i.e. cp loaddefs.el
>    ldefs-boot.el vs a complete bootstrap build of Emacs).
>
> Invariants:
>
>  - to my testing there is negligable difference in build time.


Have you had a chance to look at this yet?

Phil



  reply	other threads:[~2016-11-25 11:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-20 17:46 replacing ldefs-boot.el Phillip Lord
2016-11-20 19:23 ` Eli Zaretskii
2016-11-20 21:28   ` Phillip Lord
2016-11-21  3:27     ` Eli Zaretskii
2016-11-21 22:03       ` Phillip Lord
2016-11-25 11:23         ` Phillip Lord [this message]
2016-11-25 13:28           ` Eli Zaretskii
2016-11-25 18:10             ` Paul Eggert
2016-11-25 19:31               ` Eli Zaretskii
2016-11-25 20:11                 ` Stefan Monnier
2016-11-26  6:46                   ` Eli Zaretskii
2016-11-26 12:08                     ` Phillip Lord
2016-11-25 21:34                 ` Phillip Lord
2016-11-25 23:18                   ` Óscar Fuentes
2016-11-26 20:59                     ` Phillip Lord
2016-11-27 20:14               ` Nicolas Petton
2016-11-25 21:11         ` Noam Postavsky
2016-11-25 21:57           ` Phillip Lord
2016-11-26  5:34             ` Noam Postavsky
2016-11-26 12:19               ` Phillip Lord
2016-11-27 23:04                 ` Noam Postavsky
2016-11-29 14:57                   ` Phillip Lord
2016-11-27 21:19         ` Phillip Lord
2016-12-13 12:17 ` Phillip Lord
2016-12-13 14:02   ` Noam Postavsky
2016-12-14 11:53     ` Phillip Lord
2016-12-13 14:58   ` John Wiegley
2016-12-13 16:08   ` Eli Zaretskii
2016-12-14 12:00     ` Phillip Lord

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=8737ifu7ki.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eliz@gnu.org \
    --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).