← Back to team overview

kicad-developers team mailing list archive

Re: KiCad-Winbuilder V3.3

 

Good work Brian,

   volunteers to help, please stand up! ;)

   When's the new baby arriving?, we're expecting for Mid-April...

   First one?, 2nd one?...  Very good luck, and congratulations!.

Cheers, Miguel Ángel.

---
irc: ajo / mangelajo
Miguel Angel Ajo Pelayo
+34 636 52 25 69
skype: ajoajoajo


2014-01-30 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.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

Follow ups

References