elisp: no need to "absolutize" $(srcdir) and $(builddir) ...

* lib/am/lisp.am (.el.elc): ... here: we don't chdir around anyway,
nor move or copy around our source '.el' files.  Update comments,
and re-wrap them while we are at it.

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>

diff --git a/lib/am/lisp.am b/lib/am/lisp.am
index ce87fb0..ba15bf1 100644 (file)
--- a/lib/am/lisp.am
+++ b/lib/am/lisp.am
@@ -23,16 +23,17 @@ endif %?INSTALL%
 ## ---------- ##
 
 .el.elc:
-## We add $(abs_builddir) and $(abs_srcdir) to load-path, so that any
-## .el files that $< depends upon can be found (including generated
-## ones). Prefer files from the build directory to those from the source
-## directory, in true VPATH spirit.  The destination file is normally
-## determined by appending "c" to the input (which would erronously put
-## it in $(srcdir) in VPATH builds), so we override that, too.
+## We add $(builddir) and $(srcdir) to load-path, so that any '.el' files
+## that $< depends upon can be found (including generated ones).
+## We prefer files from the build directory to those from the source
+## directory, in true VPATH spirit.
+## The destination file is normally determined by appending "c" to the
+## input (which would erronously put it in $(srcdir) in VPATH builds),
+## so we override that, too.
        if test "$(EMACS)" != "no"; then \
          $(EMACS) -q --batch \
-           --eval "(setq load-path (cons \"$(abs_srcdir)\" load-path))" \
-           --eval "(setq load-path (cons \"$(abs_builddir)\" load-path))" \
+           --eval "(setq load-path (cons \"$(srcdir)\" load-path))" \
+           --eval "(setq load-path (cons \"$(builddir)\" load-path))" \
            --eval "(defun byte-compile-dest-file (f) \"$@\")" \
            --eval "(unless (byte-compile-file \"$<\") (kill-emacs 1))"; \
        else :; fi