[Wxlua-users] Custom wxBind library and wxLua

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

Hi,
    thinking to implementation of the WXLUASETUP_DIR and 
WXLUABINDLIB_DIR options, I realized one thing.

I.e. if I want to install app X (from sources) which has its own wxLua 
extensions, then I cannot just compile&install wxLua with a standard 
"./configure && make && make install" (on win32 "cd wxLua/build/msw && 
nmake -fmakefile.vc"): app X requires wxLua's build options to be 
modified (i.e. adding something like WXLUASETUP_DIR=X/luaext 
WXLUABINDLIB_DIR=X/lualib).

Ok, this affects only source builds and it won't be the first case that 
such thing happens. However I think that if that can be avoided, it 
would be a Good Thing.

One way to avoid that could be providing the app X with a way to 
recompile the wxLua's wxbind module with its own wxluasetup.h.
This means that the custom wxbind module would not be generated when 
wxLua is compiled but rather when app X is compiled.

I'm not sure if you had this same idea when you wrote that 
WXLUASETUP_DIR and WXLUABINDLIB_DIR options should not be exposed in the 
configure script :)

Anyway, on Unix, it wouldn't be such difficult to provide to the guest 
app X the required info to recompile wxLua's wxbind module.
It would probably be somewhat more difficult on win32, but probably 
still feasible.


What do you think of this approach ?

Francesco