[Top][All Lists]

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

Some problems I had with texi/info files

From: BeN [F1233 121D312]
Subject: Some problems I had with texi/info files
Date: Sat, 17 Feb 2007 03:59:04 +0100
User-agent: Thunderbird (X11/20061220)

Hello all.

The following example explains the problems I had.
gentoo/gnu/linux kernel-2.6.20 i686
automake (GNU automake) 1.10
autoconf (GNU Autoconf) 2.61

The tree looks like

|           +--
|           +-- project.texi

info_TEXINFOS = project.texi

AM_INIT_AUTOMAKE([foreign 1.6])

#the project.texi file has a line :
@include version.texi

*1st problem*

version.texi is missing when running `make'. Running `make version.texi' won't generated it. I have to do `make stamp-vti' or `make dist' to have it generated. I have noticed that version.texi is not updated either when I change the version number in the and run (autoconf and configure) ... Once again I have to run explicite make with stamp-vti or dist target. Is that on purpose ?

Rules in Makefile are:

$(srcdir)/version.texi: # $(srcdir)/stamp-vti
$(srcdir)/stamp-vti: project.texi $(top_srcdir)/configure

The '#' char should be the reason why `make version.texi' does not produce the file. It explains the first error since the .info file rule depend on matching .texi and version.texi but this last rule does not work.

$(srcdir)/ project.texi $(srcdir)/version.texi

*2nd problem*

>cd build
../project/project.texi:7: @include `version.texi': No such file or directory. makeinfo: Removing output file `../project/' due to errors; use --force to preserve.

>make stamp-vti
Updating ../project/version.texi
makeinfo -I ../project -o ../project/ ../project/project.texi

Here I was expecting to have something like that:
makeinfo -I ../project -o ./ ../project/project.texi

From my point of view the info file should be generated in the build directory. In a more general case shouldn't all generated files including temp files be generated in the build directory ? The source directory may have its write access denied (indeed very unexpected) ... Anyway the discussion is open for temp or intermediat files but output target such as .info files should definitevely be generated in the build directory. Well that's what I think ^^.

So my guess is that a ${srcdir)/ should be replaced by ${builddir}/ or something like that...
Same goes for version.texi ...
Probably this problem exists for some other target types.

I'd like to have your point of view on all this.


reply via email to

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