From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix parallel build failure for Texinfo manual
Date: Tue, 21 Dec 2021 19:17:20 +0700 [thread overview]
Message-ID: <spsgki$vua$1@ciao.gmane.io> (raw)
In-Reply-To: <87r1a7rm6d.fsf@gmail.com>
On 21/12/2021 04:39, Marco Wahl wrote:
>
> Possibly a split of function org-make-manuals in org-make-manual and
> org-make-guide and further create two single targets instead of the
> current double target is more clear.
Marco, have you considered the following idea (I have not tested it)?
org.texi orgguide.texi:
$(BATCH) \
--eval '(add-to-list `load-path "../lisp")' \
--eval '(load "../mk/org-fixup.el")' \
--eval '(org-to-texi argv)' $<
org.texi: org-manual.org
orgguide.texi: org-guide.org
(defun org-to-texi (org-files)
"Generate the Texinfo files out of Org manuals."
(require 'ox-texinfo)
(dolist (manual org-files)
(find-file manual)
(org-texinfo-export-to-texinfo)))
P.S. Frankly speaking I was surprised that make runs command for every
target, I believed that is a way to specify multiple output files for
recipes. I had to look into info "(make) Multiple Targets" to realize
that I was wrong.
next prev parent reply other threads:[~2021-12-21 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 16:44 [PATCH] Fix parallel build failure for Texinfo manual Ulrich Müller
2021-12-20 21:39 ` Marco Wahl
2021-12-21 7:29 ` Ulrich Mueller
2021-12-21 11:21 ` Marco Wahl
2021-12-21 12:17 ` Max Nikulin [this message]
2021-12-21 12:48 ` Marco Wahl
2021-12-21 14:37 ` Max Nikulin
2021-12-21 20:34 ` Marco Wahl
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='spsgki$vua$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).