[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Feature Request: LuaWinMake in Next Release?
- From: Thijs Schreijer <thijs@...>
- Date: Fri, 1 Jun 2018 11:47:42 +0000
> On 30 May 2018, at 11:40, Gisle Vanem <email@example.com> wrote:
> Russell Haley wrote:
>> I took a few minutes today at work with a fresh Windows 10 VM to test LuaWinMake with the Visual Studio C++ Build Tools and can report success. All I had to do was open the "Visual Studio Developer Console", move the winmake.bat file into my Lua directory and type winmake.bat.
> Nice, I tried it. But it does not with a TCC/4NT-shell
> (it doesn't like the awful cmd construct in LFCHAR).
Well, that is a commercial command-shell replacement… if it doesn’t work maybe raise an issue with them regarding compatibility?
And yes it is one of the ugliest hack I’ve ever done, and that says a lot . Unfortunately Windows batch files are still the most “compatible” way of doing stuff like this without extra dependencies. But it does require occasional hacks due to its limitations.
> That aside, how can it build a 32-bit LUA with a dual-mode
> MinGW (tdm-gcc or MinGW64-w64). With those, when winmake.bat does
> a 'gcc', it implies 64-bit ('gcc -m64'). How can I specify
> 'gcc -m32'?
> There should perhaps be a way to 'set EXTRAFLAG=-m32' from the
The aim of luawinmake is to just build Lua. It auto-detects the Lua version from the source code. It works for Lua 5.1, 5.2 and 5.3 (5.4 is available as a separate branch). And it works with all common compilers available for Windows (also auto-detected).
So a PR would be most welcome :)
 unfortunately about more of my code than just luawinmake :)