Re: luasetup.h and wxLua build system (was Re: [Wxlua-users] wxLua Compiles and works in Linux)

[klaas.holwerda <kho...@xs...>]

Francesco Montorsi wrote:

>
>
> So I don't know if it's better to limit project files to the default 
> luasetup.h or to force them to look for the WXLUASETUP_DIR and 
> WXBIND_TARGET_LIBDIR env vars...

The user already needs to set WXWIN, so one more or less will not hurt.
But there is i think more to it.
One job to do is to generate the custom made wxLua version for an 
external project. But that same project will have its own make files or 
project files.
In wxArt2D for example we will not limit the wxLua, only extend it with 
extra bindings. So i assume we will use something like a wxlua-config to 
get the information about where wxLua is etc. and on windows the envvar 
WXLUA will be used to find it.
So wxArt2D has its own module with *.i files, leading to an extra 
library  with wxLua art2d  bindings.  To conclude, this  is part of its 
own project files. No need for a dedicated project file from wxLua itself.
If however one only wants to link in a partly wxLua ( which can be the 
case for certain wxArt2D applications, where lua is used only for a 
command interpreter, and nothing fancy ), we get to the situation that 
John explained.
And again here i think it should be the job of the wxart2d\project/make 
files to generate this partly wxLua by taking only parts of *.i , having 
a customized luasetup.h in wxArt2D.

In short i think we need a system for external wxLua project ( app or 
lib ), in which on can take the complete wxLua or a partly binding and 
at the same time extend it with extra bindings, and that alltogether 
could best go into a library which belongs to that external project itself.
I would non be suprized that in some far future there will be a 
lua_art2dsetup.h next to the luasetup.h, making it able to choose 
between  the various wxArt2d modules wrapped into lua.

So i wonder if a VC project file is really helping in such a situation.
But of course it will be good to help a user on his way, since wxLua/lua 
is often really meant to be used with/inside other applications to 
extend them with scripting.  We must make something which makes this 
easy to do.
Maybe we must generate some sort of template makefile/project files, or 
even better bakefile template itself, within wxLua, which makes this 
easy to include in our own projects?
 
John would you be able to explain how you picture the use of  
genwxbind.bat in an external project ?  e.g. should one extend wx.rules?
In that case, one will need a copy of that file in its own projects i 
think, but will it still work from  there? Did you already use wxLua 
like it is now in one of your own project (which has its own bindings ). 
How do you do that?

Trying to prepare myself for having the new wxLua used in wxArt2D ;-)

Thanks all,

Klaas