Roland Ver. 4.5 Información técnica descargar pdf (Pagina 171)

Chapter 15: Makeﬁle Conventions 161

generated. These targets should not be dependencies of the all target; the

user must manually invoke them.

Here’s an example rule for generating DVI ﬁles from Texinfo:

dvi: foo.dvi

foo.dvi: foo.texi chap1.texi chap2.texi

$(TEXI2DVI) $(srcdir)/foo.texi

You must deﬁne the variable TEXI2DVI in the Makeﬁle. It should run the

program texi2dvi, which is part of the Texinfo distribution. (texi2dvi uses

X to do the real work of formatting. T

X is not distributed with Texinfo.)

Alternatively, write only the dependencies, and allow GNU make to provide the

command.

Here’s another example, this one for generating HTML from Texinfo:

html: foo.html

foo.html: foo.texi chap1.texi chap2.texi

$(TEXI2HTML) $(srcdir)/foo.texi

Again, you would deﬁne the variable TEXI2HTML in the Makeﬁle; for example,

it might run makeinfo --no-split --html (makeinfo is part of the Texinfo

distribution).

‘dist’ Create a distribution tar ﬁle for this program. The tar ﬁle should be set up so

that the ﬁle names in the tar ﬁle start with a subdirectory name which is the

name of the package it is a distribution for. This name can include the version

number.

For example, the distribution tar ﬁle of GCC version 1.40 unpacks into a sub-

directory named gcc-1.40.

The easiest way to do this is to create a subdirectory appropriately named, use

ln or cp to install the proper ﬁles in it, and then tar that subdirectory.

Compress the tar ﬁle with gzip. For example, the actual distribution ﬁle for

GCC version 1.40 is called gcc-1.40.tar.gz. It is ok to support other free

compression formats as well.

The dist target should explicitly depend on all non-source ﬁles that are in the

distribution, to make sure they are up to date in the distribution. See Section

“Making Releases” in GNU Coding Standards.

‘check’ Perform self-tests (if any). The user must build the program before running

the tests, but need not install the program; you should write the self-tests so

that they work when the program is built but not installed.

The following targets are suggested as conventional names, for programs in which they

are useful.

installcheck

Perform installation tests (if any). The user must build and install the program

before running the tests. You should not assume that $(bindir) is in the

search path.

1 2 ... 166 167 168 169 170 171 172 173 174 175 176 ... 211 212

Comentarios a estos manuales

Sin comentarios

Roland Ver. 4.5 Información técnica Pagina 171

Comentarios a estos manuales

Relacionado con productos y manuales para Impresión y escaneo Roland Ver. 4.5