Ralf Wildenhues ralf.wildenh...@gmx.de writes:
OK. So IIUC one example dependency graph would be something like this:
( sin.go cos.go exp.go ) - math.OBJEXT - libfem.so
( grid.go solver.go )- sub/pdesolve.OBJEXT ---^
where the sets of .go files are distinct, the sets of object
Ralf Wildenhues ralf.wildenh...@gmx.de writes:
[ dropping libtool@ ]
* Ian Lance Taylor wrote on Mon, Nov 01, 2010 at 09:48:03PM CET:
Ralf Wildenhues ralf.wildenh...@gmx.de writes:
We need a bit of new notation for this, and we need to teach automake
about languages that shouldn't have
When automake is configured to use DejaGNU, it uses two different values
for srcdir. There are two different cases in lib/am/dejagnu.am:
The first is in check-DEJAGNU:
check-DEJAGNU: site.exp
## Life is easiest with an absolute srcdir, so do that.
srcdir=`$(am__cd) $(srcdir) pwd`;
Stefano Lattarini stefano.lattar...@gmail.com writes:
Are you sure about this? Why then is the attached testcase working
(for me at least)?
I guess I'm not sure what point you are trying to make with your
example. A relative srcdir will sometimes work and sometimes fail. It
seemed to me an
Stefano Lattarini stefano.lattar...@gmail.com writes:
On Thursday 13 January 2011, Ian Lance wrote:
Stefano Lattarini stefano.lattar...@gmail.com writes:
Are you sure about this? Why then is the attached testcase working
(for me at least)?
I guess I'm not sure what point you are
Stefano Lattarini stefano.lattar...@gmail.com writes:
(I think avoiding info documentation being built in the source directory,
so that builds could use a non-writable source directory, may have been
one part).
There is probably some hack to obtain this effect (it's tested in the
testsuite
Stefano Lattarini stefano.lattar...@gmail.com writes:
Anyway the real use in the src tree is different, IIUC.
Info files are built in the build tree by developers, but put in the
source tree for distribution.
In such a setup, what is the issue with having the '.info' files built
in the
Stefano Lattarini stefano.lattar...@gmail.com writes:
But since I'm not yet ready to publish this new feature, I intend to make
it available only though the new, undocumented option named (literally)
hack!info-in-builddir. I hope this is acceptable to you.
Sure, works for me.
Thanks.
Ian
Stefano Lattarini stefano.lattar...@gmail.com writes:
But since I'm not yet ready to publish this new feature, I intend to make
it available only though the new, undocumented option named (literally)
hack!info-in-builddir. I hope this is acceptable to you.
Sure, works for me.
Thanks.
Ian
