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 msys2 project, this is much less of an issue. I'm not sure merging these all into a single build option is completely risk free.
On 6/7/2016 2:25 PM, Nick Østergaard wrote: > 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 <[email protected]>: >> 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 >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
