From owner-freebsd-current Tue Apr 25 11:55:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA07839 for current-outgoing; Tue, 25 Apr 1995 11:55:31 -0700 Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA07832 ; Tue, 25 Apr 1995 11:55:29 -0700 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.11/8.6.9) id LAA02726; Tue, 25 Apr 1995 11:53:59 -0700 From: Steven G Kargl Message-Id: <199504251853.LAA02726@troutmask.apl.washington.edu> Subject: Re: TeX support in bsd.doc.mk? To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 25 Apr 1995 11:53:59 -0700 (PDT) Cc: jkh@freefall.cdrom.com, nate@trout.sri.mt.net, current@freefall.cdrom.com In-Reply-To: <199504251708.KAA10222@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 25, 95 10:08:03 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1760 Sender: current-owner@FreeBSD.org Precedence: bulk According to Rodney W. Grimes: > > > > > > Jordan K. Hubbard writes: > > > > How do people feel about adding in some standard handy rules for this? > > > > > > I'm not sure I follow? What kind of rules? > > > > TEXDOC= foo > > > > .include > > > > % make > > tex foo.tex ... > > ... > > End up with foo.ps in obj. > > I only have one thing I would like to say about this, don't modify > bsd.doc.mk to do this (that file has to get parsed for every make > in the source we do, and this just adds stuff to it to parse that > we well not use in /usr/src) add bsd.tex.mk to do this. > I agree with Rodney about bsd.tex.mk. However, I was wondering if it can be made smart enough to distinguish between TeX (as in Knuth), LaTex2e, TeXinfo, ... Also, you need to consider the possibility of cross references in a TeX file. This normally means that tex (or latex) is run more than once to get things straight;i.e., %latex foo <--- produce *.log, *.aux, *.toc ... %latex foo <--- resolve cross references (e.g., Table of Contents) [%latex foo <--- again, resolve more cross references?] %dvips -o foo.ps foo If you incorporate a dvips step, are we assuming 300dpi on a Canon CX laser printer engine? This could probably be set in make.conf; i.e., DPI=300 or ENGINE=CX. Dvips needs to have the *.mf files for font creationr available, and a single place to build/store the *.300pk files? If the tex,dvips,xdvi packages are previously installed, then dvips should Do the Right Thing, but it's not guaranteed. -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.1-current | Seattle, WA 98105 |---------------------|