From: klaas.holwerda <kho...@xs...> - 2006-01-27 17:03:00
|
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. Same i would say: a2d_msw etc. > > > > 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. 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. I would keep the versions of wxLua and wxArt2D independent from wxWidgets. It should be in the install.html and configure etc. ( there are/will be more dependencies, so where would one stop??) Also i am thinking in the future wxWidgets might get to the level that wxCode stuff will be moduler/pluggable. 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. regards, Klaas |