Re: Extending makefile to pdf and html output
Heime <[email protected]> Sat, 25 Apr 2026 13:24:39 +0000
| Newsgroups | gmane.comp.tex.texinfo.general |
|---|---|
| Message-ID | <KKn8dgprxL25WagFE3oClkyFXXTLg4mCp45O880JzCMtkiV6vWraTgQpK2PoTX4CU6zxAgeUp1CvLNlp1zCTFPKOsU0fYdJI9ennqfre99Q=@protonmail.com> |
Sent with Proton Mail secure email. On Sunday, April 26th, 2026 at 1:13 AM, Eli Zaretskii <[email protected]> wrote: > > Date: Sat, 25 Apr 2026 13:03:25 +0000 > > From: Heime <[email protected]> > > Cc: [email protected] > > > > On Saturday, April 25th, 2026 at 7:40 PM, Eli Zaretskii <[email protected]> = wrote: > > > > > > Date: Sat, 25 Apr 2026 00:09:07 +0000 > > > > From: Heime <[email protected]> > > > > > > > > I want to add the production of pdf and html. How would one > > > > change this makefile? > > > > > > You can see how this is done forEmacs by looking into the > > > subdirectories of the doc/ directory in the Emacs source tree. For > > > example, in doc/emacs/. > > > > I can see that you specify all the .texi source files. I am using > > rule where I do not specify the files. What is the reason for doing > > so, and I do the same? > > > > $(trgdir)/%.info: $(srcdir)/%.texi >=20 > This is okay if your manual has a single source file. The Emacs > manual is a single Info file built from many source files, so the > above rule would not work. My program manual will be split in a number of files - would I=20 have to do the same? The emacs single source file you mention, are the many source files you mention separate info manuals. Or is it a single manual with chapters or sections split in multiple files (as I will do)?=20 =20 > > Also noticed you use texi2pdf. makeinfo should be the same as > > texi2any, why is texi2pdf preferred? I was going to use makeinfo > > to do everything. >=20 > Yes, you can use makeinfo for everything. Have tried your earlier suggestion for emacs and in the scratch buffer I run=20 (info (emacs))=20 which entered a Lisp error: (void-function emacs) =20