unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Reworking loaddefs.el generation
Date: Wed, 01 Jun 2022 07:43:21 +0200	[thread overview]
Message-ID: <87a6ax2b2e.fsf@gnus.org> (raw)
In-Reply-To: <87ilpl2g2c.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 01 Jun 2022 05:55:23 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> So we'd need to rearrange those to be compiled first, and then
> have that target depend on that new target?  Perhaps put them in
> MAIN_FIRST in lisp/Makefile, and...  er...  something.

Perhaps something along the lines of:

diff --git a/doc/misc/Makefile.in b/doc/misc/Makefile.in
index d9c5173c07..a0788580b7 100644
--- a/doc/misc/Makefile.in
+++ b/doc/misc/Makefile.in
@@ -71,8 +71,8 @@ INFO_COMMON =
 	dbus dired-x ebrowse ede ediff edt eieio \
 	emacs-mime epa erc ert eshell eudc efaq eww \
 	flymake forms gnus emacs-gnutls htmlfontify idlwave ido info.info \
-	mairix-el message mh-e modus-themes newsticker nxml-mode octave-mode \
-	org pcl-cvs pgg rcirc remember reftex sasl \
+	mairix-el message mh-e newsticker nxml-mode octave-mode \
+	pcl-cvs pgg rcirc remember reftex sasl \
 	sc semantic ses sieve smtpmail speedbar srecode todo-mode transient \
 	tramp url vhdl-mode vip viper vtable widget wisent woman
 
@@ -82,7 +82,7 @@ INFO_INSTALL =
 ## Info files to build on current platform.
 ## This is all of them, even though they might not all get installed,
 ## because the info files are pre-built in release tarfiles.
-INFO_TARGETS = $(INFO_COMMON) efaq-w32
+INFO_TARGETS = $(INFO_COMMON) efaq-w32 org modus-themes
 
 ## Some manuals have their source in .org format.
 ## This is discouraged because the .texi files it generates
diff --git a/lisp/Makefile.in b/lisp/Makefile.in
index 5f9ca01694..4e3219bcef 100644
--- a/lisp/Makefile.in
+++ b/lisp/Makefile.in
@@ -98,7 +98,9 @@ COMPILE_FIRST +=
 # to speed things up.
 MAIN_FIRST = ./emacs-lisp/eieio.el ./emacs-lisp/eieio-base.el \
   ./cedet/semantic/db.el ./emacs-lisp/cconv.el \
-  ./international/ja-dic-cnv.el
+  ./international/ja-dic-cnv.el \
+  ./org/ox.el ./org/ox-texinfo.el ./org/org-macro.el ./org/org-element.el \
+  ./org/oc.el ./org/ol.el ./emacs-lisp/cl-lib.el
 
 # Prevent any settings in the user environment causing problems.
 unexport EMACSDATA EMACSDOC EMACSLOADPATH EMACSPATH
@@ -121,11 +123,12 @@ SUBDIRS_SUBDIRS =
 
 # cus-load and finder-inf are not explicitly requested by anything, so
 # we add them here to make sure they get built.
-all: compile-main $(lisp)/cus-load.el $(lisp)/finder-inf.el generate-ja-dic
+all: compile-main $(lisp)/cus-load.el $(lisp)/finder-inf.el generate-ja-dic \
+	org-manuals
 
 PHONY_EXTRAS =
 .PHONY: all custom-deps finder-data autoloads update-subdirs $(PHONY_EXTRAS) \
-	generate-ja-dic
+	generate-ja-dic org-manuals
 
 # custom-deps and finder-data both used to scan _all_ the *.el files.
 # This could lead to problems in parallel builds if automatically
@@ -161,6 +164,9 @@ generate-ja-dic:
 	$(AM_V_at)$(MAKE) -C ../leim generate-ja-dic EMACS="$(EMACS)"
 	$(AM_V_at)$(MAKE) compile-targets TARGETS="./leim/ja-dic/ja-dic.elc"
 
+org-manuals: main-first
+	$(MAKE) -C ../doc/misc org.texi modus-themes.texi
+
 ## Comments on loaddefs generation:
 
 # loaddefs depends on gen-lisp for two reasons:


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2022-06-01  5:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 10:53 Reworking loaddefs.el generation Lars Ingebrigtsen
2022-05-27 12:03 ` Andreas Schwab
2022-05-27 12:17   ` Lars Ingebrigtsen
2022-05-27 12:43 ` Stefan Monnier
2022-05-27 13:00   ` Lars Ingebrigtsen
2022-05-31 16:10 ` Lars Ingebrigtsen
2022-05-31 16:33   ` Lars Ingebrigtsen
2022-05-31 16:53     ` Lars Ingebrigtsen
2022-05-31 17:32       ` Eli Zaretskii
2022-05-31 17:40         ` Lars Ingebrigtsen
2022-05-31 18:09       ` Lars Ingebrigtsen
2022-05-31 19:24         ` Eli Zaretskii
2022-05-31 19:33           ` Lars Ingebrigtsen
2022-06-01  2:26             ` Eli Zaretskii
2022-06-01  2:29               ` Lars Ingebrigtsen
2022-06-01 11:40                 ` Eli Zaretskii
2022-06-01 12:13                   ` Lars Ingebrigtsen
2022-06-01 19:02                     ` Eli Zaretskii
2022-06-02  9:14                       ` Lars Ingebrigtsen
2022-05-31 18:44 ` Alan Mackenzie
2022-05-31 18:47   ` Lars Ingebrigtsen
2022-06-01  3:55     ` Lars Ingebrigtsen
2022-06-01  5:43       ` Lars Ingebrigtsen [this message]
2022-06-01 11:16         ` Lars Ingebrigtsen
2022-06-01 11:26           ` Lars Ingebrigtsen
2022-06-01 12:00           ` Andreas Schwab
2022-06-01 12:10             ` Lars Ingebrigtsen
2022-06-01 14:23             ` Lars Ingebrigtsen
2022-06-01 11:47       ` Stefan Monnier
2022-06-01 12:09         ` Lars Ingebrigtsen
2022-05-31 19:04   ` Stefan Monnier
2022-06-01  5:13     ` Lars Ingebrigtsen
2022-06-01 11:07       ` Eli Zaretskii
2022-06-01 12:29         ` Lars Ingebrigtsen
2022-05-31 19:00 ` Lars Ingebrigtsen
2022-05-31 19:12   ` Lars Ingebrigtsen

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=87a6ax2b2e.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=acm@muc.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).