Makefile.in: Get parsedir and docobjdir from configure.

2003-10-20  Kelley Cook  <kcook@gcc.gnu.org>

	* Makefile.in: Get parsedir and docobjdir from configure.
	* configure.in: Recogonize --enable-generated-files-in-srcdir.
	Pass along parsedir and docobjdir.
	* configure: Regenerate.
	* doc/install.texi: Document --enable-generated-files-in-srcdir.

From-SVN: r72731

gcc/ChangeLog

 2003-10-20  Kelley Cook  <kcook@gcc.gnu.org>
 
+	* Makefile.in: Get parsedir and docobjdir from configure.
+	* configure.in: Recogonize --enable-generated-files-in-srcdir.
+	Pass along parsedir and docobjdir.
+	* configure: Regenerate.
+	* doc/install.texi: Document --enable-generated-files-in-srcdir.
+
+2003-10-20  Kelley Cook  <kcook@gcc.gnu.org>
+
 	* Makefile.in: Define $(docdir) before the Make-lang.in fragments are
 	included.
 

gcc/Makefile.in

@@ -76,11 +76,10 @@ program_transform_cross_name = @program_transform_name@
 srcdir = @srcdir@
 
 # These directories contain files that are provided as part of a FSF tarball,
-# but not provided in CVS.  Some GCC integrators like to use the CVS sources
-# but keep them read-only during a build, and so change these variables
-# from these defaults.
-parsedir = $(srcdir)
-docobjdir = $(srcdir)/doc
+# but not provided in CVS.  Unless --enable-generated-files-in-srcdir is
+# specified these files will be put in the object directory.
+parsedir = @parsedir@
+docobjdir = @docobjdir@
 docdir = $(srcdir)/doc
 
 # Top build directory, relative to here.

gcc/configure.in

@@ -148,6 +148,20 @@ elif test x$withval != xno; then
   cpp_install_dir=$withval
 fi])
 
+# We would like to our source tree to be readonly.  However when releases or
+# pre-releases are generated, the flex/bison generated files as well as the 
+# various formats of manuals need to be included along with the rest of the
+# sources.  Therefore we have --enable-generated-files-in-srcdir to do 
+# just that.
+
+AC_ARG_ENABLE(generated-files-in-srcdir, 
+[  --enable-generated-files-in-srcdir  Put generated files in source dir],
+[case ${enableval} in
+  no)    parsedir='$(objdir)'; docobjdir='$(objdir)/doc';;
+  yes,*) parsedir='$(srcdir)'; docobjdir='$(srcdir)/doc';;
+esac],
+[parsedir='$(objdir)'; docobjdir='$(objdir)/doc';])
+
 # -------------------
 # Find default linker
 # -------------------
@@ -2922,6 +2936,8 @@ AC_SUBST(objdir)
 # Substitute configuration variables
 AC_SUBST(subdirs)
 AC_SUBST(srcdir)
+AC_SUBST(docobjdir)
+AC_SUBST(parsedir)
 AC_SUBST(all_boot_languages)
 AC_SUBST(all_compilers)
 AC_SUBST(all_gtfiles)

gcc/doc/install.texi

@@ -957,6 +957,20 @@ catalog, configuring with @option{--enable-maintainer-mode} will enable
 this.  Note that you need a recent version of the @code{gettext} tools
 to do so.
 
+@item --enable-generated-files-in-srcdir
+Neither the .c and .h files that are generated from bison and flex nor the
+info manuals and man pages that are built from the .texi files are present
+in the CVS development tree.  When building GCC from that development tree,
+or from a snapshot which are created from CVS, then those generated files
+are placed in your build directory, which allows for the source to be in a
+readonly directory.
+
+If you configure with @option{--enable-generated-files-in-srcdir} then those
+generated files will go into the source directory.  This is mainly intended
+for generating release or prerelease tarballs of the GCC sources, since it
+is not a requirement that the users of source releases to have flex, bison, or
+makeinfo.  
+
 @item --enable-version-specific-runtime-libs
 Specify
 that runtime libraries should be installed in the compiler specific