kicad-developers team mailing list archive

[Miguel Angel Ajo Pelayo <miguelangel@xxxxxxx>]

You're right Brian, that's the reason why you couldn't see the scripting
console button at the toolbar
and pcbnew didn't incorporate the scripting "ui" things inside, the lack of
wxPython (that as far as I know
just substitute wx itself).

I think there is another compile switch you must enable yet for scripting:

KICAD_SCRIPTING  <-- enables scripting inside pcbnew

KICAD_SCRIPTING_MODULES <--- builds a pcbnew.dll for standalone python

KICAD_SCRIPTING_WXPYTHON  <---- builds all the UI stuff dependent on
wxPython inside pcbnew


Thanks a lot for taking care of the windows build!! :)




2012/10/25 Brian Sidebotham <brian.sidebotham@xxxxxxxxx>

> > Well, the version info is correct, in that the following is a result
> > of PCBNEW->Help->Copy Version Information:
> >
> > Application: Pcbnew
> > Version: (2012-10-23 BZR 3779)-testing
> > Build: wxWidgets 2.9.4 (wchar_t,compiler with C++ ABI 1002,GCC
> > 4.7.0,wx containers,compatible with 2.8)
> > Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64
> > bit, Little endian, wxMSW
> > Boost version: 1.49.0
> > Options: USE_PCBNEW_SEXPR_FILE_FORMAT=OFF
> >          USE_PCBNEW_NANOMETRES=ON
> >          USE_PCBNEW_SEXPR_FOOTPRINT_LIBS=OFF
> >          KICAD_GOST=OFF
> >          USE_WX_GRAPHICS_CONTEXT=OFF
> >          USE_WX_OVERLAY=OFF
> >          USE_BOOST_POLYGON_LIBRARY
> >          KICAD_SCRIPTING=ON
> >
> > But what I was after was a menu option, or some visual hint that
> > PCBNEW is honouring the scripting option. i.e. a menu option to show a
> > scripting option or something! :-)
> >
> > Anyway, I just installed wxPython-2.9.4 and am building against that
> > with the KICAD_SCRIPTING_WXPYTHON option now ON.
> >
> > Best Regards, Brian.
>
> I've grabbed wxPython. I have merely installed their binaries in the
> python install, and I've grabbed their dev files and moved the
> /include/wx/wxPython directory to my local wxWidgets build which gets
> built as part of the KiCadWinbuilder script. I assume that on Windows
> we will need to compile the wxPython source as our wxWidgets libs
> instead of a native wxWidgets install.
>
> Best Regards, Brian.
>



-- 

Miguel Angel Ajo Pelayo
http://www.nbee.es
+34 636 52 25 69
skype: ajoajoajo