Changes between Version 2 and Version 3 of pm-base-make


Ignore:
Timestamp:
Jun 1, 2006 7:17:16 PM (14 years ago)
Author:
andreasw
Comment:

minor corrections

Legend:

Unmodified
Added
Removed
Modified
  • pm-base-make

    v2 v3  
    5757}}}
    5858
    59  * One should always start with a copyright note and author information, and include the {{{svn:keyword}}} "{{{$Id}}}"
     59 * One should always start with a copyright note and author information, and include the {{{svn:keyword}}} "{{{$Id}}}".  The line with the keyword should start with "{{{##}}}" so that it is not copied into the generated {{{Makefile.in}}} file.
    6060
    6161 * The '''AUTOMAKE_OPTIONS''' variable is a special variable that indicates certain options for the {{{automake}}} run.  The '''foreign''' option doesn't require the strict conformance with GNU guidelines.
     
    6969 * For C++ packages, we usually also provide a target '''doxydoc''', which runs the {{{doxygen}}} program for all source code found in subdirectories.  Note the "'''cd $(srcdir)'''" here.  In case of a VPATH compilation, the Makefile generated from this {{{Makefile.am}}} file is not run in the directory where {{{doxygen}}} should be run.  The Autoconf output variable '''srcdir''' is set to the directory which contains the source code (such as the {{{Makefile.am}}} file) corresponding to the VPATH directory.
    7070
    71  * Finally, we '''include the BuildTools include Makefile.am'''.  This makes sure that additional maintainer-specific targets are defined (such as an automatic update of the {{{svn:externals}}} property when the {{{Externals}}} file has been changed). 
     71 * Finally, we '''include the !BuildTools include Makefile.am'''.  This makes sure that additional maintainer-specific targets are defined (such as an automatic update of the {{{svn:externals}}} property when the {{{Externals}}} file has been changed).