Hello, Bastien <b...@gnu.org> writes:
> it would be nice to make the switch to org-manual.org for Org 9.2, > and to delete org.texi entirely from the master branch. We already switched to "org-manual.org" in the sense that current "org.texi" is generated from "org-manual.org". > I guess we need to add some Makefile rules so that "make pdf" first > exports .org => .texi then exports .texi to .pdf... is that so? I guess we could extend the "info" rule to generate the ".texi" file out of "org-manual.org" first. For example, in "doc/Makefile", we could either add a pre-requisite to the following rule: info: org e.g., info: org.texi org org.texi: org-manual.org $(BATCH) \ --eval '(add-to-list '"'"'load-path "../lisp")' \ --eval '(load "org-compat.el")' \ --eval '(load "../mk/org-fixup.el")' \ --eval '(org-generate-texinfo-manual "$<" "@$")' $(MAKEINFO) --no-split $< -o $@ assuming `org-generate-texinfo-manual' is defined in "org-fixup.el". However, the above may require to mess with the match-all rule .SUFFIXES: .texi .tex .txt _letter.tex %: %.texi org-version.inc $(MAKEINFO) --no-split $< -o $@ In particular, we might drop the "org-version.inc" file. But the build system is tricky, I admit I do not understand it totally. BTW, I wonder why the build system needs to create an "org" file, without extension, equivalent to "org.info". Regards, -- Nicolas Goaziou