On further review of the msys2 news page that states: /quote 2020-05-17 - 32-bit MSYS2 no longer actively supported 32-bit mingw-w64 packages are still supported, this is about the POSIX emulation layer, i.e. the runtime, Bash, MinTTY...
After this date, we don't plan on building updated msys-i686 packages nor releasing i686 installers anymore. This is due to increasingly frustrating difficulties with limited 32-bit address space, high penetration of 64-bit systems and Cygwin (our upstream) starting their way to drop 32-bit support as well. /quote It does mention that it is just the environment that is 64 bit only, but not the mingw toolchains, so I don't really think this affects us. Nick On Wed, 5 Aug 2020 at 01:10, Wayne Stambaugh <stambau...@gmail.com> wrote: > On 8/4/20 4:43 PM, Seth Hillbrand wrote: > > > > > > On Tue, Aug 4, 2020 at 4:41 AM Wayne Stambaugh <stambau...@gmail.com > > <mailto:stambau...@gmail.com>> wrote: > > > > On 8/3/20 9:19 PM, Seth Hillbrand wrote: > > > > > > > > > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh > > <stambau...@gmail.com <mailto:stambau...@gmail.com> > > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>> > wrote: > > > > > > I'm not ready to drop 32 bit builds for V6. I still think > > there are > > > enough 32-bit users to warrant supporting it for one more > > release. It's > > > something we can discuss for V7. > > > > > > > > > If we keep 32 bit builds on mingw2, does that mean that we freeze > all > > > packages at their current versions? It might be problematic to > keep > > > different package versions for different architectures. > > > > I'm assuming you mean dependency packages so yes we would continue to > > build 32 bit windows versions using the current package versions. If > > someone figures out how to get wxPhoenix to build, then we could > bump to > > wxWidgets 3.1.x and Python 3.x. > > > > > > Do you envision building 32-bit and 64-bit with different package > versions? > > I hope not but we may have to bite the bullet if we can't get all of the > packaging up to snuff be it msys2 or msvc builds. > > > > > -Seth > > > > > > -- > > KiCad Services Corporation Logo > > Seth Hillbrand > > *Lead Developer* > > +1-530-302-5483 <tel:+12126039372> > > Davis, CA > > www.kipro-pcb.com <https://www.kipro-pcb.com/> i...@kipro-pcb.com > > <mailto:i...@kipro-pcb.com> > > > > _______________________________________________ > 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 >
_______________________________________________ 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
