[Wxlua-users] Re: Remaining problems on Linux (Re: wxLua on Linux)

[Francesco M. <f18...@ya...>]

hi,

Francesco Montorsi ha scritto:
> Hi,
>     I think I can update this thread with last two unsolved problems (at 
> least on Unix).
> 
> 
>> 1) STC (more generically CONTRIB) problem
> Now that wxbindstc has been separed from remaining bindings, I think 
> that we can add a new option like USE_WXBINDSTCLIB which allows to 
> enable/disable it, right ?
> 
> Then, when USE_WXBINDSTCLIB=1, wxLuaApp can be built.
> 
> When the configure script (on Unix) detects wxStedit, then also 
> wxLuaEdit can be built. Is this right ?
I have worked on the configure script and added USE_WXBINDSTC option.

Now when the user has not compiled wxSTC, he's kindly warned that he 
needs to that if he wants to compile wxLuaApp and wxLuaEdit, but that he 
can use the --disable-wxbindstc option to skip them.

I've tried to compile & install wxSTC and to compile wxLuaApp but when I 
try to run it I get the error:

frm@genius:~/work/wxLua/gtksud/bin$ ./wxlua
[string "./wxlua"]:374: attempt to call field `wxStyledTextCtrl' (a nil 
value)wxLua: Error while running chunkwxLua: Error while running chunk

previously I thought that this error was because of missing wxStEdit 
control but I've now realized that wxLuaApp doesn't need it and that 
wxStyledTextCtrl is defined in wxSTC.
So, please ignore problem #2 of my previous mail; this is the problem I 
meant: when running wxluaapp, even if you compiled wxSTC and wxBindSTC 
you get the error above (at least on Unix).


The configure script now just misses a check for wxStEdit component, 
which must enable/disable wxLuaEdit, right ?


Francesco