Package: kicad
Version: 4.0.2+dfsg1-4
Severity: important

Dear Mr Khaznadar,

I have recently installed KiCAD 4.0.2 fresh on this computer. Upon
opening Cvpcb, the following error appears:

Errors were encountered loading footprints
IO_ERROR: BUILD_GITHUB_PLUGIN not enabled in cmake build environment
from /home/georgesk/developpement/kicad/kicad-4.0.2+dfsg1/pcbnew/io_mgr.cpp
: PluginFind() : line 99
IO_ERROR: BUILD_GITHUB_PLUGIN not enabled in cmake build environment
from /home/georgesk/developpement/kicad/kicad-4.0.2+dfsg1/pcbnew/io_mgr.cpp
: PluginFind() : line 99
IO_ERROR: BUILD_GITHUB_PLUGIN not enabled in cmake build environment
from /home/georgesk/developpement/kicad/kicad-4.0.2+dfsg1/pcbnew/io_mgr.cpp
: PluginFind() : line 99
IO_ERROR: BUILD_GITHUB_PLUGIN not enabled in cmake build environment
from /home/georgesk/developpement/kicad/kicad-4.0.2+dfsg1/pcbnew/io_mgr.cpp
: PluginFind() : line 99
IO_ERROR: BUILD_GITHUB_PLUGIN not enabled in cmake build environment
from /home/georgesk/developpement/kicad/kicad-4.0.2+dfsg1/pcbnew/io_mgr.cpp
: PluginFind() : line 99
IO_ERROR: BUILD_GITHUB_PLUGIN not enabled in cmake build environment
from /home/georgesk/developpement/kicad/kicad-4.0.2+dfsg1/pcbnew/io_mgr.cpp
: PluginFind() : line 99
IO_ERROR: BUILD_GITHUB_PLUGIN not enabled in cmake build environment
from /home/georgesk/developpement/kicad/kicad-4.0.2+dfsg1/pcbnew/io_mgr.cpp
: PluginFind() : line 99

I believe the error is self-explanatory. If relevant, it occurs after
completing a schematic in Eeschema, exporting the netlist and then
opening Cvpcb from within Eeschema.

I imagine this also affects the layout editor, but did not test prior to
implementing a workaround.

No footprints are included with KiCAD it would appear. I can see various
footprint libraries like Air_Coils_SML_NE0SID, Buttons_Switches_SMD,
etc., in the left pane of Cvpcb but no footprints exist within them.
(Expectation being it will automatically download them via the GitHub
plugin?)

This prevents normal usage of the KiCAD PCB design workflow.

WORKAROUND (for any passers-by):

The workaround is to download the footprints manually and modify the
.config/kicad/fp-lib-table configuration file to point to the local copies
rather than the GitHub ones. A script in the KiCAD sources can do this:
https://bazaar.launchpad.net/~kicad-product-committers/kicad/product/view/head:/scripts/library-repos-install.sh

Regards,

Marc-Alexandre Chan




-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages kicad depends on:
ii  kicad-common                    4.0.2+dfsg1-4
ii  libboost-context1.58.0          1.58.0+dfsg-4.1
ii  libboost-date-time1.58.0        1.58.0+dfsg-4.1
ii  libboost-filesystem1.58.0       1.58.0+dfsg-4.1
ii  libboost-iostreams1.58.0        1.58.0+dfsg-4.1
ii  libboost-locale1.58.0           1.58.0+dfsg-4.1
ii  libboost-program-options1.58.0  1.58.0+dfsg-4.1
ii  libboost-regex1.58.0            1.58.0+dfsg-4.1
ii  libboost-system1.58.0           1.58.0+dfsg-4.1
ii  libboost-thread1.58.0           1.58.0+dfsg-4.1
ii  libc6                           2.21-8
ii  libcairo2                       1.14.6-1
ii  libgcc1                         1:5.3.1-8
ii  libgl1-mesa-glx [libgl1]        11.1.2-1
ii  libglew1.13                     1.13.0-2
ii  libglu1-mesa [libglu1]          9.0.0-2.1
ii  libgomp1                        5.3.1-8
ii  libpython2.7                    2.7.11-3
ii  libstdc++6                      5.3.1-8
ii  libwxbase3.0-0v5                3.0.2+dfsg-1.2
ii  libwxgtk3.0-0v5                 3.0.2+dfsg-1.2
ii  python-wxgtk3.0                 3.0.2.0+dfsg-1+b1

kicad recommends no packages.

Versions of packages kicad suggests:
pn  extra-xdg-menus  <none>
ii  kicad-doc-en     4.0.1+dfsg1-2

-- no debconf information

Reply via email to