kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

Hi Guys,

I've just uploaded a new release for KiCad-Winbuilder which includes a
few fixes and bumps wxPython up to V3+ (V3.0.0 with a couple of
patches mentioned on the KiCad developers list which are useful fixes
for KiCad). The library now also comes from GitHub (Simply by
downloading the master zip file every time).

I wanted to move the APPDATA stuff into the KiCad-Winbuilder
environment so that it was all self-contained but wxWidgets makes use
of the CSIDL_* "constants" obtained through the Windows API rather
than using the more common APPDATA environment path, so I can't
redirect that.

It may be better that it's not re-directed anyway. I tested last night
and everything appeared to work okay.

Whilst building our house and especially when our new baby arrives I
might have to leverage support from users of the script to help
maintain it. If anyone's interested in improving or helping maintain
the build system please don't hesitate to get in contact. I have
appreciated all the bug reporting that has gone on recently as the
script fell out-of-sync with KiCad's changes - it really helps focus
my time on fixing things rather than discovering things.

This is partially compounded by the fact that the default OS in my
bootloader is now Linux. However, I do not intend that to detract from
supporting KiCad-Winbuilder.

Everyone should upgrade as soon as possible. The first build takes
ages, so just let it run overnight. CMake still has issues on Windows
creating the keyword files and some other header files without error
when using parallel jobs. Therefore if those files have not yet been
created, the build defaults to no parallel jobs! Sorry I can't do
anything to resolve that issue at the moment.

Best Regards,

Brian.