Hi Nicolas, I'm cc'ing Achim as I seem to remember he offered to help writing needed rules for the switch to org-manual.org to be complete.
> 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. Achim, what do you think? If we can drop the org-version.inc, that's even better. > BTW, I wonder why the build system needs to create an "org" file, > without extension, equivalent to "org.info". I guess that's a leftover from old times, when the .info extension on info files was not systematic. -- Bastien
