search for: lua_cpath

Displaying 4 results from an estimated 4 matches for "lua_cpath".

2016 Oct 27
1
[PATCH] run.in: Quote contents of @VAR@ substitutions
...CLASSPATH "$b/java/t" prepend CLASSPATH "$b/java" @@ -171,7 +171,7 @@ prepend ERL_LIBS "$b/erlang" export ERL_LIBS # For Lua. -export LUA=@LUA@ +export LUA="@LUA@" # Can't use 'prepend' here because Lua paths use semicolons. if [ -z "$LUA_CPATH" ]; then LUA_CPATH="$b/lua/?.so" @@ -181,7 +181,7 @@ fi export LUA_CPATH # For golang. -export GOLANG=@GOLANG@ +export GOLANG="@GOLANG@" prepend GOPATH "$b/golang" export GOPATH if [ -z "$CGO_CFLAGS" ]; then @@ -198,7 +198,7 @@ fi export CGO...
2015 Feb 13
2
[PATCH] ./run: Use 'prepend' function to build paths.
...quot;$ERL_LIBS" ]; then - ERL_LIBS="$b/erlang" -else - ERL_LIBS="$b/erlang:$ERL_LIBS" -fi +prepend ERL_LIBS "$b/erlang" export ERL_LIBS # For Lua. export LUA=@LUA@ +# Can't use 'prepend' here because Lua paths use semicolons. if [ -z "$LUA_CPATH" ]; then LUA_CPATH="$b/lua/?.so" else @@ -167,11 +182,7 @@ export LUA_CPATH # For golang. export GOLANG=@GOLANG@ -if [ -z "$GOPATH" ]; then - GOPATH="$b/golang" -else - GOPATH="$b/golang:$GOPATH" -fi +prepend GOPATH "$b/golang"...
2015 Feb 13
0
Re: [PATCH] ./run: Use 'prepend' function to build paths.
...prepend VIRT_P2V_DATA_DIR "$b/p2v" > export VIRT_P2V_DATA_DIR > fi Is prepend needed here? After all, it is just a single directory. > # For Lua. > export LUA=@LUA@ > +# Can't use 'prepend' here because Lua paths use semicolons. > if [ -z "$LUA_CPATH" ]; then > LUA_CPATH="$b/lua/?.so" > else I guess using a second helper like: prepend_semicolon() { eval $1="$2\${$1:+;\$$1}" } could help? -- Pino Toscano
2012 Dec 13
3
Lua improvements
Here are a few patches I applied to get the Lua bindings to build correctly with different versions of Lua. I am not particularly happy with generating all the test scripts just for the shebang line. Since it has been a while since I had to edit autoconf/automake, this was the best I could come up with. Cheers, -Hilko