From: Philipp Stephani <p.stephani2@gmail.com>
To: Jean-Christophe Helary <lists@traduction-libre.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: make docs
Date: Thu, 23 Dec 2021 13:57:04 +0100 [thread overview]
Message-ID: <CAArVCkR0YzOJKssuV6LLFfL4H1ce9E9UG0zupQ409qrcSNWDuw@mail.gmail.com> (raw)
In-Reply-To: <F3008E92-CF6F-4527-BF9A-142B97A55E9E@traduction-libre.org>
Am Do., 23. Dez. 2021 um 13:44 Uhr schrieb Jean-Christophe Helary
<lists@traduction-libre.org>:
>
>
>
> > On Dec 23, 2021, at 18:21, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >> From: Jean-Christophe Helary <lists@traduction-libre.org>
> >> Date: Thu, 23 Dec 2021 18:00:38 +0900
> >> Cc: Philipp Stephani <p.stephani2@gmail.com>,
> >> emacs-devel@gnu.org
> >>
> >>> You've removed the most interesting parts of the build transcript --
> >>> the ones that follow the Emacs build part -- which leaves me unable to
> >>> guess which parts of the doc directory need to build Emacs. Philipp's
> >>> guess that it's those manuals which are provided in *.org format is
> >>> still the winner in my book, btw.
> >>
> >>
> >> Et voilà monsieur :-)
> >
> > Thanks. This is clear now: the *.org files need to be converted to
> > *.texi, and that requires Emacs. So Philipp was right.
>
> Thank you. Which part of the log tells you that ? I'm just curious.
In the log there's a line
GEN org.texi
which indicates that org.texi is somehow generated.
The Makefile in docs/misc contains these rules:
define org_template
$(1:.org=.texi): $(1) ${top_srcdir}/lisp/org/ox-texinfo.el
$${AM_V_GEN}cd "$${srcdir}" && $${emacs} -l ox-texinfo \
-f org-texinfo-export-to-texinfo-batch $$(notdir $$<) $$(notdir $$@)
endef
$(foreach orgfile,${ORG_SRC},$(eval $(call org_template,$(orgfile))))
which means that Emacs is required to build these generated .texi
files from .org files.
next prev parent reply other threads:[~2021-12-23 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 4:43 make docs Jean-Christophe Helary
2021-12-22 13:29 ` Eli Zaretskii
2021-12-22 14:01 ` Jean-Christophe Helary
2021-12-22 15:45 ` Philipp Stephani
2021-12-22 16:43 ` Jean-Christophe Helary
2021-12-23 4:34 ` Jean-Christophe Helary
2021-12-23 7:15 ` Eli Zaretskii
2021-12-23 9:00 ` Jean-Christophe Helary
2021-12-23 9:21 ` Eli Zaretskii
2021-12-23 12:44 ` Jean-Christophe Helary
2021-12-23 12:57 ` Philipp Stephani [this message]
2021-12-23 13:04 ` Jean-Christophe Helary
2021-12-23 14:18 ` Eli Zaretskii
2021-12-23 15:08 ` Jean-Christophe Helary
2021-12-23 16:47 ` Glenn Morris
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=CAArVCkR0YzOJKssuV6LLFfL4H1ce9E9UG0zupQ409qrcSNWDuw@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lists@traduction-libre.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).