Re: [Wxlua-users] Re: wxLua and wxWidgets versions (was Re: target names)

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

> >> 2) We are going to put wxversion numbers somewhere in library names
> >> in any case. However I'd like to discuss a couple of things about
> >> version.
> >>
> >> I see wxPython works this way: for wx2.6.2 there is wxPython2.6.2.1,
> >> wxPython2.6.1.2, etc...
> >> This is probably the best thing to do as it will be simpler for users
> >> to  understand which release of wxPython targets which release of
> >> wxWidgets but still lets wxPython developers to make other releases
> >> still targeted  to wx 2.6.2 using the fourth digit.
...
>
> AFAIK the fourth digit of wxPython indicates the version of wxPython
> wrappers while the first 3 indicate the version of wxWidgets which must
> be used with those wrappers.
>
> > Also i do not think that wxLuaversionX will be different for different
> > version of wxWidgets.
...
>
> > I would keep the versions of wxLua and wxArt2D independent from wxWidge=
ts.
> I agree for wxArt2d but not for wxLua. wxLua is a wrapper and I'd take
> inspiration for such things from the well-known wxPython package.

I agree that we should use the 2.6.2.X versioning for wxLua. The .i
files do try to maintain backwards compatibility as they move
forwards, but it's a drag trying to keep them working for 2.4 and so
by naming wxLua2.6.2.x we're suggesting to people that this is what
version wxLua is targeted for. For example the MSVC dsp files use 26
in them. People are welcome to hack away to make it work for other
versions and perhaps it will, but the numbering implies that it should
work out of the box for that version of wxWidgets.

Regards,
    John Labenski