public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-4994] modula-2, doc: Build dvi, ps and pdf doc in the gcc/doc directory. Date: Wed, 4 Jan 2023 14:52:18 +0000 (GMT) [thread overview] Message-ID: <20230104145218.534603858D39@sourceware.org> (raw) https://gcc.gnu.org/g:e15e8d430c5f6a85334f67fd552850e8aa27a7cf commit r13-4994-ge15e8d430c5f6a85334f67fd552850e8aa27a7cf Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sat Dec 31 13:22:56 2022 +0000 modula-2, doc: Build dvi, ps and pdf doc in the gcc/doc directory. This also uses the configured $(TEXI2DVI) and $(TEXI2PDF) to deal with those targets (since we cannot assume to know what the use might have installed). gcc/m2/ChangeLog: * Make-lang.in (dvi, ps, pdf): Build in the gcc/doc directory, also use the configured tools for texi -> dvi and texi -> pdf. Diff: --- gcc/m2/Make-lang.in | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/gcc/m2/Make-lang.in b/gcc/m2/Make-lang.in index 3050f5a581c..b7dec120078 100644 --- a/gcc/m2/Make-lang.in +++ b/gcc/m2/Make-lang.in @@ -141,18 +141,22 @@ $(DESTDIR)$(man1dir)/$(GM2_INSTALL_NAME)$(man1ext): doc/m2.1 installdirs -$(INSTALL_DATA) $< $@ -chmod a-x $@ -m2.dvi: $(TEXISRC) - $(TEXI2DVI) -I $(objdir)/m2 -I $(srcdir)/doc/include $(srcdir)/doc/gm2.texi -o $@ +m2.dvi: doc/m2.dvi -m2.ps: m2.dvi +doc/m2.dvi: $(TEXISRC) + $(TEXI2DVI) -c -I $(objdir)/m2 -I $(srcdir)/doc/include -o $@ $(srcdir)/doc/gm2.texi + +doc/m2.ps: doc/m2.dvi dvips -o $@ $< -m2.pdf: m2.ps - gs -q -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=$@ $< +m2.pdf: doc/m2.pdf + +doc/m2.pdf: $(TEXISRC) + $(TEXI2PDF) -I $(objdir)/m2 -I $(srcdir)/doc/include $(srcdir)/doc/gm2.texi -o $@ .INTERMEDIATE: m2.pod -m2.pod: doc/gm2.texi $(TEXISRC) +m2.pod: $(TEXISRC) -$(TEXI2POD) -I $(objdir)/m2 -D m2 < $< > $@ doc/m2.info: $(TEXISRC)
reply other threads:[~2023-01-04 14:52 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230104145218.534603858D39@sourceware.org \ --to=iains@gcc.gnu.org \ --cc=gcc-cvs@gcc.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).