Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-11-11 Thread Nick Østergaard
Correct, but that is not the case right now. It just means that we should
be able to update MSYS2 packages just fine without trouble on the builder
server.

On Wed, 11 Nov 2020 at 13:30, Mark Roszko  wrote:

> >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.
>
> It does,* just not right now. *The writing is on the wall for 32-bit x86.
> Microsoft officially has marked 32-bit Windows 10 EOL and I believe it's
> being dropped by Microsoft towards the end of next year (no more security
> updates).
> It would be crazy for MSYS2 not to eventually drop the packages themselves
> as well.
>
> On Tue, Nov 10, 2020 at 6:13 PM Nick Østergaard  wrote:
>
>> 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 
>> wrote:
>>
>>> On 8/4/20 4:43 PM, Seth Hillbrand wrote:
>>> >
>>> >
>>> > On Tue, Aug 4, 2020 at 4:41 AM Wayne Stambaugh >> > > wrote:
>>> >
>>> > On 8/3/20 9:19 PM, Seth Hillbrand wrote:
>>> > >
>>> > >
>>> > > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh
>>> > 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‬ 
>>> > Davis, CA
>>> > www.kipro-pcb.com 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
>>
>
>
> --
> Mark
>
___
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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-11-11 Thread Mark Roszko
>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.

It does,* just not right now. *The writing is on the wall for 32-bit x86.
Microsoft officially has marked 32-bit Windows 10 EOL and I believe it's
being dropped by Microsoft towards the end of next year (no more security
updates).
It would be crazy for MSYS2 not to eventually drop the packages themselves
as well.

On Tue, Nov 10, 2020 at 6:13 PM Nick Østergaard  wrote:

> 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  wrote:
>
>> On 8/4/20 4:43 PM, Seth Hillbrand wrote:
>> >
>> >
>> > On Tue, Aug 4, 2020 at 4:41 AM Wayne Stambaugh > > > wrote:
>> >
>> > On 8/3/20 9:19 PM, Seth Hillbrand wrote:
>> > >
>> > >
>> > > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh
>> > 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‬ 
>> > Davis, CA
>> > www.kipro-pcb.com 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
>


-- 
Mark
___
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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-11-10 Thread Nick Østergaard
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  wrote:

> On 8/4/20 4:43 PM, Seth Hillbrand wrote:
> >
> >
> > On Tue, Aug 4, 2020 at 4:41 AM Wayne Stambaugh  > > wrote:
> >
> > On 8/3/20 9:19 PM, Seth Hillbrand wrote:
> > >
> > >
> > > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh
> > 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‬ 
> > Davis, CA
> > www.kipro-pcb.com 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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-17 Thread Christopher Buckley
 Okay, admitting that it's been almost a year since I tuned in to any KiCAD 
dev, this MSYS stuff has got my attention, and I feel compelled to offer my two 
'sense' worth.

I'm disappointed to hear support for 32 bit is going bye-bye, but then I still 
use XP because the vast majority of my CAE/CAD and management software is all 
that old.

So I'm really unhappy with this move, because I'm sure there are a heck of a 
lot of people out there like me that can't afford to spend 5-10K upgrading all 
of their software for 64-bit systems that are being force upon us by 
"advancements" and the market place.

It makes me wonder: "How long until we will be forced in 128-bit systems, and 
must spend another 5-10K updating???"

That being said, my last build of KiCAD was 64-Bit, and it seems KiCAD left the 
32 bit world long ago anyways.

Sadly, I haven't had time to transition to Linux Wine or ReactOS that will 
facilitate my needs.

Driving a truck 12-14 hours a day 6-7 days per week just to survive doesn't 
allow a lot of time to do anything, let alone deal with all my "tech" problems 
that I wish I had time for.

Thanks for keeping me advised, and aware of my progressively sinking boat! LOL!

Cheers all,

C


 On Tuesday, August 4, 2020, 07:39:45 a.m. MDT, Mark Roszko 
 wrote:  
 
 Sigh, almost as bad as QT 5 minors being majors without ever bumping the 5 
because "qt5" is a marketing brand they don't want to replace from the 
commercial standpoint.
On Tue, Aug 4, 2020 at 9:15 AM Ian McInerney  wrote:



On Tue, Aug 4, 2020 at 1:44 PM Mark Roszko  wrote:

Been working on Phoenix, I basically have something working to build, though 
it'll be awhile before I have anything to share.

