pcbnew: expose build information to python interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Fix Released
|
Unknown
|
Bug Description
It would be really nice if build version and build settings were exposed to python interface. Two usecases are:
- an action plugin could support different versions of KiCad plugin or would at least be able to notify the user that certain KiCad version is required.
- an action plugin could check for build settings such as KICAD_SCRIPTING
Using:
Application: kicad
Version: (6.0.0-
Libraries:
wxWidgets 3.0.4
libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
wxWidgets: 3.0.4 (wchar_t,wx containers,
Boost: 1.68.0
OpenCASCADE Community Edition: 6.9.1
Curl: 7.61.1
Compiler: GCC 8.2.0 with C++ ABI 1013
Build settings:
USE_
USE_
KICAD_
KICAD_
KICAD_
KICAD_
KICAD_
KICAD_
BUILD_
KICAD_
KICAD_
KICAD_SPICE=ON
Changed in kicad: | |
milestone: | none → 6.0.0-rc1 |
importance: | Undecided → Wishlist |
tags: |
added: scripting removed: wishlist |
tags: |
added: python removed: scripting |
Changed in kicad: | |
importance: | Wishlist → Unknown |
status: | Expired → Fix Released |
We could only provide the static build info. Some of the info used in the about dialog is generated at run time and requires a valid wxApp instance in order to run. Calling this from a script where no wxApp was present would fail. I looked at this and it will require factoring out the static info code from the run time info code before this can be implemented.