Re: [Kicad-developers] Finally!

On 15 October 2014 22:44, Brian Sidebotham wrote: > On 15 October 2014 21:44, Wayne Stambaugh wrote: >> On 10/15/2014 4:27 PM, Brian Sidebotham wrote: >>> On 5 October 2014 00:12, Brian Sidebotham >>> wrote: Hi Wayne, I can't check right now, but I'm sure it is to find python-a-mingw-

Re: [Kicad-developers] Finally!

On 15 October 2014 21:44, Wayne Stambaugh wrote: > On 10/15/2014 4:27 PM, Brian Sidebotham wrote: >> On 5 October 2014 00:12, Brian Sidebotham wrote: >>> Hi Wayne, I can't check right now, but I'm sure it is to find >>> python-a-mingw-us for kicad-winbuilder. I expect the answer is to remove the

Re: [Kicad-developers] Finally!

On 10/15/2014 4:27 PM, Brian Sidebotham wrote: > On 5 October 2014 00:12, Brian Sidebotham wrote: >> Hi Wayne, I can't check right now, but I'm sure it is to find >> python-a-mingw-us for kicad-winbuilder. I expect the answer is to remove the >> custom findpython cmake module and replace it with a

Re: [Kicad-developers] Finally!

On 5 October 2014 00:12, Brian Sidebotham wrote: > Hi Wayne, I can't check right now, but I'm sure it is to find > python-a-mingw-us for kicad-winbuilder. I expect the answer is to remove the > custom findpython cmake module and replace it with a findpythonamingwus > module instead. > > Please let

Re: [Kicad-developers] Finally!

On 10/6/2014 11:37 AM, Brian Sidebotham wrote: > On 5 October 2014 00:18, Wayne Stambaugh wrote: >> Here is a another teaser of the mingw64 version of kicad showing the >> wxPython shell so it appears to be working. >> > > Hi Wayne, > > There's no reason it shouldn't work really, KiCad-Winbuilde

Re: [Kicad-developers] Finally!

On 5 October 2014 00:18, Wayne Stambaugh wrote: > Here is a another teaser of the mingw64 version of kicad showing the > wxPython shell so it appears to be working. > Hi Wayne, There's no reason it shouldn't work really, KiCad-Winbuilder uses mingw-w64 and builds fine with wxPython (Well, the wx

Re: [Kicad-developers] Finally!

No hurry. Let me know when you have it sorted out. Please send me a patch so I can verify it on msys2. Thanks, Wayne On 10/4/2014 7:12 PM, Brian Sidebotham wrote: > Hi Wayne, I can't check right now, but I'm sure it is to find > python-a-mingw-us for kicad-winbuilder. I expect the answer is to

Re: [Kicad-developers] Finally!

Here is a another teaser of the mingw64 version of kicad showing the wxPython shell so it appears to be working. On 10/4/2014 5:09 PM, Wayne Stambaugh wrote: > After years of struggling to get KiCad to build with the wxPython > scripting enabled with mingw on Windows, I've finally managed to pull

Re: [Kicad-developers] Finally!

Hi Wayne, I can't check right now, but I'm sure it is to find python-a-mingw-us for kicad-winbuilder. I expect the answer is to remove the custom findpython cmake module and replace it with a findpythonamingwus module instead. Please let me introduce the latter before we remove the former; Sorry i

Re: [Kicad-developers] Finally!

Thanks for the input. I give Brian and chance to reply. It may have been something just for the kicad-winbuilder so I may have to find an alternate solution that works in both cases. On 10/4/2014 6:21 PM, Blair Bonnett wrote: > On 5 October 2014 10:09, Wayne Stambaugh

Re: [Kicad-developers] Finally!

The MSYS2 file layout is configured very much like Linux so that is probably why the stock version worked. The if(MINGW) code in our custom version broke finding the include file path. The MSYS2 version of cmake is 3.0.2 so they are keeping things up to date. On 10/4/2014 5:23 PM, Adam Wolf wrot

Re: [Kicad-developers] Finally!

On 5 October 2014 10:09, Wayne Stambaugh wrote: > > On that note, I had to remove our custom FindPythonLib.cmake in order to > get it to work properly. There are some questionable if( MINGW ) blocks > in our custom version that don't make sense to me. Would who ever > modified the stock CMak

[Kicad-developers] Finally!

After years of struggling to get KiCad to build with the wxPython scripting enabled with mingw on Windows, I've finally managed to pull it off. Take a look at the attached screenshot. You'll notice that all of the major KiCad features are enabled. This is due in large part to the excellent work