On Sun, 21 Feb 2010, Ralf Wildenhues wrote:
but this does not help much unless I know the directory where the
build was performed (not always the case). The "./" bit in front of
test-suite.log is not really very helpful. What would be much more
helpful is if a full path from root is reported so that I can view
the right file regardless of my current directory.
I'm not sure I understand. The code in question uses something like
See $(subdir)/$(TEST_SUITE_LOG).
which should expand to the full relative patch of the log file, starting
from the top builddir in a package.
Is $(subdir) wrong in your Makefile, or are you using a package
hierarchy with sub-configure scripts? In the latter case, autotools so
far never produce relative paths wrt. the topmost package.
$(subdir) is always '.' for my non-recursive project. Totally useless
info. Even if it contained './foo/test-suite.log', it would be not
be much more helpful.
To clarify, I run test suites for many different builds on many
different systems and at the end of the test run, there is just this
little summary message in a terminal window at the end of the run
which gives no clue as to what directory the build was done in. In
some cases, my build/test scheme uses a command script which causes
the build to be done in some other directory so that when the build
completes, the original directory is restored. Without some other way
to glean what I did, when I come back to a terminal session, it is not
always easy to find the relevant test-suite.log file.
If an absolute path is provided instead, then there is no confusion.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
