Movatterモバイル変換

5.3.8.3 The Front EndMake-lang.in File ¶

Each language subdirectory contains aMake-lang.in file. It containstargetslang.hook (wherelang is thesetting oflanguage inconfig-lang.in) for the followingvalues ofhook, and any other Makefile rules required tobuild those targets (which may if necessary use other Makefilesspecified inoutputs inconfig-lang.in, although this isdeprecated). It also adds any testsuite targets that can use thestandard rule ingcc/Makefile.in to the variablelang_checks.

all.cross

start.encap

rest.encap

FIXME: exactly what goes in each of these targets?

tags

Build anetagsTAGS file in the language subdirectoryin the source tree.

info

Build info documentation for the front end, in the build directory.This target is only called by ‘make bootstrap’ if a suitableversion ofmakeinfo is available, so does not need to checkfor this, and should fail if an error occurs.

dvi

Build DVI documentation for the front end, in the build directory.This should be done using$(TEXI2DVI), with appropriate-I arguments pointing to directories of included files.

pdf

Build PDF documentation for the front end, in the build directory.This should be done using$(TEXI2PDF), with appropriate-I arguments pointing to directories of included files.

html

Build HTML documentation for the front end, in the build directory.

man

Build generated man pages for the front end from Texinfo manuals(seeMan Page Generation), in the build directory. This targetis only called if the necessary tools are available, but should ignoreerrors so as not to stop the build if errors occur; man pages areoptional and the tools involved may be installed in a broken way.

install-common

Install everything that is part of the front end, apart from thecompiler executables listed incompilers inconfig-lang.in.

install-info

Install info documentation for the front end, if it is present in thesource directory. This target should have dependencies on info filesthat should be installed.

install-man

Install man pages for the front end. This target should ignoreerrors.

install-plugin

Install headers needed for plugins.

srcextra

Copies its dependencies into the source directory. This generally shouldbe used for generated files such as Bison output files which are notversion-controlled, but should be included in any release tarballs. Thistarget will be executed during a bootstrap if‘--enable-generated-files-in-srcdir’ was specified as aconfigure option.

srcinfo

srcman

Copies its dependencies into the source directory. These targets will beexecuted during a bootstrap if ‘--enable-generated-files-in-srcdir’was specified as aconfigure option.

uninstall

Uninstall files installed by installing the compiler. This iscurrently documented not to be supported, so the hook need not doanything.

mostlyclean

clean

distclean

maintainer-clean

The language parts of the standard GNU‘*clean’ targets. SeeStandard Targets forUsers inGNU Coding Standards, for details of the standardtargets. For GCC,maintainer-clean should deleteall generated files in the source directory that are not version-controlled,but should not delete anything that is.

Make-lang.in must also define a variablelang_OBJSto a list of host object files that are used by that language.

Previous:The Front Endconfig-lang.in File, Up:Anatomy of a Language Front End   [Contents][Index]