Hi Vincent,
On 2016-02-25 14:29, Vincent Danjean wrote:
> Thank you very much for this info. I will add it upstream.
> Can you also send me a (small) lualatex source file, so that I add it
> to the list of documents I try to compile when testing the build?
> (I never looked at luatex for now).
I have a tikz guru sitting next to me, so we are usually using
lualatex --shell-escape here. ;-)
Any document you use with pdflatex should also work in lualatex,
but that would be boring :-)
So let's do something that won't work in pdflatex:
\documentclass{article}
\usepackage{luacode}
\begin{document}
A random number:
\begin{luacode}
tex.print(math.random())
\end{luacode}
\end{document}
You can also replace the body with "Hello, World!" or whatever you like
if you don't want to run lua stuff in there, the \usepackage{luacode}
is already sufficient to rule out pdflatex.
Build with
PDFLATEX = lualatex
include LaTeX.mk
Also the LU_UTILS autodetection does not work - 'cp --heelp' does fail
on GNU and is interpreted as BSD. Kill one 'e' and it should do :-)
I'm not sure whether the following fix is correct, at least it got
me some (sensible) output while debugging stuff (instead of an empty
string)
$$(warning Stopping generation of $$@) \
- $$(warning I got max recursion level $$(LU_$(1)_$(2)_MAX_REC)) \
+ $$(warning I got max recursion level $$(call
lu-getvalue,MAX_REC,$(1),$(2))) \
$$(warning Set LU_$(1)_$(2)_MAX_REC, LU_MAX_REC_$(1) or
LU_MAX_REC if you need it) \
and while we are at debugging ... VERB=verbose was not verbose
enough for me (while debugging that .bbl - .aux loop) , so I set
COMMON_HIDE = set -x;
That shows the actual path taken through the embedded shell scripts ...
Maybe that's helpful.
Andreas
