188.8.131.52 The Front End language Directory
A front end language directory contains the source files of that front end (but not of any runtime libraries, which should be outside the gcc directory). This includes documentation, and possibly some subsidiary programs build alongside the front end. Certain files are special and other parts of the compiler depend on their names:
- This file is required in all language subdirectories. See The Front End config-lang.in File, for details of
- This file is required in all language subdirectories. It contains
.hook (where lang is the setting of
languagein config-lang.in) for the following values of hook, and any other Makefile rules required to build those targets (which may if necessary use other Makefiles specified in
outputsin config-lang.in, although this is deprecated). It also adds any testsuite targets that can use the standard rule in gcc/Makefile.in to the variable
- FIXME: exactly what goes in each of these targets?
- Build an etags TAGS file in the language subdirectory
in the source tree.
- Build info documentation for the front end, in the build directory.
This target is only called by make bootstrap if a suitable
version of makeinfo is available, so does not need to check
for this, and should fail if an error occurs.
- 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.
- 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.
- Build HTML documentation for the front end, in the build directory.
- Build generated man pages for the front end from Texinfo manuals
(see Man Page Generation), in the build directory. This target
is only called if the necessary tools are available, but should ignore
errors so as not to stop the build if errors occur; man pages are
optional and the tools involved may be installed in a broken way.
- Install everything that is part of the front end, apart from the
compiler executables listed in
- Install info documentation for the front end, if it is present in the
source directory. This target should have dependencies on info files
that should be installed.
- Install man pages for the front end. This target should ignore
- Copies its dependencies into the source directory. This generally should
be used for generated files such as Bison output files which are not
present in CVS, but should be included in any release tarballs. This
target will be executed during a bootstrap if
--enable-generated-files-in-srcdir was specified as a
- Copies its dependencies into the source directory. These targets will be
executed during a bootstrap if --enable-generated-files-in-srcdir
was specified as a configure option.
- Uninstall files installed by installing the compiler. This is
currently documented not to be supported, so the hook need not do
- The language parts of the standard GNU
*clean targets. See Standard Targets for Users (GNU Coding Standards), for details of the standard
targets. For GCC,
maintainer-cleanshould delete all generated files in the source directory that are not checked into CVS, but should not delete anything checked into CVS.
Make-lang.in must also define a variable lang
_OBJSto a list of host object files that are used by that language.
- This file registers the set of switches that the front end accepts on
the command line, and their --help text. See Options.
- This file provides entries for
default_compilersin gcc.c which override the default of giving an error that a compiler for that language is not installed.
- This file, which need not exist, defines any language-specific tree codes.