Unfortunately they're busted, but hopefully only slightly. Everything
builds properly except for a hundred or so errors about undeclared
identifiers, but see #1 below.
1) genwxbind doesn't handle %enums properly, it needs to write
enumType::enumName so it can handle enums in a class. Unfortunately I
cannot make any sense of genwxbind so I've left it with two "FIXME"
lines, one where the enumType is known and one where I want to use it.
2) It doesn't seem to write out the %builtin functions, I can't figure
this out at all.
Ray could you take a look at this, I've only modified genwxbind ever
so slightly.
See wxLua/bindings/genwxbind.bat to see how to generate new bindings.
You can easily test them by using wxLua/apps/wxlua/src/wxLua_wx26.dsw=20
which will build everything. (I've not updated the makefiles)
I've decided to put the output of the wrappers into
wxLua/modules/wxbind/include and src
this way the code necessary for virtual functions can be built right
with it, I've called those wxlprint and wxlhtmlwin (used to be
wxLuaPrinting, wxLuaHtmlWin).
I think the only viable option for personalized bindings to link to is
to have people's projects compile the wrapper cpp files into their own
lib using their own luasetup.h file. We should have a generic build
file to build all of them as is, this is what wxlua will use. I've
added my wxluabind_wx26.dsp file in modules/wxbind/src/ to do this
already, but eventually we can make bakefile do this.
I've not uploaded the wrapper *.cpp files yet since they don't work,
are huge, and can be easily generated, but if you run the code in
genwxbind.bat you'll get them.
I hope this makes sense, this is our last step and once apps/wxlua
compiles properly anyone is free to do as they please since I think
we've got the best of all the various wxLuas now. Just remember, test
the wxlua app against any change you make and fix it up if necessary.
Regards,
John Labenski
|
