kicad-developers team mailing list archive

[Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>]

Sure, I’ll try latest over the weekend.
I can also make a debug build and try to see if it points somewhere interesting.

I never did really understand that… what’s the difference between those two switches?
One seems to be for being able to use python from inside pcbnew for automation (I can imagine why someone wants to do that, like scripting in other applications), the other one just the other way round (what from pcbnew could/would I use outside of a pcbnew window/application)?


Regards,
Bernhard

On 03.12.2014, at 20:28, jp charras <jp.charras@xxxxxxxxxx> wrote:

> Le 03/12/2014 07:32, Bernhard Stegmaier a écrit :
>> Hi,
>> 
>> don’t know about fix_swig_imports, I never did get an error when building a scripting version.
>> I didn’t build a scripting version for some weeks, though.
>> 
>> My scripting builds also almost always crashed when exiting pcbnew, so I think this is not a problem with your build.
>> This doesn’t happen with non-scripting builds.
>> 
>> 
>> Regards,
>> Bernhard
> 
> Can you try to compile with scripting/modules=ON and wxpython=OFF, and
> see if the crash happens.
> 
> Compiling with scripting/modules=ON (or at least scripting=ON) is useful
> because you have access to footprint wizards in footprint creation
> (ModEdit).
> 
> This the option I am using on Windows (building with wxpython=ON is tricky).
> 
> -- 
> 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