A good while ago, KiCad-Winbuilder changed from it's current form on
Launchpad to using msys2 to build KiCad because that provided all the
MinGW packages required. You'll find that project hosted on GitHub: https://github.com/BrianSidebotham/KiCad-Winbuilder. It is now how the
Windows installer is built.
The project has essentially been handed over to Nick ( https://github.com/nickoe ) who's been working on it for a while and
getting it to run on the ci server so that it produces regular
binaries.
KiCad-Winbuilder is probably no longer of any use to anyone because
you now have access to snapshots built using it anyway: http://kicad-pcb.org/download/windows/ (See the Recent Builds link)
I will reflect all of this on the KiCad-Winbuilder launchpad site
tonight so everyone is aware of the new version of the tool and the
snapshot availability.
Best Regards,
Brian.
On 5 October 2015 at 00:02, Wayne Stambaugh <email address hidden> wrote:
> I just changed this and it should work fine unless Brian did some non-
> standard install path stuff in kicad-winbuilder. The install sub-
> folders on linux and windows should be the same now and should not be
> changed. I will not apply your patch because it will break some of the
> other install path stuff. I recommend not using kicad-winbuilder and
> using msys2/mingw64 to build kicad. It is the preferred method on
> windows since it provides pre-built packages for all of the necessary
> dependencies.
>
> ** Changed in: kicad-winbuilder
> Status: New => Invalid
>
> --
> You received this bug notification because you are a member of Valvers
> GCode Committers, which is subscribed to kicad-winbuilder.
> Matching subscriptions: kicad-winbuilder-bugs-subs, winbuilder-bugs
> https://bugs.launchpad.net/bugs/1502667
>
> Title:
> KiCAD scripting python has new location
>
> Status in kicad-winbuilder:
> Invalid
>
> Bug description:
> After developer revision 6236 the scripting plugin directory has a new
> location. Now on windows and linux the search path is in the share
> dir. I have generate a little patch to correct the install dir in the
> kicad-winbuilder script. Additionally I send even a small patch of the
> revision 6236 to the developer team for kicad, because even a small
> change needs to be made. On linux the scripting wizard is now working.
> With these small changes, we have a homogeneous structure in Linux and
> Windows.
>
> see:
> https://bugs.launchpad.net/kicad/+bug/1493052
> https://bugs.launchpad.net/kicad/+bug/1501725
>
> regards
> Michael
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad-winbuilder/+bug/1502667/+subscriptions
Yes, https:/ /launchpad. net/kicad- winbuilder did custom install steps.
A good while ago, KiCad-Winbuilder changed from it's current form on /github. com/BrianSidebo tham/KiCad- Winbuilder. It is now how the
Launchpad to using msys2 to build KiCad because that provided all the
MinGW packages required. You'll find that project hosted on GitHub:
https:/
Windows installer is built.
The project has essentially been handed over to Nick ( /github. com/nickoe ) who's been working on it for a while and
https:/
getting it to run on the ci server so that it produces regular
binaries.
KiCad-Winbuilder is probably no longer of any use to anyone because kicad-pcb. org/download/ windows/ (See the Recent Builds link)
you now have access to snapshots built using it anyway:
http://
I will reflect all of this on the KiCad-Winbuilder launchpad site
tonight so everyone is aware of the new version of the tool and the
snapshot availability.
Best Regards,
Brian.
On 5 October 2015 at 00:02, Wayne Stambaugh <email address hidden> wrote: r-bugs- subs, winbuilder-bugs /bugs.launchpad .net/bugs/ 1502667 /bugs.launchpad .net/kicad/ +bug/1493052 /bugs.launchpad .net/kicad/ +bug/1501725 /bugs.launchpad .net/kicad- winbuilder/ +bug/1502667/ +subscriptions
> I just changed this and it should work fine unless Brian did some non-
> standard install path stuff in kicad-winbuilder. The install sub-
> folders on linux and windows should be the same now and should not be
> changed. I will not apply your patch because it will break some of the
> other install path stuff. I recommend not using kicad-winbuilder and
> using msys2/mingw64 to build kicad. It is the preferred method on
> windows since it provides pre-built packages for all of the necessary
> dependencies.
>
> ** Changed in: kicad-winbuilder
> Status: New => Invalid
>
> --
> You received this bug notification because you are a member of Valvers
> GCode Committers, which is subscribed to kicad-winbuilder.
> Matching subscriptions: kicad-winbuilde
> https:/
>
> Title:
> KiCAD scripting python has new location
>
> Status in kicad-winbuilder:
> Invalid
>
> Bug description:
> After developer revision 6236 the scripting plugin directory has a new
> location. Now on windows and linux the search path is in the share
> dir. I have generate a little patch to correct the install dir in the
> kicad-winbuilder script. Additionally I send even a small patch of the
> revision 6236 to the developer team for kicad, because even a small
> change needs to be made. On linux the scripting wizard is now working.
> With these small changes, we have a homogeneous structure in Linux and
> Windows.
>
> see:
> https:/
> https:/
>
> regards
> Michael
>
> To manage notifications about this bug go to:
> https:/