-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Applied to HEAD.

  * looking for [EMAIL PROTECTED]/libtool--devo--1.0--patch-362 to compare with
  * comparing to [EMAIL PROTECTED]/libtool--devo--1.0--patch-362
  M  doc/libtool.texi
  M  ChangeLog
  
  * modified files
  
  Index: Changelog
  from  Gary V. Vaughan  <[EMAIL PROTECTED]>
        * doc/libtool.texi (Distributing libltdl): Document correct use of
        LT_CONFIG_LTDL_DIR mode argument with Autoconf and Automake.
  
  --- orig/doc/libtool.texi
  +++ mod/doc/libtool.texi
  @@ -4207,10 +4207,110 @@
   is bad.  Ensuring that only one copy of the libltdl sources are linked
   into any program is left as an exercise for the reader.
   
  [EMAIL PROTECTED] LT_CONFIG_LTDL_DIR (@var{DIRECTORY})
  [EMAIL PROTECTED] LT_CONFIG_LTDL_DIR (@var{DIRECTORY}. @var{LTDL-MODE})
   Declare @var{DIRECTORY} to be the location of the @code{libltdl}
   source files, for @command{libtoolize --ltdl} to place
  -them. @xref{Invoking libtoolize}, for more details.
  +them. @xref{Invoking libtoolize}, for more details.  Provided that you
  +add an appropriate @code{LT_CONFIG_LTDL} call in your
  [EMAIL PROTECTED] before calling @command{libtoolize}, the
  +appropriate @code{libltdl} files will be installed automatically without
  +manually specifying the mode to @command{libtoolize} explicitly.
  +
  [EMAIL PROTECTED] can be either @samp{nonrecursive}, @samp{recursive}, or
  [EMAIL PROTECTED] depending on how you wish for your project to build
  [EMAIL PROTECTED]  In order for @command{libtoolize} to detect
  [EMAIL PROTECTED] correctly, if you supply one of these arguments, they
  +must be given literally (i.e. macros or shell variables that expand to
  +the correct @var{LTDL-MODE} will not work):
  +
  [EMAIL PROTECTED] @samp
  [EMAIL PROTECTED] nonrecursive
  +This is how the Libtool project distribution builds the @code{libltdl}
  +we ship and install.  If you wish to use Automake to build
  [EMAIL PROTECTED] without invoking a recursive make to descend into the
  [EMAIL PROTECTED] subdirectory, then use this option.  You will need to set
  +your configuration up carefully to make this work properly, and you will
  +need releases of Autoconf and Automake that support
  [EMAIL PROTECTED] and @code{LIBOBJDIR} properly.  In your
  [EMAIL PROTECTED], add:
  +
  [EMAIL PROTECTED]
  +AM_INIT_AUTOMAKE([subdir-objects])
  +AC_PROG_CC
  +AM_PROG_CC_C_O
  +LT_CONFIG_LTDL_DIR([libltdl], [nonrecursive])
  +LT_WITH_LTDL
  [EMAIL PROTECTED] example
  +
  [EMAIL PROTECTED]
  +And add the following near the top of your @file{Makefile.am}:
  +
  [EMAIL PROTECTED]
  +AM_CPPFLAGS =
  +AM_LDFLAGS =
  +
  +BUILT_SOURCES =
  +EXTRA_DIST =
  +CLEANFILES =
  +MOSTLYCLEANFILES =
  +
  +noinst_LTLIBRARIES =
  +lib_LTLIBRARIES =
  +EXTRA_LTLIBRARIES =
  +
  +include libltdl/Makefile.inc
  [EMAIL PROTECTED] example
  +
  [EMAIL PROTECTED]
  +Unless you don't build any other libraries from this @file{Makefile.am},
  +you will also need to change @code{lib_LTLIBRARIES} to assign with
  [EMAIL PROTECTED] so that the @code{libltdl} targets declared in
  [EMAIL PROTECTED] are not overwritten.
  +
  [EMAIL PROTECTED] recursive
  +This build mode still requires that you use Automake, but (in contrast
  +with @samp{nonrecursive}) uses the more usual device of starting another
  [EMAIL PROTECTED] process in the @file{libltdl} subdirectory.  To use this
  +mode, you should add to your @file{configure.ac}:
  +
  [EMAIL PROTECTED]
  +AM_INIT_AUTOMAKE
  +LT_CONFIG_LTDL_DIR([libltdl], [recursive])
  +LT_WITH_LTDL
  +AC_CONFIG_FILES([libltdl/Makefile])
  [EMAIL PROTECTED] example
  +
  [EMAIL PROTECTED]
  +and to your @file{Makefile.am}:
  +
  [EMAIL PROTECTED]
  +SUBDIRS = libltdl
  [EMAIL PROTECTED] example
  +
  [EMAIL PROTECTED] subproject
  +This mode is the default unless you declare otherwise with
  [EMAIL PROTECTED], and is the only mode supported by previous
  +releases of libltdl.  If you do not use Autoconf in the parent project,
  +then @samp{subproject} mode @code{libltdl} contains all the necessary
  +files to configure and build itself -- you just need to arrange for your
  +build system to call @file{libltdl/configure} with appropriate options,
  +and then run @code{make} in the @code{libltdl} subdirectory.
  +
  +If you @emph{are} using Autoconf and Automake, then you will need to add
  +the following to your @file{configure.ac}:
  +
  [EMAIL PROTECTED]
  +LT_CONFIG_LTDL_DIR([libltdl], [subproject])
  +LT_WITH_LTDL
  [EMAIL PROTECTED] example
  +
  [EMAIL PROTECTED]
  +and to @file{Makefile.am}:
  +
  [EMAIL PROTECTED]
  +SUBDIRS = libltdl
  [EMAIL PROTECTED] example
  [EMAIL PROTECTED] table
   @end defmac
   
   @defmac LT_WITH_LTDL
  
  
- -- 
Gary V. Vaughan      ())_.  [EMAIL PROTECTED],gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook
_________________________________________________________
This patch notification generated by tlaapply version 1.0
http://tkd.kicks-ass.net/arch/[EMAIL PROTECTED]/cvs-utils--tla--1.0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDb2ZzFRMICSmD1gYRAtFJAJ9gKirWZzGMnNwpvgiTejqv3WpGjQCcCoPI
rx6sCOMFtRUdLPuhfAatQuM=
=UN/v
-----END PGP SIGNATURE-----


Reply via email to