I figured someone would ask that question. So far, I've only been able to get the mingw32 version to build. I'm still running into build issues with mingw64. Once I clear that hurdle, I'll try to package KiCad. The other piece of the puzzle that is missing is wxPython. I suppose I could build KiCad without scripting enabled but quite a few of our users depend on scripting support so that is a less than ideal solution. I've already looked at the documentation for creating a package using PKGBUILD so I think I have a good handle on what is required. The short answer to your question is yes there is a chance of a mingw-w64-KiCad/PKGBUILD but there is quite a bit of work to be done outside of PKGBUILD before that can happen.
On 8/19/2014 3:05 PM, Ray Donnelly wrote: > Which leads me naturally to ask: > > "Any chance of a mingw-w64-KiCad/PKGBUILD appearing?" ;-) > > On Tue, Aug 19, 2014 at 8:00 PM, Wayne Stambaugh <[email protected]> > wrote: >> On 8/19/2014 2:14 PM, Richard Shaw wrote: >>> From the department of "Be careful what you ask for..." >>> >>> I'm now the upstream maintainer of the FindwxWidgets.cmake and >>> UsewxWidgets.cmake cmake modules. >>> >>> One of the other developers worked out a slightly different way of >>> fixing the problem that my initial method but no reason to panic. I'll >>> see about doing a pull request here once it's implemented in cmake master. >>> >>> Thanks, >>> Richard >>> >> >> No good deed goes unpunished! When you have some time, I have some >> thoughts on how to improve FindwxWidgets.cmake. There is another bug >> that we have patched in a custom version of FindwxWidgets.cmake used by >> KiCad that fixes cross builds but I don't think it's the ideal solution. >> >> Wayne ------------------------------------------------------------------------------ _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
