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

[Francesco M. <f18...@ya...>]

Hi,

klaas.holwerda ha scritto:
> Francesco Montorsi wrote:
> 
>>
>> Thus I suggest to stick with wx rules for both linux and win32 libnames.
> 
> 
> Fine with me, but will the next become?
> 
> wxmsw[wxversion without dots][u][d]_[libname].lib
> 
> wxl_msw_wxluaversion without dots][u][d]_[libname].lib
> 
> As you see wxl_ is i think better then wxmsw.
> It must be clear we are taliking wxLua.
maybe you're right; but I would then use (for win32):

     wxlua_msw[wxversion without dots][u][d]_[libname].lib



>> 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.
>>
>> Do you agree to use this versioning rule ?
> 
> 
> I think this is confusing, since those numbers normally mean something 
> else.
what do they mean ?

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.
 > At least that was the goal of the *.i files.
Yes but say that after releasing wxLua 2.6.2 we found that there is a 
small bug in wrapper generator which needs to be fixed.
How do we call the next release (still targeted for wx2.6.2) ?
Using 4th digit there's no such problem: the new version would be 2.6.2.2



> I would keep the versions of wxLua and wxArt2D independent from wxWidgets.
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.


> Also i am thinking in the future wxWidgets might get to the level that 
> wxCode stuff will be moduler/pluggable.
I hope it, too :)


> In that case we certainly not have the situation that each module goes 
> in the same pase with wxWidgets.
> So better decide a solution that works always in al  situations, which 
> is what i think keep the version seperated.
3d party code (like contribs or wxCode components) should always be 
checked by wxLua configure script or CPP code for its version.
IMO this is an independent issue from the type of versioning we choose 
for wxLua...

Francesco