RE: Makefile vs LUA_PATH inconsistency

[Thijs Schreijer <thijs@...>]

> -----Original Message-----
> From: lua-l-bounces@lists.lua.org [mailto:lua-l-bounces@lists.lua.org] On
> Behalf Of Philipp Janda
> Sent: dinsdag 20 mei 2014 18:02
> To: lua-l@lists.lua.org
> Subject: Re: Makefile vs LUA_PATH inconsistency
> 
> >
> > What alternative would you suggest that works on Windows, using any
> > of the available toolchains, doesn't require a lot of upfront
> > fiddling to build, nor a lot of afterwork to relocate files, fix
> > paths etc. ?
> 
> There is no option on Windows that works that way. At the very least you
> have to put `lua[c].exe` and `lua5x.dll` in a directory in PATH, move
> the three or four public include files into a directory in your
> compiler's include path, and the import library (and/or dll) into your
> compiler's library directory. As an alternative you could just use the
> extracted archive as final installation, but then you have to add the
> `src` directory to PATH, INCLUDE, and LIB (or specify the latter two via
> compiler options).
> 
> For a newbie I would just say "run this installer", or if he/she really
> wants to get dirty: "Put lua.exe and lua5x.dll in a directory in your
> PATH, and when you want to compile your own extensions, then come back
> for detailed instructions for your compiler".

It can be minimized;
Clone the lua52 modified code ( https://github.com/Tieske/lua52/tree/windows_friendly ) then do

make mingw
make install INSTALL_TOP="c:/program files/lua/"
set PATH=c:\program files\lua\bin;%PATH%

That’s all for Lua to be up and running. All that is left to do is to persist the change to the path after a reboot. It won't get much simpler than this.

Then download luarocks and do;
install /MW /LV 5.2 /TREE "c:\program files\lua\"

And any newbie is set to use Lua and a fast number of Lua and binary modules with the least amount of hassle. 5 lines, 1 variable and everything works as expected...



> 
> >
> >> Are
> >> you using MSYS by any chance? It seems that plain MinGW doesn't have
> >> `rm` or `install` executables (or a `mkdir` that understands `-p`), so
> >> you really have to work hard to make the install target work for MinGW
> ...
> >
> > Iirc, some on the list use TDM as well.
> 
> So, I assume TDM includes those programs?!

I don't know TDM

> 
> >
> >> Also you should probably avoid GNU make features or you will break the
> >> Makefile for some Unixes. And I think you are missing some `.exe` file
> >> extensions in the modified install target.
> >
> > Which then? (Note that lua and luac do not need the .exe extension when
> building)
> 
> Also when installing? Does `install` copy `lua.exe` if you just say `lua`?

It works, give it a try.

> 
> 
> Philipp
> 
> 
>