Steve Youngs <[EMAIL PROTECTED]> writes: > I'm not totally convinced that PUSHPATH DTRT anyway.
Its necessary to set the load-path properly to compile because some Xtla source files require other source files. I'm not the one who wrote the code defining PUSHPATH, I find it quite complicated for what it does, but well, it works. > It definitely doesn't for xtla-build. Why? There's no difference between calling a file by its name or by its full path if the path comes first in load-path, is there? > > I don't like ../@srcdir@ because if I do > > > cd /tmp > > mkdir build > > cd build > > ~/path/to/xtla/configure > > make > > > then, I get > > > EXTRA_OPTS = -l ..//home/moy/emacs-lisp/xxtla/lisp/xtla-build > > But you're missing a couple of important facts... > > 1) The path is legit. > 2) The build succeeds. Hmm, OK: Emacs has a different interpretation of "//" than unix here. Unix would interpret this as ../home/moy/emacs-lisp/xxtla/lisp/xtla-build, whereas Emacs treats this as /home/moy/emacs-lisp/xxtla/lisp/xtla-build, so, it works, yes. (Still, I don't like relying on a strange interpretation of the double slash, but, if it works ...) > > If the path is necessary, then, I suppose @abs_srcdir@ would be better > > No, I tried @[EMAIL PROTECTED] it didn't work. :-( If I write EXTRA_OPTS = -l @[EMAIL PROTECTED] It expands to EXTRA_OPTS = -l /home/moy/emacs-lisp/xxtla/lisp/xtla-build or (if configure is called with a relative path) EXTRA_OPTS = -l /home/moy/emacs-lisp/xxtla/++emacs/lisp/../../lisp/xtla-build And the build succeeds. What was the problem for you? -- Matthieu
