On 24 October 2014 16:31, Wayne Stambaugh stambau...@verizon.net wrote:
Brian,
I restored the custom FindPythonLibs.cmake file. I found an issue with
the stock version when configuring on MSYS2. I made some minor changes
to it which should make it more robust when looking for mingw python
On 10/25/2014 4:59 PM, Brian Sidebotham wrote:
On 24 October 2014 16:31, Wayne Stambaugh stambau...@verizon.net wrote:
Brian,
I restored the custom FindPythonLibs.cmake file. I found an issue with
the stock version when configuring on MSYS2. I made some minor changes
to it which should
On 25 October 2014 22:29, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/25/2014 4:59 PM, Brian Sidebotham wrote:
I expect the other two PATH_SUFFIXES supplied to that find_path() are
wrong by the way, I've not removed them in case they are actually
correct, but generally the only
Brian,
I restored the custom FindPythonLibs.cmake file. I found an issue with
the stock version when configuring on MSYS2. I made some minor changes
to it which should make it more robust when looking for mingw python
builds. Please test it out when you get a chance and let me know if you
find
Hi, I have previously used kicad-winbuilder successfully, but I just tried
it again (in a fresh directory) and get the error below. I tried it in a
much shorter path too and it still fails (and it worked with that path
before so I'm pretty sure it's not the path).
Anyone have any ideas?
Cheers,
Kicad-Winbuilder was broke a few commits ago by removing some custom python
finding cmake module. I've not had the time to replace it with another
working version. I was hoping to replace it before it was removed.
Hopefully it should be fixed soon!
Best Regards,
Brian.
On 22 Oct 2014 21:30, Tim
6 matches
Mail list logo
