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

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

Hi,

John Labenski ha scritto:
> On 2/1/06, Francesco Montorsi <f18...@ya...> wrote:
>>>>>> 1) STC (more generically CONTRIB) problem
>>> I tried to disconnect wxSTC from the wxWidgets wrappers last night. I
>>> think it will take some doing however. Since they'll share the same
>>> lua namespace, they don't have to, but I would like the generic
>>> flexibility of putting multiple wrappers into the same namespace, any
>>> additional wrappers overwrite earlier ones. I have to do some reading
>>> up on how to add more to lua in C. I hope it won't be too hard.
>> ok, let me know if I can help in some way...
> 
> I believe I got it to work. It currently generates a library that you
> link to in addition to the wxbind library.  You can now add any
> arbitrary number of libraries to any lua namespace.
very nice !


> So, I guess we need to add some more dirs, let me know what you think
> about these.
> 
> wxLua/bindings/wxstc/stc.i
>    or wxLua/bindings/wxwidgets/contrib/stc/stc.i  (maybe better)
there is the possibility that some day wx contrib stuff will be moved in 
wxCode or somewhere else... so I would use wxLua/bindings/wxstc/stc.i 
rather than wxLua/bindings/wxwidgets/contrib/stc/stc.i ...


> wxLua/modules/wxbindstc/  - same as wxbind
>    * I think this has to be in it's own dir at the same level as wxbind
ok



>>>>>> 2) wxLUA_USE_wxCriticalSectionLocker is not defined - maybe it should
>>>>>> be added to wxluasetup.h
>>>>> looking to wxluasetup.h I've found that there is a heading which says
>>>>> that it's generated by "utils/get_luasetup"; however I couldn't find
>>>>> that util.
>>>>> Is that true or that's an old comment?
>>> That is a simple little utility, basicly just grep wxLUA_USE* for the
>>> .i files. I will try to find it if I can.
>> it would be nice to have it in CVS...
> 
> I found it, it's an awk script that was written before we used the
> wxWidgets %if wxUSE_XXX in the bindings so it's pretty dumb and not
> very useful anymore.
> 
> #=======================
> # read in all the .i files, look for "%if" print them out
> 
> grep "%if" *.i | awk 'BEGIN {print("// Automatically generated by
> utils/get_luasetup edit as necessary."); \
>                              print(""); \
>                              print("#ifndef __WXLUA_SETUP__");
>                              print("#define __WXLUA_SETUP__");
>                              print("") } \
>                { len = length($2); printf("#define %s",$2); for
> (i=0;i<40-len;i++) { printf(" ") }; print("1") } \
>                END { print(""); print("#endif // __WXLUA_SETUP__") }'
> #=======================
No problem for me if we decide to maintain wxluasetup.h by hand.
In that case I will add wxLUA_USE_wxCriticalSectionLocker to it, ok ?



> 
>>>>> 7) can I start to connect the options WXLUASETUP_DIR and
>>>>> WXLUABINDLIB_DIR to the build system ?
>>>> Before starting this work, I need to know exactly how they must work ;)
>>>>
>>>> If I'm right, they should be used not to *modify* the build of the
>>>> wxbind module of wxLua (which should always use the
>>>> modules/wxbind/src/wxluasetup.h header and should always go in the lib/
>>>> folder) but rather to *create* a new library, built from same sources of
>>>> wxbind module, which would be created in the WXLUABINDLIB_DIR folder and
>>>> which would use the wxluasetup.h found in the WXLUASETUP_DIR path.
>>>> Is it right ?
>>>
>>> I would be nice to be able to build the wxbind lib for different
>>> wxluasetup.h files, one lib for the wxLua app and others for your
>>> programs that use wxLua as a library. Sorry, I didn't follow this too
>>> closely.
>> Klaas, IIRC you would use these options... my description above describe
>> the wanted behaviour correctly, or there is something else which needs
>> to be done ?
> 
> These are things that you can use with configure?
yes, there will be some options like --enable-custom-bindlib=path and 
--with-custom-wxluasetup=path  to enable the build of this additional lib.


> How would you make
> it so that you can build wxbind for the apps/wxlua and a different one
> for external programs. Do you have to run configure between building
> each of them?
No, that's not required. I'll just add another wxLua module which is 
enabled only when WXLUABINDLIB_DIR!='' and which includes the 
WXLUASETUP_DIR instead of the dir which contains the std wxluasetup.h.

Francesco