kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

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 build on with mingw32 or mingw64.  At this point, the
3.0.2 version suites our needs just fine.  Hopefully they will keep up
with the wxWidgets development and have a release around the same time
as wxWidgets 3.2.

On 6/7/2016 3:02 PM, Simon Wells wrote:
> 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 <jp.charras@xxxxxxxxxx> wrote:
>> 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 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.
>>
>> Yes, wxPython support is a serious problem, not only on Windows, but on all platforms.
>>
>> To be able to build Kicad without wxPython support is *mandatory*, for instance to be able to try
>> new versions of wxWidgets, or fix a wxWidgets issue (it happens sometimes ...), and rebuild
>> wxWidgets (obviously without wxPython support, because it does not exist).
>>
>> But only 2 options (DKICAD_SCRIPTING=ON/OFF (with modules generation) and
>> -DKICAD_SCRIPTING_WXPYTHON=ON/OFF) could be enough for me.
>> ( building Kicad without python support is also mandatory, because it is *really* faster, and useful
>> for testing purposes)
>>
>> Currently I am using:
>> KICAD_SCRIPTING_MODULES=ON or OFF (ON for usual build, OFF for testing builds)
>> and
>> -DKICAD_SCRIPTING_WXPYTHON=ON (sometimes) or OFF (usually).
>>
>>
>>>
>>> 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 <swel024@xxxxxxxxx>:
>>>>> 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
>>>
>>
>>
>> --
>> Jean-Pierre CHARRAS
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>