Re: [Wxlua-users] #define WXWIN_COMPATIBILITY_2_4 1

[John L. <jla...@gm...>]

On 7/29/05, k. holwerda <kla...@nl...> wrote:
> I am still using the/my old wxLua  inside wxArt2D. Hoping for wxLua CVS
> to become usable, but maybe it already is?

It currently doen't wrap "enums" and "builtin" functions in the cpp
wrapper files. It does compile and work otherwise. I cannot figure it
out, but gave up since we're going to get some new wrappers anyway.

> Referring to non use of *.i files or at least other ways to generate
> them using Ray his ideas.
>=20
> What impact will all that have on the current structure? Will the *.i
> files stay? Or will it be  a new aproach ?

I don't know, hopefully Ray's reading this and can comment, maybe he
has something, even if it's half done that we can use to bring wxLua
back to a working state and the rest of us can pitch in to polish it
off.

I made some suggestions about making the .i files look more like c++
so that making your own would be a simple matter of taking a header
file and just removing the stuff you don't want. You'd then be able to
run a diff program on the .i and the original header to compare. But,
I don't know what other's thought of it. Basicly, replace the
%endclass, %endenum by surrounding them using {} like in c++.

> The thing is, i will need to have Cmake files in there ( or my own
> wxart2d  copy ) for wxArt2D.

I'd like for you to use wxLua itself (if that's what you mean by "my
own wxart2d copy), just direct people to download it someplace
relative to your wxArt2D. That way we avoid the splintering we had
before. Remixing together code from various places is error prone and
laborous. Hopefully it'll work soon...

I think that we can easily have cmake files too, right? Cmake IIRC
generates the build files on the fly after you download the source and
run cmake. If the files it generates are given names that won't clash
with the files in CVS it'll be easy to have both of them together. You
could put them in the build dir or if there will be a few of them in
build/cmake right?

> In any case, i would like to know is the current version can be compiled
> with wx261, and if that is with
>=20
> #define WXWIN_COMPATIBILITY_2_4 1
> i think it should be:
> #define WXWIN_COMPATIBILITY_2_4 0
> as setup.h recomments.

I currently use it with COMPAT_2_4 =3D 1, I haven't tested it without
it, but Ray has made the wrapper files generate #if wxCHECK_VER around
different functions so that it should compile either way. If not, it's
just a matter of fixing the problems in the .i files and regenerating
the wrappers. Before we change anything we really have to wait for
Ray, since doing anything to the wrappers will be a waste of time
since I think they'll be replaced.

You're right in that we probably should focus on 2.6 since when we're
done 2.4 will be pretty ancient (it already is to some extent).

> And how does one tell wxLuaWrap.lua, does it really read the setup.h?

It tries to find your wxWidgets setup.h file the best it can and sets
values from it. See bindings/wxluawrap.lua and at the top there is
code to look for "wxSetup_h" if it's nil. You can also specify
wxSetup_h before you run wxluawrap.lua if the code fails for some
reason.

I hope this helps, I hope we can get going again...
    John Labenski