[wxlua-users] Compilation errors without compat28 setting with the trunk version
Hi John, I came across few more compilation errors when compat28 flag is not used: [ 17%] Building CXX object modules/luamodule/CMakeFiles/wxLuaModule.dir/__/wxbind/src/wxcore_geometry.cpp.o /home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp: In function 'int wxLua_wxMouseState_LeftDown(lua_State*)': /home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:455:27: error: 'class wxMouseState' has no member named 'LeftDown' bool returns = (self-LeftDown()); ^ /home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp: In function 'int wxLua_wxMouseState_MiddleDown(lua_State*)': /home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:487:27: error: 'class wxMouseState' has no member named 'MiddleDown' bool returns = (self-MiddleDown()); ^ /home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp: In function 'int wxLua_wxMouseState_RightDown(lua_State*)': /home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:503:27: error: 'class wxMouseState' has no member named 'RightDown' bool returns = (self-RightDown()); ^ This is using the latest trunk of wxlua and wxwidgets (compiling on Linux). The compilation proceeded successfully when I added --enable-compat28. Paul. -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231iu=/4140/ostg.clktrk ___ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
Re: [wxlua-users] Compilation errors without compat28 setting with the trunk version
On Fri, Feb 7, 2014 at 6:48 PM, Paul K paulclin...@yahoo.com wrote: Hi John, I came across few more compilation errors when compat28 flag is not used: Yes, there are far more differences than I realized, you'll have to use --enable-compat28 for the near future. I have also seen some problems with the wxLua app (editor.wx.lua) not exiting for some reason with 3.0, but not 2.9.x if I remember correctly. I am also thinking that the switch to 3.0 without compat28 will probably pose problems for people since Lua won't give compile time errors for missing/changed functions. It might not be too hard to make some sort of diff file using the code from bindings.wx.lua to print the full list of functions for each version. John -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231iu=/4140/ostg.clktrk___ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
Re: [wxlua-users] Compilation errors without compat28 setting with the trunk version
Hi John, Yes, there are far more differences than I realized, you'll have to use --enable-compat28 for the near future. That's okay; I already added it to some of my build scripts, just wanted to let you know. I have also seen some problems with the wxLua app (editor.wx.lua) not exiting for some reason with 3.0, but not 2.9.x if I remember correctly. I have seen this in my application as well, even with 2.9.5. I'd like to get to the bottom of it, but so far I've been using os.exit() at the end of my main script. For some reason, each of the platforms is guilty in some way: -- (1) to fix a crash on OSX when closing with debugging in progress. -- (2) to fix a crash on Linux 32/64bit during GC cleanup in wxlua -- after an external process has been started from the IDE. -- (3) to fix exit on Windows when started as bin\lua src\main.lua. I just tested the last one using 2.9.5; if I don't have os.exit() at the end, the script just hangs. Not sure why... In cases 1 and 2, I do call :Detach() on the started process, but it still crashes after MainLoop is done without os.exit(). Paul. On Fri, Feb 7, 2014 at 8:44 PM, John Labenski jlaben...@gmail.com wrote: On Fri, Feb 7, 2014 at 6:48 PM, Paul K paulclin...@yahoo.com wrote: Hi John, I came across few more compilation errors when compat28 flag is not used: Yes, there are far more differences than I realized, you'll have to use --enable-compat28 for the near future. I have also seen some problems with the wxLua app (editor.wx.lua) not exiting for some reason with 3.0, but not 2.9.x if I remember correctly. I am also thinking that the switch to 3.0 without compat28 will probably pose problems for people since Lua won't give compile time errors for missing/changed functions. It might not be too hard to make some sort of diff file using the code from bindings.wx.lua to print the full list of functions for each version. John -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231iu=/4140/ostg.clktrk ___ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231iu=/4140/ostg.clktrk ___ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