However, here's the fun part:wxPhoenix 4.1.0 only works with wxWidgets 3.1.4 
and abovewxPhoenix 4.0.7 only works with wxWidgets 3.0.x series
There's a fun gap with 3.1.0-3.1.3 :D Basically even with their fancy pancy 
dynamic generation system for most of their code. They hardcoded things 
specific references with no version checking fallback. Even the 4.0.x series 
may have some compatibility issues with wx 3.0.x depending on mix.
wx is to blame too because wxWidgets 3.1.4 has API changes that really should 
have made it 3.2.  Hell, 3.1.4 appears to have enabled a newer C++ standard and 
the build is broken for MSVC until you patch it with master because Microsoft 
under some newer standard flags clamped down on STL export violations.


wxWidgets follows a "development series" version system - only the even numbers 
are stable releases (e.g. 2.9, 3.0, 3.2, etc.), so anything in 3.1 is going to 
have API/ABI changes happening as they change the API and stabilize it before 
the next stable release (the full list of changes from 3.0 to the current 
3.1/future 3.2 is here 
https://github.com/wxWidgets/wxWidgets/blob/master/docs/changes.txt). This on 
its own isn't a problem, the real problem is that 3.1 has been in development 
for a long time and hasn't been released as a stable release yet. 
I have a PR update to vcpkg to go to 3.1.4 and patch it for 
MSVC.https://github.com/microsoft/vcpkg/pull/12733  


On Tue, Aug 4, 2020 at 7:41 AM Wayne Stambaugh  wrote:

On 8/3/20 9:19 PM, Seth Hillbrand wrote:
> 
> 
> On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh  > 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.

> 
> Obviously, if we successfully move to MSVC, this question is moot.
> 
> -Seth
> 

___
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



-- 
Mark
___
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




-- 
Mark
___
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 : 

Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-04 Thread Wayne Stambaugh
On 8/4/20 4:43 PM, Seth Hillbrand wrote:
> 
> 
> On Tue, Aug 4, 2020 at 4:41 AM Wayne Stambaugh  > wrote:
> 
> On 8/3/20 9:19 PM, Seth Hillbrand wrote:
> >
> >
> > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh
> 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‬ 
> Davis, CA
> www.kipro-pcb.com     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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-04 Thread Seth Hillbrand
On Tue, Aug 4, 2020 at 4:41 AM Wayne Stambaugh  wrote:

> On 8/3/20 9:19 PM, Seth Hillbrand wrote:
> >
> >
> > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh  > > 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?

-Seth


-- 
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483‬ <+12126039372>
Davis, CA
www.kipro-pcb.comi...@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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-04 Thread Mark Roszko
Sigh, almost as bad as QT 5 minors being majors without ever bumping the 5
because "qt5" is a marketing brand they don't want to replace from the
commercial standpoint.

On Tue, Aug 4, 2020 at 9:15 AM Ian McInerney 
wrote:

>
>
> On Tue, Aug 4, 2020 at 1:44 PM Mark Roszko  wrote:
>
>> Been working on Phoenix, I basically have something working to build,
>> though it'll be awhile before I have anything to share.
>>
>>
>> However, here's the fun part:
>> wxPhoenix 4.1.0 only works with wxWidgets 3.1.4 and above
>> wxPhoenix 4.0.7 only works with wxWidgets 3.0.x series
>>
>> There's a fun gap with 3.1.0-3.1.3 :D Basically even with their fancy
>> pancy dynamic generation system for most of their code. They hardcoded
>> things specific references with no version checking fallback. Even the
>> 4.0.x series may have some compatibility issues with wx 3.0.x depending on
>> mix.
>>
>> wx is to blame too because wxWidgets 3.1.4 has API changes that
>> really should have made it 3.2.  Hell, 3.1.4 appears to have enabled a
>> newer C++ standard and the build is broken for MSVC until you patch it with
>> master because Microsoft under some newer standard flags clamped down on
>> STL export violations.
>>
>>
> wxWidgets follows a "development series" version system - only the even
> numbers are stable releases (e.g. 2.9, 3.0, 3.2, etc.), so anything in 3.1
> is going to have API/ABI changes happening as they change the API and
> stabilize it before the next stable release (the full list of changes from
> 3.0 to the current 3.1/future 3.2 is here
> https://github.com/wxWidgets/wxWidgets/blob/master/docs/changes.txt).
> This on its own isn't a problem, the real problem is that 3.1 has been in
> development for a long time and hasn't been released as a stable release
> yet.
>
>
>> I have a PR update to vcpkg to go to 3.1.4 and patch it for MSVC.
>> https://github.com/microsoft/vcpkg/pull/12733
>>
>>
>>
>> On Tue, Aug 4, 2020 at 7:41 AM Wayne Stambaugh 
>> wrote:
>>
>>> On 8/3/20 9:19 PM, Seth Hillbrand wrote:
>>> >
>>> >
>>> > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh >> > > 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.
>>>
>>> >
>>> > Obviously, if we successfully move to MSVC, this question is moot.
>>> >
>>> > -Seth
>>> >
>>>
>>> ___
>>> 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
>>>
>>
>>
>> --
>> Mark
>> ___
>> 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
>>
>

-- 
Mark
___
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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-04 Thread Ian McInerney
On Tue, Aug 4, 2020 at 1:44 PM Mark Roszko  wrote:

> Been working on Phoenix, I basically have something working to build,
> though it'll be awhile before I have anything to share.
>
>
> However, here's the fun part:
> wxPhoenix 4.1.0 only works with wxWidgets 3.1.4 and above
> wxPhoenix 4.0.7 only works with wxWidgets 3.0.x series
>
> There's a fun gap with 3.1.0-3.1.3 :D Basically even with their fancy
> pancy dynamic generation system for most of their code. They hardcoded
> things specific references with no version checking fallback. Even the
> 4.0.x series may have some compatibility issues with wx 3.0.x depending on
> mix.
>
> wx is to blame too because wxWidgets 3.1.4 has API changes that
> really should have made it 3.2.  Hell, 3.1.4 appears to have enabled a
> newer C++ standard and the build is broken for MSVC until you patch it with
> master because Microsoft under some newer standard flags clamped down on
> STL export violations.
>
>
wxWidgets follows a "development series" version system - only the even
numbers are stable releases (e.g. 2.9, 3.0, 3.2, etc.), so anything in 3.1
is going to have API/ABI changes happening as they change the API and
stabilize it before the next stable release (the full list of changes from
3.0 to the current 3.1/future 3.2 is here
https://github.com/wxWidgets/wxWidgets/blob/master/docs/changes.txt). This
on its own isn't a problem, the real problem is that 3.1 has been in
development for a long time and hasn't been released as a stable release
yet.


> I have a PR update to vcpkg to go to 3.1.4 and patch it for MSVC.
> https://github.com/microsoft/vcpkg/pull/12733
>
>
>
> On Tue, Aug 4, 2020 at 7:41 AM Wayne Stambaugh 
> wrote:
>
>> On 8/3/20 9:19 PM, Seth Hillbrand wrote:
>> >
>> >
>> > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh > > > 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.
>>
>> >
>> > Obviously, if we successfully move to MSVC, this question is moot.
>> >
>> > -Seth
>> >
>>
>> ___
>> 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
>>
>
>
> --
> Mark
> ___
> 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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-04 Thread Mark Roszko
Been working on Phoenix, I basically have something working to build,
though it'll be awhile before I have anything to share.


However, here's the fun part:
wxPhoenix 4.1.0 only works with wxWidgets 3.1.4 and above
wxPhoenix 4.0.7 only works with wxWidgets 3.0.x series

There's a fun gap with 3.1.0-3.1.3 :D Basically even with their fancy pancy
dynamic generation system for most of their code. They hardcoded things
specific references with no version checking fallback. Even the 4.0.x
series may have some compatibility issues with wx 3.0.x depending on mix.

wx is to blame too because wxWidgets 3.1.4 has API changes that
really should have made it 3.2.  Hell, 3.1.4 appears to have enabled a
newer C++ standard and the build is broken for MSVC until you patch it with
master because Microsoft under some newer standard flags clamped down on
STL export violations.

I have a PR update to vcpkg to go to 3.1.4 and patch it for MSVC.
https://github.com/microsoft/vcpkg/pull/12733



On Tue, Aug 4, 2020 at 7:41 AM Wayne Stambaugh  wrote:

> On 8/3/20 9:19 PM, Seth Hillbrand wrote:
> >
> >
> > On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh  > > 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.
>
> >
> > Obviously, if we successfully move to MSVC, this question is moot.
> >
> > -Seth
> >
>
> ___
> 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
>


-- 
Mark
___
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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-04 Thread Wayne Stambaugh
On 8/3/20 9:19 PM, Seth Hillbrand wrote:
> 
> 
> On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh  > 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.

> 
> Obviously, if we successfully move to MSVC, this question is moot.
> 
> -Seth
> 

___
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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-03 Thread Seth Hillbrand
On Mon, Aug 3, 2020, 10:48 AM Wayne Stambaugh  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.

Obviously, if we successfully move to MSVC, this question is moot.

-Seth

>
___
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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-03 Thread Wayne Stambaugh
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.

On 8/1/20 10:20 PM, Mark Roszko wrote:
> Only just noticed this
> https://www.msys2.org/news/#2020-05-17-32-bit-msys2-no-longer-actively-supported
>  
> 
> As a whole to KiCad, only 6% of Windows users will be affected.
> 
> I did change the website awhile back to more prominently push people
> onto 64-bit builds. 
> 
> Just the world finally moving forward with technology :D
> 
> -- 
> Mark
> 
> ___
> 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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-02 Thread Seth Hillbrand
On Sun, Aug 2, 2020 at 4:37 AM Ian McInerney 
wrote:

> We'll have to figure out how to phrase the support requirements for this,
> because we have committed to supporting Windows 8.1 until January 10, 2023
> apparently - and 8.1 would have 32-bit versions.
>

Right.  Well, let's see what our MSVC packaging looks like closer to v6
rollout.  I think we will probably need it for Python anyways.

For Windows 10 this should not be an issue:
https://docs.microsoft.com/en-us/windows-hardware/design/minimum/minimum-hardware-requirements-overview#31-processor

Although few OEMs install 32-bit versions, I imagine that there are a
number of board houses that run 32-bit versions to maintain compatibility
with their older control software.

-Seth

-- 
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483‬ <+12126039372>
Davis, CA
www.kipro-pcb.comi...@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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-02 Thread Mark Roszko
8.1 shouldn't be the biggest issue. Windows 7 was launched with 32-bit and
64-bit machines. By the time 8.1 rolled around 64-bit was the major default
for machines from OEMs as basically all CPUs were 64-bit capable by then.
With 10, OEMs still had the choice of 32-bit but they would be some really
terrible OEM to install 32-bit.



On Sun, Aug 2, 2020 at 7:37 AM Ian McInerney 
wrote:

> We'll have to figure out how to phrase the support requirements for this,
> because we have committed to supporting Windows 8.1 until January 10, 2023
> apparently - and 8.1 would have 32-bit versions.
>
> -Ian
>
> On Sun, Aug 2, 2020 at 4:58 AM Mark Roszko  wrote:
>
>> I am working on a MSVC build chain slowly amongst my ADHD heh.
>> Though I'm focusing on Win64 builds, Win32 would be trivial. It's just a
>> measure of how much is it worth it. Microsoft has instituted a complete ban
>> on 32-bit sales of new PCs a few months ago on their end so wiin32 is
>> slowly moving towards life support status.
>>
>> On Sat, Aug 1, 2020 at 11:31 PM Seth Hillbrand 
>> wrote:
>>
>>>
>>> On Sat, Aug 1, 2020 at 7:31 PM Mark Roszko 
>>> wrote:
>>>
 Ah right, as it stands, the only way to use a new install of msys2
 32-bit now is to patch it on startup because the repo keys changed but they
 no longer update the 32-bit base package

 See: https://www.msys2.org/news/#2020-06-29-new-packagers

 But the package versions available on 32-bit are going to begin to
 diverge from the 64-bit builds


 There may need to be a decision made about continued 32-bit support for
 KiCad Windows.


>>> Unless we push the Windows builds over to Visual Studio, this
>>> announcement makes our decision for us.  V6 makes a natural transition
>>> point for us, support-wise as well.
>>>
>>> -Seth
>>>
>>> --
>>> [image: KiCad Services Corporation Logo]
>>> Seth Hillbrand
>>> *Lead Developer*
>>> +1-530-302-5483‬ <+12126039372>
>>> Davis, CA
>>> www.kipro-pcb.comi...@kipro-pcb.com
>>>
>>
>>
>> --
>> Mark
>> ___
>> 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
>>
>

-- 
Mark
___
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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-02 Thread Ian McInerney
We'll have to figure out how to phrase the support requirements for this,
because we have committed to supporting Windows 8.1 until January 10, 2023
apparently - and 8.1 would have 32-bit versions.

-Ian

On Sun, Aug 2, 2020 at 4:58 AM Mark Roszko  wrote:

> I am working on a MSVC build chain slowly amongst my ADHD heh.
> Though I'm focusing on Win64 builds, Win32 would be trivial. It's just a
> measure of how much is it worth it. Microsoft has instituted a complete ban
> on 32-bit sales of new PCs a few months ago on their end so wiin32 is
> slowly moving towards life support status.
>
> On Sat, Aug 1, 2020 at 11:31 PM Seth Hillbrand  wrote:
>
>>
>> On Sat, Aug 1, 2020 at 7:31 PM Mark Roszko  wrote:
>>
>>> Ah right, as it stands, the only way to use a new install of msys2
>>> 32-bit now is to patch it on startup because the repo keys changed but they
>>> no longer update the 32-bit base package
>>>
>>> See: https://www.msys2.org/news/#2020-06-29-new-packagers
>>>
>>> But the package versions available on 32-bit are going to begin to
>>> diverge from the 64-bit builds
>>>
>>>
>>> There may need to be a decision made about continued 32-bit support for
>>> KiCad Windows.
>>>
>>>
>> Unless we push the Windows builds over to Visual Studio, this
>> announcement makes our decision for us.  V6 makes a natural transition
>> point for us, support-wise as well.
>>
>> -Seth
>>
>> --
>> [image: KiCad Services Corporation Logo]
>> Seth Hillbrand
>> *Lead Developer*
>> +1-530-302-5483‬ <+12126039372>
>> Davis, CA
>> www.kipro-pcb.comi...@kipro-pcb.com
>>
>
>
> --
> Mark
> ___
> 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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-01 Thread Mark Roszko
I am working on a MSVC build chain slowly amongst my ADHD heh.
Though I'm focusing on Win64 builds, Win32 would be trivial. It's just a
measure of how much is it worth it. Microsoft has instituted a complete ban
on 32-bit sales of new PCs a few months ago on their end so wiin32 is
slowly moving towards life support status.

On Sat, Aug 1, 2020 at 11:31 PM Seth Hillbrand  wrote:

>
> On Sat, Aug 1, 2020 at 7:31 PM Mark Roszko  wrote:
>
>> Ah right, as it stands, the only way to use a new install of msys2 32-bit
>> now is to patch it on startup because the repo keys changed but they no
>> longer update the 32-bit base package
>>
>> See: https://www.msys2.org/news/#2020-06-29-new-packagers
>>
>> But the package versions available on 32-bit are going to begin to
>> diverge from the 64-bit builds
>>
>>
>> There may need to be a decision made about continued 32-bit support for
>> KiCad Windows.
>>
>>
> Unless we push the Windows builds over to Visual Studio, this announcement
> makes our decision for us.  V6 makes a natural transition point for us,
> support-wise as well.
>
> -Seth
>
> --
> [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬ <+12126039372>
> Davis, CA
> www.kipro-pcb.comi...@kipro-pcb.com
>


-- 
Mark
___
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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-01 Thread Seth Hillbrand
On Sat, Aug 1, 2020 at 7:31 PM Mark Roszko  wrote:

> Ah right, as it stands, the only way to use a new install of msys2 32-bit
> now is to patch it on startup because the repo keys changed but they no
> longer update the 32-bit base package
>
> See: https://www.msys2.org/news/#2020-06-29-new-packagers
>
> But the package versions available on 32-bit are going to begin to
> diverge from the 64-bit builds
>
>
> There may need to be a decision made about continued 32-bit support for
> KiCad Windows.
>
>
Unless we push the Windows builds over to Visual Studio, this announcement
makes our decision for us.  V6 makes a natural transition point for us,
support-wise as well.

-Seth

-- 
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483‬ <+12126039372>
Davis, CA
www.kipro-pcb.comi...@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


Re: [Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-01 Thread Mark Roszko
Ah right, as it stands, the only way to use a new install of msys2 32-bit
now is to patch it on startup because the repo keys changed but they no
longer update the 32-bit base package

See: https://www.msys2.org/news/#2020-06-29-new-packagers

But the package versions available on 32-bit are going to begin to
diverge from the 64-bit builds


There may need to be a decision made about continued 32-bit support for
KiCad Windows.

On Sat, Aug 1, 2020 at 10:20 PM Mark Roszko  wrote:

> Only just noticed this
>
> https://www.msys2.org/news/#2020-05-17-32-bit-msys2-no-longer-actively-supported
>
>
> As a whole to KiCad, only 6% of Windows users will be affected.
>
> I did change the website awhile back to more prominently push people onto
> 64-bit builds.
>
> Just the world finally moving forward with technology :D
>
> --
> Mark
>


-- 
Mark
___
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


[Kicad-developers] MSYS2 Dropping 32-bit support

2020-08-01 Thread Mark Roszko
Only just noticed this
https://www.msys2.org/news/#2020-05-17-32-bit-msys2-no-longer-actively-supported


As a whole to KiCad, only 6% of Windows users will be affected.

I did change the website awhile back to more prominently push people onto
64-bit builds.

Just the world finally moving forward with technology :D

-- 
Mark
___
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