On 2019/11/06 10:14, Tracey Emery wrote:
> On Fri, Nov 01, 2019 at 10:10:00AM -0600, Tracey Emery wrote:
> > Kicad built fine with this oce. Attached is a new kicad port with the
> > kicad-share changes.
> > 
> > Thanks,
> > 
> > Tracey
> > 
> 
> Hello,
> 
> Two ports are attached to this. One has with_scripting in the name, and
> the other without_scripting.
> 
> The first without_scripting port is a cleaned up version of the
> previously submitted kicad port. It aligns the order to
> Makefile.template, removes enabled-by-default CONFIGURE_ARGS, and cleans
> up WANTLIB. This appears to be ready to me, when OCE gets imported.

I'm just looking at this one for now as it seems simplest, but I'm
having problems getting it to build,

In file included from 
/usr/obj/ports/kicad-5.1.4/kicad-5.1.4/pcbnew/dialogs/dialog_netlist.cpp:39:
/usr/obj/ports/kicad-5.1.4/kicad-5.1.4/pcbnew/./netlist_reader.h:39:10: fatal 
error: 'netlist_lexer.h' file not found
#include <netlist_lexer.h>    // netlist_lexer is common to Eeschema and Pcbnew
         ^~~~~~~~~~~~~~~~~

(and similar errors from various other files on other build attempts or if
restarting).

Have you run into this, any idea what might be wrong?

> For the other with_scripting port, I was looking for a reason why cmake
> complains about multiple pcbnew targets after configuration. I found a
> patch in the Kicad forum to fix the problem. The attach port enable the
> python scripting stuff -- which I've never used --, cleans up the
> Makefile order, removes the enabled-by-defaultCONFIGURE_ARGS, and cleans
> up WANTLIB.
> 
> This one will probably need a python wrangler to look at. When pcbnew is
> opened, the following error occurs:
> 
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "/usr/local/lib/python2.7/site-packages/wxversion.py", line 152, in 
> select
>     raise VersionError("Requested version of wxPython not found")
> wxversion.VersionError: Requested version of wxPython not found
> 
> I'm not a python user, so I'm not sure where to start looking for the
> problem. Pcbnew runs without any errors that I've seen after the error
> is thrown.
> 
> If someone can figure out the problem, the with_scripting port should be
> able to be used as a revision to the without_scriptping port.
> 
> Thanks,
> 
> Tracey
> 
> -- 
> 
> Tracey Emery



Reply via email to