cvs commit: ALFS/nALFS/doc/hackers_guide/chapter01 cvs.xml

kpfleming at linuxfromscratch.org kpfleming at linuxfromscratch.org
Tue Nov 4 10:21:05 PST 2003


kpfleming    03/11/04 11:21:05

  Modified:    nALFS/doc/hackers_guide/chapter01 cvs.xml
  Log:
  CVS usage instructions update
  
  Revision  Changes    Path
  1.5       +23 -13    ALFS/nALFS/doc/hackers_guide/chapter01/cvs.xml
  
  Index: cvs.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/nALFS/doc/hackers_guide/chapter01/cvs.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- cvs.xml	31 Oct 2003 02:46:32 -0000	1.4
  +++ cvs.xml	4 Nov 2003 18:21:05 -0000	1.5
  @@ -12,15 +12,15 @@
   be rebuilt.</para>
   
   <para>In addition, if you are going to make changes to
  -<filename>configure.ac</filename>, you should add the
  -<filename>"--enable-maintainer-mode"</filename> parameter to the
  +<filename>bootstrap</filename>, you should add the
  +<filename>"--enable-maintainer-mode"</filename> parameter to your
   <filename>configure</filename> command. With this done, each time you edit
  -<filename>configure.ac</filename>, the <filename>Makefile</filename> will
  -automatically re-run <filename>configure</filename> to make your changes take
  -effect. Be warned though, that if you manually edit
  -<filename>Makefile.am</filename>, you must modify the
  -<filename>bootstrap</filename> script to incorporate your changes, because
  -<filename>Makefile.am</filename> is not stored in the <acronym>CVS</acronym>
  +and re-run <filename>bootstrap</filename>, the <filename>Makefile</filename>
  +will automatically re-run <filename>configure</filename> to make your changes
  +take effect. Be warned though, that if you manually edit
  +<filename>Makefile.am</filename> or <filename>configure.ac<filename>, you must 
  +modify the <filename>bootstrap</filename> script to incorporate your changes, 
  +because these files are not stored in the <acronym>CVS</acronym>
   repository.</para>
   
   <para>If you add any C source files to the tree, you will need to rerun the
  @@ -30,6 +30,16 @@
   dist" from that same tree, in which case those added headers would not
   get included into the tarball.</para>
   
  +<para>If you add or remove "syntax versions" in any of the handlers, 
  +you must re-run <filename>bootstrap</filename> to get the version lists in
  +<filename>Makefile.am</filename> and <filename>configure.ac</filename> to
  +incorporate your changes, or you will experience unusual build behavior.</para>
  +
  +<para>If you add or remove any program options in <filename>src/options.h</filename>, 
  +you must re-run <filename>bootstrap</filename> to regenerate src/option-list.h.
  +Without that file being regenerated, you may experience compile errors or find
  +that your newly added option does not work properly.</para>
  +
   <para>All other types of files fall into two categories:</para>
   
   <blockquote><para>those that should be present <emphasis>only</emphasis> in the CVS
  @@ -40,7 +50,7 @@
   
   <blockquote><para>those that should be added to the distribution tarball</para></blockquote>
   
  -<para>The <filename>bootstrap</filename> script will need to be edited,
  +<para>The <filename>bootstrap.Makefile</filename> script will need to be edited,
   specifically the line that sets <filename>EXTRA_DIST</filename> near the
   beginning of the script. Add the path(s) to the new files to this line, or add
   an additional line starting with "<filename>EXTRA_DIST
  @@ -56,15 +66,15 @@
   <para>The <acronym>CVS</acronym> repository copy of &book-product; does not
   include an executable <filename>configure</filename> script nor a
   <filename>Makefile</filename>. This is by design, as there is a script to
  -create them, which ensures that the <filename>Makefile</filename> content will
  +create them, which ensures that their contents will
   always be up to date with the source tree contents and not require manual
   editing.</para>
   
   <para>&book-product; has been configured to use the <acronym>GNU</acronym>
   <filename>autotools</filename> suite for its build process. The build system
  -was created using <filename>autoconf-2.57</filename>, <filename>automake-
  -1.7.7</filename> and <filename>libtool-1.5</filename>. If you use older
  -versions than those, you may experience warnings and/or outright failures
  +was created using <filename>autoconf-2.57</filename>, <filename>automake-1.7.7</filename> 
  +and <filename>libtool-1.5</filename>. If you use older versions than those, 
  +you may experience warnings and/or outright failures
   (<filename>automake-1.6</filename> is known to be unable to handle the
   &book-product; <filename>Makefile.am</filename>).</para>
   
  
  
  



More information about the alfs-log mailing list