kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

This is on my todo list but not until after the schematic I/O plugin and
new file format work is completed.  The reason for this is most (but not
all) of the tight coupling you mention is in the current file I/O so any
attempt to create a python library for eeschema will be have to be
changed accordingly.  If you want to start working on it, I'm fine with
that but be prepared for lots of changes over the next few months.
Also, it will have to be done with swig.  Take a look at our pcbnew
scripting support for how swig was used to wrap the board objects.


On 8/23/2016 2:46 AM, Trygve Laugstøl wrote:
> Hi
> 
> I've been wanting to automate the generation of PCB and schematic plots.
> I've been able to do the PCB parts with the existing Python interface
> (though a bit of a hassle to find), but I want the same for eeschema too
> but that doesn't seem to exist but could help get that working.
> 
> It seems that the code in scripting/ and pcbnew/scripting is too tightly
> coupled to easily copy the CMake setup from pcbnew to eeschema.
> 
> I know my way around CMake and C++ but I would appreciate some some
> pointers to the best way to get started with building a scripting
> interface for eeschema? I heard from IRC that there is work going on for
> a better general API for the Python code so I guess I would make a
> specialized plotting API.
>