Re: Documentation for Manual for Dynamically Linked Functions

[John W. Eaton]

On 25-Apr-2007, David Bateman wrote:

| John W. Eaton wrote:
| > On 25-Apr-2007, David Bateman wrote:
| > 
| > | John W. Eaton wrote:
| > | > On 25-Apr-2007, David Bateman wrote:
| > | > 
| > | > | If we do we need to be careful to replace all of the TABs with 8
| > | > | whitespaces, as the formating in the @example environment doesn't 
handle
| > | > | the TABs correctly..
| > | > 
| > | > OK, I did this and modified dynamic.txi to use @verbatiminclude, but
| > | > using a macro like this:
| > | > 
| > | >   @macro examplefile{file}
| > | >   @example
| > | >   @group
| > | >   @verbatiminclude @value{top_srcdir}/examples/\file\
| > | >   @end group
| > | >   @end example
| > | >   @end macro
| > | > 
| > | > so the example files can be included with just
| > | > 
| > | >   @examplefile{filename}
| > | > 
| > | > The conf.texi file also now has a definition for top_srcdir to make
| > | > this work.
| > | 
| > | Can we have the attached patch as well so that top_srcdir is the
| > | absolute directory so that out of tree builds work correctly.
| > 
| > Probably, but first can we have the patch attached?
| > 
| > jwe
| > 
| > 
| 
| Opps, sorry.

OK, I applied this and fixed the macro dynamic.txi to use
abs_top_srcdir.

I only do out of source tree builds when I'm working on Octave but
didn't notice the problem because I always run configure with an
absolute path so srcdir is absolute.

jwe