kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

On 24 October 2012 23:32, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
> While I don't want to pollute the title bar, would it be a good idea
> for us to mark scripting builds with -scripting like we do with
> testing?  This wouldn't be a long term thing--just until scripting
> support is in every single build.
>
> Adam Wolf

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.