kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

I found a slight problem with it.  I changed the install path of the
plugins from ${CMAKE_INSTALL_PATH}/bin/scripting/plugins to
${CMAKE_INSTALL_PREFIX}/share/kicad/scripting/plugins so this:

path_frag = Pgm().GetExecutablePath() + wxT( "../scripting/plugins" );

doesn't work.  I'm in the process of fixing it now.


On 10/1/2015 2:43 PM, Brian Sidebotham wrote:
> Shall I apply the one-liner to get python footprint wizards working on Linux?
> 
> On 30 September 2015 at 23:57, Brian Sidebotham
> <brian.sidebotham@xxxxxxxxx> wrote:
>> On 30 September 2015 at 21:19, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>> I just committed a fix so at least the python plugins will get installed
>>> in share/kicad/scripting which seems to work properly on msys2/mingw64
>>> builds.  I'll test it on Linux when I get a chance.  I'm going to pass
>>> on the python scripting example folder unless someone can confirm that
>>> all of the example python scripts work correctly.
>>
>> It's broken on Linux too, the script path is broken. I've attached a
>> patch to fix it ( a one liner )
>>
>> There's also a patch which helps when you install locally rather than
>> globally (like me!) so I can have more than one install at a time, but
>> it's tied specifically to a python version so is useless. We can fix
>> all this properly after the stable release. For now the one-liner fix
>> will work for system-wide installs.
>>
>> Best Regards,
>>
>> Brian.