|
From: | Tacvek |
Subject: | Re: [Enigma-devel] Lua 5.1 "luaL_error" problems on Windows |
Date: | Sat, 29 Jul 2006 13:57:37 -0400 |
----- Original Message ----- From: "Ronald Lamprecht" <address@hidden>
To: "Tacvek" <address@hidden> Cc: <address@hidden> Sent: Thursday, July 27, 2006 4:20 PM Subject: Re: [Enigma-devel] Lua 5.1 "luaL_error" problems on Windows
Hi, Tacvek wrote:Ok. I just got an Enigma version to work correctly with a C++ lua build. :DWorks correctly as in does not crash on any of those tests.Great!Either of the patches can be used to stop the crashing on Windows.The patch called simple compiles liblua as C++ and disables building the tolua++ toolfor all MingW32 compiles.The patch named complex is my preffered patch. It adds a new configure option: --enable-cxxlua/--disable--cxxlua. This option causes liblua to be compiled as C++ and disbales building the tolua++ tool. It defaults to disabled, except on MingW32,where it defaults to enabled.The second patch would be the preferable patch. I compile on Windows, too. But it is not essential to build a Windowstolua++ within Enigma. Is a tolua++ build possible with your "--disable-cxxlua"There should be absolutely no changes versus the current situation if you are using--disable-cxxlua.Every single change (except those to configure) should be properly set off by preprocessordirectives, or the equivlent for the automake changes.Well I had to make a minor change to your configure.ac patch that did not accept --disable-cxxlua if MINGW32 was set.
I've attached a diff against the latest SVN head that fixes the problem without adding "--enable-cxxlua" to the "--help" output twice. This time I've tested it completely, and all 6 situations
work as expected.
autoconfcxxlua.patch
Description: Binary data
[Prev in Thread] | Current Thread | [Next in Thread] |