wxlua-users — wxLua list for users and developers

Re: [wxlua-users] How to configure wxlua to *not* link wxpng library?

[Paul K <pau...@ya...>]

Hi John,

I ended up patching the makefile
(luamodule/CMakeFiles/wxLuaModules.dir/link.txt), but would prefer
something a bit more robust.

Paul.

On Sun, Mar 17, 2013 at 9:58 AM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I ran into an issue with configuring wxlua to use system libpng
> library. I tried both --with-libpng=builtin and --with-libpng=sys, but
> I get exactly the same result.
>
> This discussion
> (https://groups.google.com/forum/?fromgroups=#!topic/wx-users/2QWQD0qUVUc)
> indicates that it's better to use a system library, but I can't
> configure wxlua to *not* link builtin library as can be see from this
> output from cmake:
>
> -- * - wxWidgets_LIBRARIES         =
> -L/home/paul/zbs/build/deps/lib;-pthread;;;/home/paul/zbs/build/deps/lib
> /libwx_gtk2u_stc-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_aui-2.9.a;/home/paul/zbs/build/deps/lib
> /libwx_baseu_net-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_html-2.9.a;/home/paul/zbs/build/deps/lib
> /libwx_gtk2u_adv-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_core-2.9.a;/home/paul/zbs/build/deps/lib
> /libwx_baseu-2.9.a;-lwxscintilla-2.9;-pthread;-lgthread-2.0;-lrt;-lX11;-lXxf86vm;-lgtk-x11-2.0;-lgdk-x11-2.0;-latk-
> 1.0;-lgio-2.0;-lpangoft2-1.0;-lpangocairo-1.0;-lgdk_pixbuf-2.0;-lcairo;-lpango-1.0;-lfreetype;-lfontconfig;-lgobject-
> 2.0;-lglib-2.0;-lwxregexu-2.9;-lwxjpeg-2.9;-lwxpng-2.9;-lwxzlib-2.9;-ldl;-lm
>
> (note the last last that includes -lwxpng-2.9). I tried (using brute
> force) to exclude wxpng from the link command, but failed. Ideally
> wxlua should somehow check if the library is configured as "builtin"
> or "sys", but for now I just need to check if this is going to work
> for me, so, I'm fine with modifying it manually. I need to exclude
> libpng as it creates problems with systems libraries required by GTK
> on Linux.
>
> What is the way for me to tell wxlua *not* to include wxpng-2.9? Thank you.
>
> Paul.

[wxlua-users] How to configure wxlua to *not* link wxpng library?

[Paul K <pau...@ya...>]

Hi John,

I ran into an issue with configuring wxlua to use system libpng
library. I tried both --with-libpng=builtin and --with-libpng=sys, but
I get exactly the same result.

This discussion
(https://groups.google.com/forum/?fromgroups=#!topic/wx-users/2QWQD0qUVUc)
indicates that it's better to use a system library, but I can't
configure wxlua to *not* link builtin library as can be see from this
output from cmake:

-- * - wxWidgets_LIBRARIES         =
-L/home/paul/zbs/build/deps/lib;-pthread;;;/home/paul/zbs/build/deps/lib
/libwx_gtk2u_stc-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_aui-2.9.a;/home/paul/zbs/build/deps/lib
/libwx_baseu_net-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_html-2.9.a;/home/paul/zbs/build/deps/lib
/libwx_gtk2u_adv-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_core-2.9.a;/home/paul/zbs/build/deps/lib
/libwx_baseu-2.9.a;-lwxscintilla-2.9;-pthread;-lgthread-2.0;-lrt;-lX11;-lXxf86vm;-lgtk-x11-2.0;-lgdk-x11-2.0;-latk-
1.0;-lgio-2.0;-lpangoft2-1.0;-lpangocairo-1.0;-lgdk_pixbuf-2.0;-lcairo;-lpango-1.0;-lfreetype;-lfontconfig;-lgobject-
2.0;-lglib-2.0;-lwxregexu-2.9;-lwxjpeg-2.9;-lwxpng-2.9;-lwxzlib-2.9;-ldl;-lm

(note the last last that includes -lwxpng-2.9). I tried (using brute
force) to exclude wxpng from the link command, but failed. Ideally
wxlua should somehow check if the library is configured as "builtin"
or "sys", but for now I just need to check if this is going to work
for me, so, I'm fine with modifying it manually. I need to exclude
libpng as it creates problems with systems libraries required by GTK
on Linux.

What is the way for me to tell wxlua *not* to include wxpng-2.9? Thank you.

Paul.

Re: [wxlua-users] wxDir is missing Traverse method in wxlua 2.8.12

[John L. <jla...@gm...>]

On Fri, Mar 15, 2013 at 11:05 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> Thank you for the link to Traverse implementation; I should have
> looked there myself. VZ uses GetFirst and GetNext, whereas I actually
> use FindFirst and FindNext. I'm not sure what exactly the differences
> are, but I'll re-implement Traverse in Lua and see if it is
> sufficiently fast for my needs.

It'll definitely be no slower than using a wxDirTraverser since you
won't have the overhead of extra calls to the traverser itself.
Directory reading is already slow enough and I couldn't see the use of
the traverser in Lua since it's far more flexible than C++ code.

Regards,
    John

Re: [wxlua-users] wxDir is missing Traverse method in wxlua 2.8.12

[Paul K <pau...@ya...>]

Hi John,

Thank you for the link to Traverse implementation; I should have
looked there myself. VZ uses GetFirst and GetNext, whereas I actually
use FindFirst and FindNext. I'm not sure what exactly the differences
are, but I'll re-implement Traverse in Lua and see if it is
sufficiently fast for my needs.

Paul.

On Fri, Mar 15, 2013 at 6:24 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I do that now (I use GetFirst() and GetNext()), but it's a bit slow
> for my purposes. GetAllFiles is much faster, but my main problem with
> it is that I can't exclude directories I don't need (for example,
> .git, .svn and others), and those can be quite slow to scan (due to a
> large number of directories and files).
>
> For example, when I try GetAllFiles it scans a folder with 278 files
> (including subfolders, most of these are in .git folder), it takes
> 0.8s to scan (and subsequent runs only take 0.08s or so). Same folder
> without .git subfolder takes only 3ms or so to scan (17 files).
>
> I'm hoping that the Traverse method would give me a way to do it fast,
> but also allow me to filter out those folders I don't need.
> Unfortunately I can't test it without having access to it.
>
> Paul.
>
> On Fri, Mar 15, 2013 at 5:51 PM, John Labenski <jla...@gm...> wrote:
>> On Fri, Mar 15, 2013 at 8:25 PM, Paul K <pau...@ya...> wrote:
>>> Hi John,
>>>
>>> I noticed that wxlua is missing the Traverse method in wxDir object
>>> (http://docs.wxwidgets.org/2.8/wx_wxdir.html#wxdirtraverse).
>>
>> Please use GetAllFiles() or roll your own GetFirst() GetNext()
>> recursive function instead.
>> http://wxlua.sourceforge.net/docs/wxluaref.html#wxDir
>>
>> An example of how to do that is here, see wxDir::Traverse()
>> http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/src/common/dircmn.cpp?view=markup
>>
>> I don't really see any gain in using it for Lua programs as it just
>> adds a layer of complexity and without enumeration type-safety can
>> cause more problems than it would solve.
>>
>> Regards,
>>     John
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_d2d_mar
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] wxDir is missing Traverse method in wxlua 2.8.12

[Paul K <pau...@ya...>]

Hi John,

I do that now (I use GetFirst() and GetNext()), but it's a bit slow
for my purposes. GetAllFiles is much faster, but my main problem with
it is that I can't exclude directories I don't need (for example,
.git, .svn and others), and those can be quite slow to scan (due to a
large number of directories and files).

For example, when I try GetAllFiles it scans a folder with 278 files
(including subfolders, most of these are in .git folder), it takes
0.8s to scan (and subsequent runs only take 0.08s or so). Same folder
without .git subfolder takes only 3ms or so to scan (17 files).

I'm hoping that the Traverse method would give me a way to do it fast,
but also allow me to filter out those folders I don't need.
Unfortunately I can't test it without having access to it.

Paul.

On Fri, Mar 15, 2013 at 5:51 PM, John Labenski <jla...@gm...> wrote:
> On Fri, Mar 15, 2013 at 8:25 PM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>> I noticed that wxlua is missing the Traverse method in wxDir object
>> (http://docs.wxwidgets.org/2.8/wx_wxdir.html#wxdirtraverse).
>
> Please use GetAllFiles() or roll your own GetFirst() GetNext()
> recursive function instead.
> http://wxlua.sourceforge.net/docs/wxluaref.html#wxDir
>
> An example of how to do that is here, see wxDir::Traverse()
> http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/src/common/dircmn.cpp?view=markup
>
> I don't really see any gain in using it for Lua programs as it just
> adds a layer of complexity and without enumeration type-safety can
> cause more problems than it would solve.
>
> Regards,
>     John
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] wxDir is missing Traverse method in wxlua 2.8.12

[John L. <jla...@gm...>]

On Fri, Mar 15, 2013 at 8:25 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I noticed that wxlua is missing the Traverse method in wxDir object
> (http://docs.wxwidgets.org/2.8/wx_wxdir.html#wxdirtraverse).

Please use GetAllFiles() or roll your own GetFirst() GetNext()
recursive function instead.
http://wxlua.sourceforge.net/docs/wxluaref.html#wxDir

An example of how to do that is here, see wxDir::Traverse()
http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/src/common/dircmn.cpp?view=markup

I don't really see any gain in using it for Lua programs as it just
adds a layer of complexity and without enumeration type-safety can
cause more problems than it would solve.

Regards,
    John

[wxlua-users] wxDir is missing Traverse method in wxlua 2.8.12

[Paul K <pau...@ya...>]

Hi John,

I noticed that wxlua is missing the Traverse method in wxDir object
(http://docs.wxwidgets.org/2.8/wx_wxdir.html#wxdirtraverse).

Is it possible to add it or is there something more fundamental that
prevents it? I'd also like to make sure that wxDirTraverser
(http://docs.wxwidgets.org/2.8/wx_wxdirtraverser.html#wxdirtraverser)
will work as it's required for Traverse to be useful. Thank you!

Paul.

[wxlua-users] [ wxlua-Bugs-3607550 ] wxLuaFreeze.exe command line problem

[SourceForge.net <no...@so...>]

Bugs item #3607550, was opened at 2013-03-10 11:25
Message generated for change (Tracker Item Submitted) made by sergo2002
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=3607550&group_id=140042

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: MaxWell (sergo2002)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxLuaFreeze.exe command line problem

Initial Comment:
Good day!
 
It seems that script files which path includes national symbols can not run under wxLuaFreeze.exe
May be wxLuaFreeze.exe converts argument to UTF and then trying to find nonexistent location.
 
Is there necessary to convert argument to UTF?
 
Thanx.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=3607550&group_id=140042

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[Paul K <pau...@ya...>]

> To be honest, this this not something I have any interest in
> implementing. Even if it was made to work by silently ignoring missing
> parts then people who wanted to use the wxLua package as a whole may
> end up missing parts by accident and that would be far worse then you
> having extra parts. I recommend simply building it as is and taking
> the parts you want.

That is what I ended up doing. Thanks for taking look at this.

Paul.

On Fri, Mar 8, 2013 at 10:41 AM, John Labenski <jla...@gm...> wrote:
> On Fri, Mar 8, 2013 at 12:45 PM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>>> You can already do that too... see CMAKE_SKIP_INSTALL_ALL_DEPENDENCY here :
>>> http://wxlua.sourceforge.net/docs/install.html#C4
>>
>> I added -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=TRUE and ran "make
>> wxLuaModule" (to get wx.* library), but still got the same error and
>> didn't get to wx.* file:
>>
>
> To be honest, this this not something I have any interest in
> implementing. Even if it was made to work by silently ignoring missing
> parts then people who wanted to use the wxLua package as a whole may
> end up missing parts by accident and that would be far worse then you
> having extra parts. I recommend simply building it as is and taking
> the parts you want.
>
> Regards,
>     John
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[John L. <jla...@gm...>]

On Fri, Mar 8, 2013 at 12:45 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
>> You can already do that too... see CMAKE_SKIP_INSTALL_ALL_DEPENDENCY here :
>> http://wxlua.sourceforge.net/docs/install.html#C4
>
> I added -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=TRUE and ran "make
> wxLuaModule" (to get wx.* library), but still got the same error and
> didn't get to wx.* file:
>

To be honest, this this not something I have any interest in
implementing. Even if it was made to work by silently ignoring missing
parts then people who wanted to use the wxLua package as a whole may
end up missing parts by accident and that would be far worse then you
having extra parts. I recommend simply building it as is and taking
the parts you want.

Regards,
    John

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[Paul K <pau...@ya...>]

Hi John,

> You can already do that too... see CMAKE_SKIP_INSTALL_ALL_DEPENDENCY here :
> http://wxlua.sourceforge.net/docs/install.html#C4

I added -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=TRUE and ran "make
wxLuaModule" (to get wx.* library), but still got the same error and
didn't get to wx.* file:

>> CMake Error at modules/wxstedit/cmake_install.cmake:31 (FILE):
>>   file INSTALL cannot find
>>   ".../wxlua/wxLua/lib/MinSizeRel/libwxstedit-wx29-1.6.0.a".
>> Call Stack (most recent call first):
>>   cmake_install.cmake:129 (INCLUDE)
>>
>> make: *** [install/strip] Error 1

Paul.

On Thu, Mar 7, 2013 at 8:19 PM, John Labenski <jla...@gm...> wrote:
> On Thu, Mar 7, 2013 at 2:46 PM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>>>> You can already choose to build whatever libs and apps you want right
>>>> now. Choose the project you want to build in MSVC or run "make help"
>>>> for GCC to list all the targets.
>>
>> There is one small issue when I select wxLuaModule as the only target
>> for make; subsequent "make install" fails with this message when it
>> tries to install (missing) wxstedit libs:
>>
>> (...more Installing... messages)
>> -- Installing: .../apps/wxluafreeze/wxluafreeze.lua
>> CMake Error at modules/wxstedit/cmake_install.cmake:31 (FILE):
>>   file INSTALL cannot find
>>   ".../wxlua/wxLua/lib/MinSizeRel/libwxstedit-wx29-1.6.0.a".
>> Call Stack (most recent call first):
>>   cmake_install.cmake:129 (INCLUDE)
>>
>> make: *** [install/strip] Error 1
>>
>> It would be nice to skip installing components that haven't been built.
>
> You can already do that too... see CMAKE_SKIP_INSTALL_ALL_DEPENDENCY here :
> http://wxlua.sourceforge.net/docs/install.html#C4
>
> The svn install doc is far more complete.
>
> Regards,
>    John
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[John L. <jla...@gm...>]

On Thu, Mar 7, 2013 at 2:46 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
>>> You can already choose to build whatever libs and apps you want right
>>> now. Choose the project you want to build in MSVC or run "make help"
>>> for GCC to list all the targets.
>
> There is one small issue when I select wxLuaModule as the only target
> for make; subsequent "make install" fails with this message when it
> tries to install (missing) wxstedit libs:
>
> (...more Installing... messages)
> -- Installing: .../apps/wxluafreeze/wxluafreeze.lua
> CMake Error at modules/wxstedit/cmake_install.cmake:31 (FILE):
>   file INSTALL cannot find
>   ".../wxlua/wxLua/lib/MinSizeRel/libwxstedit-wx29-1.6.0.a".
> Call Stack (most recent call first):
>   cmake_install.cmake:129 (INCLUDE)
>
> make: *** [install/strip] Error 1
>
> It would be nice to skip installing components that haven't been built.

You can already do that too... see CMAKE_SKIP_INSTALL_ALL_DEPENDENCY here :
http://wxlua.sourceforge.net/docs/install.html#C4

The svn install doc is far more complete.

Regards,
   John

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[Paul K <pau...@ya...>]

Hi John,

>> You can already choose to build whatever libs and apps you want right
>> now. Choose the project you want to build in MSVC or run "make help"
>> for GCC to list all the targets.

There is one small issue when I select wxLuaModule as the only target
for make; subsequent "make install" fails with this message when it
tries to install (missing) wxstedit libs:

(...more Installing... messages)
-- Installing: .../apps/wxluafreeze/wxluafreeze.lua
CMake Error at modules/wxstedit/cmake_install.cmake:31 (FILE):
  file INSTALL cannot find
  ".../wxlua/wxLua/lib/MinSizeRel/libwxstedit-wx29-1.6.0.a".
Call Stack (most recent call first):
  cmake_install.cmake:129 (INCLUDE)

make: *** [install/strip] Error 1

It would be nice to skip installing components that haven't been built.

Paul.

On Thu, Mar 7, 2013 at 10:15 AM, Paul K <pau...@ya...> wrote:
> Hi John,
>
>> Thanks for reporting, it should be fixed now.
>
> Indeed; fixed now.
>
>> You can already choose to build whatever libs and apps you want right
>> now. Choose the project you want to build in MSVC or run "make help"
>> for GCC to list all the targets.
>
> yes, this is exactly what I need. I was looking for it in the
> configure parameters instead of make.
>
> Paul.
>
> On Wed, Mar 6, 2013 at 11:39 PM, John Labenski <jla...@gm...> wrote:
>> On Wed, Mar 6, 2013 at 11:56 PM, Paul K <pau...@ya...> wrote:
>>> Hi John,
>>>
>>> I tried to compile the latest wxlua and ran into compilation errors
>>> (both on OSX and Windows). I also tried with rev 163 (before Lua 5.2
>>> changes) and compiled it successfully (also on both platforms). The
>>> error messages I got are at the bottom of the email.
>>
>> Thanks for reporting, it should be fixed now.
>>
>>> Tangentially related; would it be possible to expose
>>> wxstc.wxStyledTextCtrl.GetLibraryVersionInfo in the API? I'd like to
>>> show Scintilla version number in the About screen.
>>
>> Sure.
>>
>>> While we are on the topic of building wxlua, is it possible to provide
>>> a parameter for configure to disable building of all
>>> executables/applications and also disable building of debug/socket
>>> libraries (which I don't need)? I regularly rebuild from source and
>>> this would noticeably speed up the process (I only need
>>> wx.dll/dylib/so). Thank you.
>>
>> You can already choose to build whatever libs and apps you want right
>> now. Choose the project you want to build in MSVC or run "make help"
>> for GCC to list all the targets.
>>
>> Regards,
>>      John
>>
>> ------------------------------------------------------------------------------
>> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
>> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
>> endpoint security space. For insight on selecting the right partner to
>> tackle endpoint security challenges, access the full report.
>> http://p.sf.net/sfu/symantec-dev2dev
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[Paul K <pau...@ya...>]

Hi John,

> Thanks for reporting, it should be fixed now.

Indeed; fixed now.

> You can already choose to build whatever libs and apps you want right
> now. Choose the project you want to build in MSVC or run "make help"
> for GCC to list all the targets.

yes, this is exactly what I need. I was looking for it in the
configure parameters instead of make.

Paul.

On Wed, Mar 6, 2013 at 11:39 PM, John Labenski <jla...@gm...> wrote:
> On Wed, Mar 6, 2013 at 11:56 PM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>> I tried to compile the latest wxlua and ran into compilation errors
>> (both on OSX and Windows). I also tried with rev 163 (before Lua 5.2
>> changes) and compiled it successfully (also on both platforms). The
>> error messages I got are at the bottom of the email.
>
> Thanks for reporting, it should be fixed now.
>
>> Tangentially related; would it be possible to expose
>> wxstc.wxStyledTextCtrl.GetLibraryVersionInfo in the API? I'd like to
>> show Scintilla version number in the About screen.
>
> Sure.
>
>> While we are on the topic of building wxlua, is it possible to provide
>> a parameter for configure to disable building of all
>> executables/applications and also disable building of debug/socket
>> libraries (which I don't need)? I regularly rebuild from source and
>> this would noticeably speed up the process (I only need
>> wx.dll/dylib/so). Thank you.
>
> You can already choose to build whatever libs and apps you want right
> now. Choose the project you want to build in MSVC or run "make help"
> for GCC to list all the targets.
>
> Regards,
>      John
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[John L. <jla...@gm...>]

On Wed, Mar 6, 2013 at 11:56 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I tried to compile the latest wxlua and ran into compilation errors
> (both on OSX and Windows). I also tried with rev 163 (before Lua 5.2
> changes) and compiled it successfully (also on both platforms). The
> error messages I got are at the bottom of the email.

Thanks for reporting, it should be fixed now.

> Tangentially related; would it be possible to expose
> wxstc.wxStyledTextCtrl.GetLibraryVersionInfo in the API? I'd like to
> show Scintilla version number in the About screen.

Sure.

> While we are on the topic of building wxlua, is it possible to provide
> a parameter for configure to disable building of all
> executables/applications and also disable building of debug/socket
> libraries (which I don't need)? I regularly rebuild from source and
> this would noticeably speed up the process (I only need
> wx.dll/dylib/so). Thank you.

You can already choose to build whatever libs and apps you want right
now. Choose the project you want to build in MSVC or run "make help"
for GCC to list all the targets.

Regards,
     John

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[John L. <jla...@gm...>]

On Thu, Mar 7, 2013 at 1:08 AM, Paul K <pau...@ya...> wrote:
> Hi John,
>
>> a parameter for configure to disable building of all
>> executables/applications and also disable building of debug/socket
>> libraries (which I don't need)? I regularly rebuild from source and
>
> Just to elaborate on this a bit; I was just compiling wxlua on Linux
> and ran into an issue with wxStEdit. It requires xrc, which I don't
> include in my version of wx.so, but I don't see any option to skip
> building wxStEdit, which breaks the build process (because of missing
> dependencies). I ended up removing it from Cmake configuration
> manually (through the gui). Is there an option I'm missing to disable
> this and other components that are not required for generating wx
> library? Thank you.

No options for disabling parts.

I would include xrc as people can and do use that for GUI layout, see
the calculator sample.

Regards,
    John

Re: [wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[Paul K <pau...@ya...>]

Hi John,

> a parameter for configure to disable building of all
> executables/applications and also disable building of debug/socket
> libraries (which I don't need)? I regularly rebuild from source and

Just to elaborate on this a bit; I was just compiling wxlua on Linux
and ran into an issue with wxStEdit. It requires xrc, which I don't
include in my version of wx.so, but I don't see any option to skip
building wxStEdit, which breaks the build process (because of missing
dependencies). I ended up removing it from Cmake configuration
manually (through the gui). Is there an option I'm missing to disable
this and other components that are not required for generating wx
library? Thank you.

Paul.

On Wed, Mar 6, 2013 at 8:56 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I tried to compile the latest wxlua and ran into compilation errors
> (both on OSX and Windows). I also tried with rev 163 (before Lua 5.2
> changes) and compiled it successfully (also on both platforms). The
> error messages I got are at the bottom of the email.
>
> Tangentially related; would it be possible to expose
> wxstc.wxStyledTextCtrl.GetLibraryVersionInfo in the API? I'd like to
> show Scintilla version number in the About screen.
>
> While we are on the topic of building wxlua, is it possible to provide
> a parameter for configure to disable building of all
> executables/applications and also disable building of debug/socket
> libraries (which I don't need)? I regularly rebuild from source and
> this would noticeably speed up the process (I only need
> wx.dll/dylib/so). Thank you.
>
> Paul.
>
> --Windows (MinGW)--
>
> Linking CXX shared library ../../bin/MinSizeRel/libwx.dll
> Creating library file:
> ../../lib/MinSizeRel/libwx.dll.aCMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x297):
> undefined reference to `wxLuaBinding_wxbase_init()'
> CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x29c):
> undefined reference to `wxLuaBinding_wxcore_init()'
> CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2a1):
> undefined reference to `wxLuaBinding_wxadv_init()'
> CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2a6):
> undefined reference to `wxLuaBinding_wxnet_init()'
> CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2ab):
> undefined reference to `wxLuaBinding_wxhtml_init()'
> CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2b0):
> undefined reference to `wxLuaBinding_wxaui_init()'
> CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2b5):
> undefined reference to `wxLuaBinding_wxstc_init()'
> CMakeFiles/wxLuaModule.dir/objects.a(wxluadebugger_bind.cpp.obj):wxluadebugger_bind.cpp:(.text+0x40c):
> undefined reference to `wxluatype_wxWindow'
> CMakeFiles/wxLuaModule.dir/objects.a(wxluadebugger_bind.cpp.obj):wxluadebugger_bind.cpp:(.data+0x5e4):
> undefined reference to `wxluatype_wxWindow
> '
> collect2: ld returned 1 exit status
> make[2]: *** [bin/MinSizeRel/libwx.dll] Error 1
> make[1]: *** [modules/luamodule/CMakeFiles/wxLuaModule.dir/all] Error 2
> make: *** [all] Error 2
> Error: failed to build wxLua
>
> --OSX--
>
> Linking CXX shared library ../../lib/MinSizeRel/libwx.dylib
> Undefined symbols for architecture i386:
>   "wxLuaBinding_wxbase_init()", referenced from:
>       _luaopen_wx in luamodule.cpp.o
>   "wxLuaBinding_wxcore_init()", referenced from:
>       _luaopen_wx in luamodule.cpp.o
>   "wxLuaBinding_wxadv_init()", referenced from:
>       _luaopen_wx in luamodule.cpp.o
>   "wxLuaBinding_wxnet_init()", referenced from:
>       _luaopen_wx in luamodule.cpp.o
>   "wxLuaBinding_wxhtml_init()", referenced from:
>       _luaopen_wx in luamodule.cpp.o
>   "wxLuaBinding_wxaui_init()", referenced from:
>       _luaopen_wx in luamodule.cpp.o
>   "wxLuaBinding_wxstc_init()", referenced from:
>       _luaopen_wx in luamodule.cpp.o
>   "_wxluatype_wxWindow", referenced from:
>       s_wxluatypeArray_wxLua_wxLuaDebuggerServer_DisplayStackDialog
>    in wxluadebugger_bind.cpp.o
>       wxLua_wxLuaDebuggerServer_DisplayStackDialog(lua_State*)      in
> wxluadebugger_bind.cpp.o
>      (maybe you meant: _p_wxluatype_wxWindow)
> ld: symbol(s) not found for architecture i386
> collect2: ld returned 1 exit status
> make[2]: *** [lib/MinSizeRel/libwx.dylib] Error 1
> make[1]: *** [modules/luamodule/CMakeFiles/wxLuaModule.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs....
> make: *** [all] Error 2
> Error: failed to build wxLua

[wxlua-users] Compilation errors with latest wxlua (2.8.12.3; rev 165)

[Paul K <pau...@ya...>]

Hi John,

I tried to compile the latest wxlua and ran into compilation errors
(both on OSX and Windows). I also tried with rev 163 (before Lua 5.2
changes) and compiled it successfully (also on both platforms). The
error messages I got are at the bottom of the email.

Tangentially related; would it be possible to expose
wxstc.wxStyledTextCtrl.GetLibraryVersionInfo in the API? I'd like to
show Scintilla version number in the About screen.

While we are on the topic of building wxlua, is it possible to provide
a parameter for configure to disable building of all
executables/applications and also disable building of debug/socket
libraries (which I don't need)? I regularly rebuild from source and
this would noticeably speed up the process (I only need
wx.dll/dylib/so). Thank you.

Paul.

--Windows (MinGW)--

Linking CXX shared library ../../bin/MinSizeRel/libwx.dll
Creating library file:
../../lib/MinSizeRel/libwx.dll.aCMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x297):
undefined reference to `wxLuaBinding_wxbase_init()'
CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x29c):
undefined reference to `wxLuaBinding_wxcore_init()'
CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2a1):
undefined reference to `wxLuaBinding_wxadv_init()'
CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2a6):
undefined reference to `wxLuaBinding_wxnet_init()'
CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2ab):
undefined reference to `wxLuaBinding_wxhtml_init()'
CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2b0):
undefined reference to `wxLuaBinding_wxaui_init()'
CMakeFiles/wxLuaModule.dir/objects.a(luamodule.cpp.obj):luamodule.cpp:(.text+0x2b5):
undefined reference to `wxLuaBinding_wxstc_init()'
CMakeFiles/wxLuaModule.dir/objects.a(wxluadebugger_bind.cpp.obj):wxluadebugger_bind.cpp:(.text+0x40c):
undefined reference to `wxluatype_wxWindow'
CMakeFiles/wxLuaModule.dir/objects.a(wxluadebugger_bind.cpp.obj):wxluadebugger_bind.cpp:(.data+0x5e4):
undefined reference to `wxluatype_wxWindow
'
collect2: ld returned 1 exit status
make[2]: *** [bin/MinSizeRel/libwx.dll] Error 1
make[1]: *** [modules/luamodule/CMakeFiles/wxLuaModule.dir/all] Error 2
make: *** [all] Error 2
Error: failed to build wxLua

--OSX--

Linking CXX shared library ../../lib/MinSizeRel/libwx.dylib
Undefined symbols for architecture i386:
  "wxLuaBinding_wxbase_init()", referenced from:
      _luaopen_wx in luamodule.cpp.o
  "wxLuaBinding_wxcore_init()", referenced from:
      _luaopen_wx in luamodule.cpp.o
  "wxLuaBinding_wxadv_init()", referenced from:
      _luaopen_wx in luamodule.cpp.o
  "wxLuaBinding_wxnet_init()", referenced from:
      _luaopen_wx in luamodule.cpp.o
  "wxLuaBinding_wxhtml_init()", referenced from:
      _luaopen_wx in luamodule.cpp.o
  "wxLuaBinding_wxaui_init()", referenced from:
      _luaopen_wx in luamodule.cpp.o
  "wxLuaBinding_wxstc_init()", referenced from:
      _luaopen_wx in luamodule.cpp.o
  "_wxluatype_wxWindow", referenced from:
      s_wxluatypeArray_wxLua_wxLuaDebuggerServer_DisplayStackDialog
   in wxluadebugger_bind.cpp.o
      wxLua_wxLuaDebuggerServer_DisplayStackDialog(lua_State*)      in
wxluadebugger_bind.cpp.o
     (maybe you meant: _p_wxluatype_wxWindow)
ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status
make[2]: *** [lib/MinSizeRel/libwx.dylib] Error 1
make[1]: *** [modules/luamodule/CMakeFiles/wxLuaModule.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [all] Error 2
Error: failed to build wxLua

Re: [wxlua-users] wxFile

[Andre A. <ar...@ki...>]

> 
> Never notice this before
> 
> wxFile:Read(unsigned int count) returns a count.
> 
> How could who read the data.
> 
> This is odd obviously other methods are available.
> 

Should have tried a bit harder
 length, data = fileIn:Read(length)
 which is exactly what you want.
Andre

[wxlua-users] wxFile

[Andre A. <ar...@ki...>]

Never notice this before

wxFile:Read(unsigned int count) returns a count.

How could who read the data.

This is odd obviously other methods are available.

Andre

Re: [wxlua-users] Patch to wxlua to allow setting event handlers from coroutines

[Paul K <pau...@ya...>]

Hi John,

> To be sure, for debugging you create a coroutine then run the whole
> app in that coroutine state using debug hooks and yields to pause it?

This is exactly correct. Debug hook is registered to that coroutine,
but the debugger itself runs in yet another coroutine.

> What happens when a wxLua app is paused at a breakpoint and an event
> handler is called? Don't you get an error saying something about
> resuming a suspended coroutine or is the coroutine not yielded to
> pause the execution?

No; never got this message. The application itself is suspended, so it
can't really receive any messages. In fact, I actually *do* set event
handlers from the debug coroutine while it's suspended to minimize
"busyness" of the application (it's around lines 540-550 in
mobdebug.lua), but I have never seen any crashes related to that.

> I would also like to understand what the advantages of the coroutine
> method of debugging are over the wxLua blocking socket method?

I don't use wxlua sockets because the debugger uses exactly the same
mechanism running wxlua or any other lua application.

> In any case, normally anyone who tries to connect an event handler in
> a coroutine will crash their program in a very hard to debug way,
> especially if the coroutine they installed the callback in gets
> garbage collected.

It seems like this has been working fine for me for as long as the
code that handles the callback is in the same coroutine as the code
that sets it (which is my case).

What I also do to support live coding is to call "error" from the
debug hook in the main coroutine, which allows me to reload the code
while the application is running. This is when it crashes with the
current wxlua code and doesn't crash with the patch. It seems like the
line I commented out in the patch does something to the Lua state that
causes the crash.

> I would like to find a way to have it work for your case, but also not
> frustrate new wxLua users who might imagine that they can somehow
> create a "threaded" GUI app using coroutines, not understanding that
> events are already sent asynchronously as has happened in the past.
>
> Maybe it is enough to simply have a strongly worded comment in the
> documentation, but please explain a little about your debugging
> methods.

"A strongly worded comment" would definitely make sense. Please let me
know if you'd need any additional details or a small example that
demonstrates the issue.

Paul.

On Wed, Feb 27, 2013 at 9:39 PM, John Labenski <jla...@gm...> wrote:
> On Wed, Feb 27, 2013 at 6:26 PM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>> I'd like to resurrect this discussion as the issue hasn't been fully
>> put to bed and as I'm preparing for 2.9 wxwidgets upgrade I'd like to
>> figure out whether I still need to patch wxlua to support my use case.
>
>> I ended up patching wxlua and removing that one line that was added in
>> the revision 104 (line 103 in this diff:
>> http://wxlua.svn.sourceforge.net/viewvc/wxlua/trunk/wxLua/modules/wxlua/src/wxlcallb.cpp?r1=100&r2=104&pathrev=104).
>
> To be sure, for debugging you create a coroutine then run the whole
> app in that coroutine state using debug hooks and yields to pause it?
> What happens when a wxLua app is paused at a breakpoint and an event
> handler is called? Don't you get an error saying something about
> resuming a suspended coroutine or is the coroutine not yielded to
> pause the execution?
>
> I would also like to understand what the advantages of the coroutine
> method of debugging are over the wxLua blocking socket method?
>
> In any case, normally anyone who tries to connect an event handler in
> a coroutine will crash their program in a very hard to debug way,
> especially if the coroutine they installed the callback in gets
> garbage collected.
>
> I would like to find a way to have it work for your case, but also not
> frustrate new wxLua users who might imagine that they can somehow
> create a "threaded" GUI app using coroutines, not understanding that
> events are already sent asynchronously as has happened in the past.
>
> Maybe it is enough to simply have a strongly worded comment in the
> documentation, but please explain a little about your debugging
> methods.
>
> Regards,
>     John
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Patch to wxlua to allow setting event handlers from coroutines

[John L. <jla...@gm...>]

On Wed, Feb 27, 2013 at 6:26 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I'd like to resurrect this discussion as the issue hasn't been fully
> put to bed and as I'm preparing for 2.9 wxwidgets upgrade I'd like to
> figure out whether I still need to patch wxlua to support my use case.

> I ended up patching wxlua and removing that one line that was added in
> the revision 104 (line 103 in this diff:
> http://wxlua.svn.sourceforge.net/viewvc/wxlua/trunk/wxLua/modules/wxlua/src/wxlcallb.cpp?r1=100&r2=104&pathrev=104).

To be sure, for debugging you create a coroutine then run the whole
app in that coroutine state using debug hooks and yields to pause it?
What happens when a wxLua app is paused at a breakpoint and an event
handler is called? Don't you get an error saying something about
resuming a suspended coroutine or is the coroutine not yielded to
pause the execution?

I would also like to understand what the advantages of the coroutine
method of debugging are over the wxLua blocking socket method?

In any case, normally anyone who tries to connect an event handler in
a coroutine will crash their program in a very hard to debug way,
especially if the coroutine they installed the callback in gets
garbage collected.

I would like to find a way to have it work for your case, but also not
frustrate new wxLua users who might imagine that they can somehow
create a "threaded" GUI app using coroutines, not understanding that
events are already sent asynchronously as has happened in the past.

Maybe it is enough to simply have a strongly worded comment in the
documentation, but please explain a little about your debugging
methods.

Regards,
    John

Re: [wxlua-users] wxLua apperantly not giving the window frame to functions defined in frame:Connect()

[John L. <jla...@gm...>]

On Wed, Feb 27, 2013 at 7:29 PM, Mitchell Monahan
<soc...@gm...> wrote:
> Hello, when I use the code that is on http://wxlua.sourceforge.com (here is
> the code in case you forgot:)
>
> frame = wx.wxFrame(wx.NULL, wx.wxID_ANY, "wxLua Minimal Demo",
>                    wx.wxDefaultPosition, wx.wxSize(450, 450),
>                    wx.wxDEFAULT_FRAME_STYLE)
...
> --------------------------------------
> I  get an error when I go to help --> about(in it's own window):
> Lua: Error while running chunk
> E:\lua\wxLua\init.lua:38: wxLua: expected a 'wxWindow'
> for parameter 4, but got a 'nil'.
> Function called: 'wxMessageBox(string,string,number,nil)'
> 01. wxMessageBox([string,string,number,wxWindow,number,number])
> stack traceback:
>         [C]: in function 'wxMessageBox'
>         E:\lua\wxLua\init.lua:38: in function
> <E:\lua\wxLua\init.lua:37>
>        [C]: in function 'MainLoop'
>         C:\Program Files (x86)\Lua\5.1\lExecuter.wlua:799: in
> function '__main'
>         C:\Program Files (x86)\Lua\5.1\lExecuter.wlua:802: in main
> chunk
>         [C]: ?

I don't understand how/why the frame variable is nil in the callback?

> Yes, I did start this in the lexecutor that was included with Lua for
> Windows, and I am also using the wxLua that was included with Lua for
> Windows.

I don't know about lexecutor or much about Lua for Windows.

The code runs fine using the official wxLua binaries here:
http://sourceforge.net/projects/wxlua/files/wxlua/

Regards,
    John

[wxlua-users] wxLua apperantly not giving the window frame to functions defined in frame:Connect()

[Mitchell M. <soc...@gm...>]

Hello, when I use the code that is on http://wxlua.sourceforge.com (here is
the code in case you forgot:)

frame = wx.wxFrame(wx.NULL, wx.wxID_ANY, "wxLua Minimal Demo",
                   wx.wxDefaultPosition, wx.wxSize(450, 450),
                   wx.wxDEFAULT_FRAME_STYLE)

-- create a simple file menu
local fileMenu = wx.wxMenu()
fileMenu:Append(wx.wxID_EXIT, "E&xit", "Quit the program")
-- create a simple help menu
local helpMenu = wx.wxMenu()
helpMenu:Append(wx.wxID_ABOUT, "&About",
                "About the wxLua Minimal Application")

-- create a menu bar and append the file and help menus
local menuBar = wx.wxMenuBar()
menuBar:Append(fileMenu, "&File")
menuBar:Append(helpMenu, "&Help")
-- attach the menu bar into the frame
frame:SetMenuBar(menuBar)

-- create a simple status bar
frame:CreateStatusBar(1)
frame:SetStatusText("Welcome to wxLua.")

-- connect the selection event of the exit menu item to an
-- event handler that closes the window
frame:Connect(wx.wxID_EXIT, wx.wxEVT_COMMAND_MENU_SELECTED,
              function (event) frame:Close(true) end )
-- connect the selection event of the about menu item
frame:Connect(wx.wxID_ABOUT, wx.wxEVT_COMMAND_MENU_SELECTED,
        function (event)
            wx.wxMessageBox('This is the "About" dialog of the Minimal
wxLua sample.',
                            "About wxLua",
                            wx.wxOK + wx.wxICON_INFORMATION,
                            frame)
        end )

-- finally, show the frame window
frame:Show(true)



--------------------------------------
I  get an error when I go to help --> about(in it's own window):
Lua: Error while running chunk
E:\lua\wxLua\init.lua:38: wxLua: expected a 'wxWindow'
for parameter 4, but got a 'nil'.
Function called: 'wxMessageBox(string,string,number,nil)'
01. wxMessageBox([string,string,number,wxWindow,number,number])
stack traceback:
        [C]: in function 'wxMessageBox'
        E:\lua\wxLua\init.lua:38: in function
<E:\lua\wxLua\init.lua:37>
       [C]: in function 'MainLoop'
        C:\Program Files (x86)\Lua\5.1\lExecuter.wlua:799: in
function '__main'
        C:\Program Files (x86)\Lua\5.1\lExecuter.wlua:802: in main
chunk
        [C]: ?



Yes, I did start this in the lexecutor that was included with Lua for
Windows, and I am also using the wxLua that was included with Lua for
Windows.

[wxlua-users] Patch to wxlua to allow setting event handlers from coroutines

[Paul K <pau...@ya...>]

Hi John,

I'd like to resurrect this discussion as the issue hasn't been fully
put to bed and as I'm preparing for 2.9 wxwidgets upgrade I'd like to
figure out whether I still need to patch wxlua to support my use case.

It all started here:
http://www.mail-archive.com/wxl...@li.../msg03002.html.
Basically, you made a change long time ago (I think when the code was
still in CVS) to avoid setting event handlers from coroutines, which
broke some code that was working before (at least for me). We
discussed this and you made a slight change
(http://wxlua.svn.sourceforge.net/viewvc/wxlua?view=revision&revision=104),
which made things better, but it didn't fully address the issue and
some of the code I need still doesn't run.

I ended up patching wxlua and removing that one line that was added in
the revision 104 (line 103 in this diff:
http://wxlua.svn.sourceforge.net/viewvc/wxlua/trunk/wxLua/modules/wxlua/src/wxlcallb.cpp?r1=100&r2=104&pathrev=104).
I can assure you that I've been running ZeroBrane Studio on Windows,
OSX, and Linux for 6+ months with that fix and have not seen or
received any problem related to that change. The problem *with* the
current code is easy to reproduce: take wx.dll compiled with the
current (not patched) version of wxlua and put it in bin/ folder of
ZBS. Try to run any of the turtle drawing examples that come with ZBS
using live coding (Project | Run as Scratchpad) and the Lua process
will crash. Comment out that line and it be executed correctly.

I'm fine with continuing applying this patch and using my own version,
but since there are people that build wxlua from the source (mostly on
Linux), it would be best to come to some agreement on this change. My
preference would be to remove it (note that reverting r104 is not
enough as it re-introduces a different issue). If you continue to
disagree, that's fine, but I'll then document the patch and update my
build scripts to apply it automatically. Thank you.

Paul.