guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How are we supposed to handle version*.texi now?


From: Thien-Thi Nguyen
Subject: Re: How are we supposed to handle version*.texi now?
Date: Wed, 21 Nov 2001 07:15:08 -0800

   From: Rob Browning <address@hidden>
   Date: Tue, 20 Nov 2001 19:13:36 -0600

   I don't actually know ATM.  There's a node in automake about it, and
   I seem to recall some discussion in the past about our needs being
   funny -- perhaps the whole -vt1 issue?  Anyway, if no one else gets
   to it sooner, I'll check it out.

just went through this w/ guile-www.  briefly, the line:

  @include version.texi

in a foo.texi and the line:

  foo_TEXINFOS = version.texi

in same-dir Makefile.am cause automake to create rules that write
version.texi at configure-time.  to make use of multiple version.texi
files, the automake info page sez:

     If you have multiple Texinfo files, and you want to use the
  `version.texi' feature, then you have to have a separate version file
  for each Texinfo file.  Automake will treat any include in a Texinfo
  file that matches `vers*.texi' just as an automatically generated
  version file.

so for A B C, maybe we need:

  A: @include versA.texi
  B: @include versB.texi
  C: @include versC.texi

and in Makefile.am:

  A_TEXINFOS = versA.texi
  B_TEXINFOS = versB.texi
  C_TEXINFOS = versC.texi

thi



reply via email to

[Prev in Thread] Current Thread [Next in Thread]