Re: [Kicad-developers] Python build options

I always thought the Phoenix project was just the name given to the python 3 port of wxPython but maybe they are renaming it. I didn't see a package for it in Debain Sid so I wont hold my breath for it to be packaged any time soon. I'm not sure I want to spend the time to see if I can get it to

Re: [Kicad-developers] Python build options

well i THINK wxpython is being replaced with https://github.com/wxWidgets/Phoenix which seems to be realtively active On Wed, Jun 8, 2016 at 6:55 AM, jp charras wrote: > Le 07/06/2016 à 20:31, Wayne Stambaugh a écrit : >> wxPython is (was?) the problem child. When the

Re: [Kicad-developers] Python build options

Le 07/06/2016 à 20:31, Wayne Stambaugh a écrit : > wxPython is (was?) the problem child. When the python scripting was > originally written, wxPython wasn't always provided in a usable form on > all platforms (think Windows with native python) so we had to be able to > provide a python pcbnew

Re: [Kicad-developers] Python build options

I wasn't a matter of finding the interpreter. It was a matter of building wxPython with mingw. Once Brian wrote the kicad-winbuilder, there was a way to build python and wxpython with mingw that could be used to build kicad on windows. Up to that point, Linux was the only platform where kicad

Re: [Kicad-developers] Python build options

is that not what all the mingw stuff in the FindPythonInterp.cmake script was for? or is it different again? On Wed, Jun 8, 2016 at 6:31 AM, Wayne Stambaugh wrote: > wxPython is (was?) the problem child. When the python scripting was > originally written, wxPython wasn't

Re: [Kicad-developers] Python build options

wxPython is (was?) the problem child. When the python scripting was originally written, wxPython wasn't always provided in a usable form on all platforms (think Windows with native python) so we had to be able to provide a python pcbnew library without wxPython support. Since the advent of the

Re: [Kicad-developers] Python build options

What about one that just enables all three, for example -DKICAD_PYTHON? And it would enable? -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON 2016-06-07 20:24 GMT+02:00 Simon Wells : > Is there anyone who doesn't use All or None of the python

[Kicad-developers] Python build options

Is there anyone who doesn't use All or None of the python build options? As with how codependent a lot of the code has become it seems pointless still having the 3 build options. Would it not be better to just have one saying -DKICAD_PYTHON or -DKICAD_SCRIPTING? Simon