[Slackbuilds-users] kicad build error

B. Watson urchlay at slackware.uk
Mon Dec 12 18:06:23 UTC 2022

On Mon, 12 Dec 2022, Tim Dickson via SlackBuilds-users wrote:

> I've found a work-around.
> 1. uninstall wxWidgets if installed
> 2. reinstall wxGTK3
> 3. reinstall wxPython3
> 4. run the kicad slackbuild
> it looks like there is a compiling issue when the stand-alone wxWidgets 
> package is a different version than the ones included/used by wxGTK3 and 
> wxPython3
> 5. reinstall wxWidgets if it was installed
> I'm not sure what the longer term solution is though. :-)
> regards, Tim

This has been an ongoing problem for things that use
wx(Widgets|GTK|Python) for ages.

At bare minimum, the kicad README should be updated to explain the
situation and the workaround.

A better solution would be, have the kicad SlackBuild pass an explicit
path to the wx-config script for the specific version of wx* it needs.
How this is done depends on how kicad's build stuff works (cmake or

I've done this for quite a few builds in the repo, but it's something
that has to be done on a per-build basis, and different types of build
(cmake, autotools, scons, etc) need different things done, so it can't
really be automated.

The config scripts live in /usr/lib$LIBDIRSUFFIX/wx/config. One
of them will also be symlinked to /usr/bin/wx-config (this will be
whichever wx-version was most recently installed). This has been an
ongoing problem for years now, and nobody seems really interested in
coming up with a true solution (a way for the various versions to live
side-by-side and for builds to easily use the correct version).

More information about the SlackBuilds-users mailing list