[Wxlua-users] genwxbind.bat

[k. h. <kla...@nl...>]

Hi John,

Trying to make a start here for external programs.
Read in the docs directory building.txt, arrived at the line:

If you wish to use the build files for modlues/wxbind that exist in wxLua
for your own project along with your own wxluasetup.h you need to...

;-))

So let me see.
 
WXLUASETUP_DIR has made it, so setting the include path to my own 
luasetup.h is fine.

What i am puzzled with is the generation of bindings.
Am i right that those binding are now platform and settings independent, 
in can be in principle become part of the wxLua distribution?
Meaning i do not have to generate those in the future and they have no 
relation with my own bindings?
And if i only want part of the wxLua bindings, this is just a matter of  
changing my own luasetup.h and rebuild the wxlua library?

I assume genwxbind.bat can be used for my own wxart2d.rules file.
My wxart2.rules file contains this at the top, but i wonder if this is 
needed?
wxlua_dir =  os.getenv("WXLUA")

But reading this in wx.rules, i get the feeling that i need to change 
more, in order to
get my own binding in the right place, assuming there is no need to have 
them in the same place as the wxWidget bindings.
In other words i will get a seperate library for my own bindings, next 
to the one containing the wxWidget bindings.
Something like:

wxart2d_dir =  os.getenv("WXART2D")


interface_dir     = wxart2d_dir.."/bindings"
output_dir        = wxart2d_dir.."/src"
output_header_dir = wxart2d_dir.."/include"

And in the

interfaceFileList =
{
    wxart2d.i
}

This seems to work, many things are generated, and they contain things 
related to what is in wxart2d.i ;-)

What should i do with the next, should i call it wxart2d? Is that oke/wise?:

hook_namespace       = "wx" 

If i do, does that require something from my site to have both bindings 
active?

Is this more or less the approach you have in mind too?

I think that once we have a working approach, we should add an app which 
uses this approach.
So all users will know how to include and use/extend wxLua in their own 
application.
This is what wx(lua) is all about, so we better make as easy  as  possible.

Thanks for some advice,

Klaas


 




-- 
Unclassified