This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[doc] Document the new frontend hooks in sourcebuild.texi


As noted by Joseph, sourcebuild.texi needs to be updated due to the addition of some new target hooks recently added for the change to a read-only source directory.

Passes make doc/gccint.info and make doc/gccint.dvi

OK to install mainline and 3.4 branch?

Kelley Cook
2004-01-22  Kelley Cook  <kcook@gcc.gnu.org>

	* doc/sourcebuild.texi (srcextra, man, srcman, srcinfo):  Document new
        target hooks.
	(info, generated-manpages): Note that these are now built in the
	build directory.  Delete reference to double-colon hook.

diff -bcd gcc-orig/gcc/doc/sourcebuild.texi gcc-snapshot/gcc/doc/sourcebuild.texi
*** gcc-orig/gcc/doc/sourcebuild.texi	Sun Jan 18 06:59:08 2004
--- gcc-snapshot/gcc/doc/sourcebuild.texi	Thu Jan 22 15:23:41 2004
***************
*** 565,587 ****
  Build an @command{etags} @file{TAGS} file in the language subdirectory
  in the source tree.
  @item info
! Build info documentation for the front end, in the source directory.
  This target is only called by @samp{make bootstrap} if a suitable
  version of @command{makeinfo} is available, so does not need to check
! for this, and should fail if an error occurs.  This hook is a
! double-colon hook.
  @item dvi
  Build DVI documentation for the front end, in the build directory.
  This should be done using @code{$(TEXI2DVI)}, with appropriate
  @option{-I} arguments pointing to directories of included files.
  This hook is a double-colon hook.
  @item generated-manpages
  Build generated man pages for the front end from Texinfo manuals
! (@pxref{Man Page Generation}), in the source 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.
! This hook is a double-colon hook.
  @item install-normal
  FIXME: what is this target for?
  @item install-common
--- 565,587 ----
  Build an @command{etags} @file{TAGS} file in the language subdirectory
  in the source tree.
  @item info
! Build info documentation for the front end, in the build directory.
  This target is only called by @samp{make bootstrap} if a suitable
  version of @command{makeinfo} is available, so does not need to check
! for this, and should fail if an error occurs.
  @item dvi
  Build DVI documentation for the front end, in the build directory.
  This should be done using @code{$(TEXI2DVI)}, with appropriate
  @option{-I} arguments pointing to directories of included files.
  This hook is a double-colon hook.
  @item generated-manpages
+ @itemx man
  Build generated man pages for the front end from Texinfo manuals
! (@pxref{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.
! FIXME: The hook name is @code{@var{lang}.@var{man}}.
  @item install-normal
  FIXME: what is this target for?
  @item install-common
***************
*** 595,600 ****
--- 595,612 ----
  @item install-man
  Install man pages for the front end.  This target should ignore
  errors.
+ @item srcextra
+ Copies its dependencies into the source directory.  This generally should
+ be used for generated files such as @file{gcc/c-parse.c} which are not
+ present in CVS, but should be included in any release tarballs.  This
+ target will be executed during a bootstrap if
+ @samp{--enable-generated-files-in-srcdir} was specified as a
+ @file{configure} option.
+ @item srcinfo
+ @itemx srcman
+ Copies its dependencies into the source directory.  These targets will be
+ executed during a bootstrap if @samp{--enable-generated-files-in-srcdir}
+ was specified as a @file{configure} option.
  @item uninstall
  Uninstall files installed by installing the compiler.  This is
  currently documented not to be supported, so the hook need not do

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]