> I presume KiCad 6 will be released after wx 3.2 is released (stated by their > releases page as 'hopefully in September 2021’).
No, we won’t be waiting on wxWidgets to release. (I suspect their date is optimistic.) Cheers, Jeff. > On 29 Jun 2021, at 14:14, Ruth Ivimey-Cook <r...@ivimey.org> wrote: > > > On 29/06/2021 12:39, Jeff Young wrote: >> Windows and Mac are single platforms, so the KiCad team builds those. We >> also build the Linux flatpak, which is statically linked (to 3.1). > > Except that the flatpak I installed yesterday is of version 5.1.10 and that > one at least is linked to wx 3.0. If there is another version of kicad > available as a flatpak I am unaware of it. > > I need (because of the new lib formats) a 5.99 linked to wx 3.1. > > I did try to self-compile, but the DRI linkage stuff broke. I still don't > know why. > > Could the team consider making a flatpak of kicad-nightly available, linked > to wx 3.1.x (not necessarily latest), and document on the relevant page how > to install and use it for those like me who are unused to the flatpak? > > >> It’s all the Linux distros that we can’t do much about. >> >>> I'm not saying it's ideal to use the possibly broken -dev version of wx, >>> but IMO it is worse to use the actually broken "stable" version of it >> He he… yeah, that about sums up the state of wxWidgets. ;) > > I presume KiCad 6 will be released after wx 3.2 is released (stated by their > releases page as 'hopefully in September 2021'). > > I personally feel the project would be much better off using Qt because it's > a far better supported and designed framework, but I guess that's a question > for another era! > > Ruth > > >> >> Cheers, >> Jeff. >> >> >>> On 29 Jun 2021, at 11:44, Ruth Ivimey-Cook <r...@ivimey.org> wrote: >>> >>> >>>> wxwidget 3.1 is the development version for the upcoming stable version >>>> 3.2 which possible breaks the API/ABI with every new version that is >>>> getting released. That makes this software breaking other software too >>>> often and by this unfit to get introduced into Debian unstable, it >>>> simply make to less sense. >>> Despite this, both the Windows and MacOS builds are using wx 3.1, somehow >>> or other.... >>> >>> I'm not saying it's ideal to use the possibly broken -dev version of wx, >>> but IMO it is worse to use the actually broken "stable" version of it. >>> >>> If needed, select a good-enough build of wx3.1 from the repo I referenced >>> and link kicad statically to it, so there can be no pollution of other apps. >>> >>> Ruth >>> >>> -- >>> >>> Tel: 01223 414180 >>> Blog: http://www.ivimey.org/blog >>> LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/ >>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp > > -- > Software Manager & Engineer > Tel: 01223 414180 > Blog: http://www.ivimey.org/blog <http://www.ivimey.org/blog> > LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/ > <http://uk.linkedin.com/in/ruthivimeycook/>
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
