 |
lua-l archive |
|
|
||
|
On Mon, Mar 19, 2018 at 10:21 AM, Isaac Hier <isaachier@gmail.com> wrote:Why don't you just use CMake? LuaDist did most of the work here:
https://github.com/LuaDist/lua.
Are you suggesting using cmake generate an nmake compliant file, or as the build tool for Lua? If the later, cmake is not installed with the Visual Studio Build Tools. If the former, I don't know enough about cmake and would rather not play there if I can avoid it. I'm not opposed to either suggestion, but it's outside the scope of my ability and toolset. If you think you can get a cmake file to generate nmake gmake and bmake files I'd be really interested in that output.I've mangled the src/Makefile enough to get things to build with nmake, but my linking is failing and I don't think the macro expansion is working the way I want. Progress in the right direction...RussOn Fri, Mar 16, 2018 at 12:20 AM, Russell Haley <russ.haley@gmail.com> wrote:
> Sorry, just to clarify the attached file doesn't work correctly yet.
>
> On Thu, Mar 15, 2018 at 9:16 PM, Russell Haley <russ.haley@gmail.com> wrote:
>>
>> Hi Lua Team,
>>
>> Microsoft has "graciously" offered the VC Build tools sans Visual Studio
>> for 2017. The install is still around 6.8 gigs, but it means a compiler and
>> nmake are present. Is there any interest in adding an nmake file to the Lua
>> sources?
>>
>> I took a brief stab at it today when I was testing the VS Build tools
>> (like 15 minutes). I will continue picking at it if there is any interest. I
>> get several "whack tons" of warnings I'll have to look into [1] :
>>
>> c:\users\russh\lua\lua-5.4.0-work1\src\lua.c(560) : warning C4711:
>> function 'dochunk' selected for automatic inline expansion
>>
>> Cheers,
>>
>> Russ
>>
>> [1] Whack Tons: The official unit for measuring compiler warnings you
>> don't know what to do with
>>
>