Hello, I was trying to build Spot on a fresh ArchLinux install, when I came across this issue:
$ ./configure ... [...] checking for swig3.0... no checking for swig... no [...]
$ make [...] swig -c++ -python -py3 -O -nofastproxy -MD -I../buddy/src -MF .deps/buddy_wrap.TPcxx ./buddy.i make[3]: swig: Command not found [...] make: *** [Makefile:1163: all] Error 2
If Spot requires Swig, shouldn't `configure` fail ? Or, if Swig is only required for users who want to build the Python library, shouldn't the latter not be included in the `all` rule ? If that's any help, I attached my config.log. Regards, -- Clément 'Cigix' Gillard "EAT SLEEP EAT REPEAT" @skrillbug_bot, 2016-06-23
On Thu, Apr 6, 2017 at 12:46 AM, Clément Gillard <cgillard@lrde.epita.fr> wrote:
If Spot requires Swig, shouldn't `configure` fail ?
Building Spot from the distributed tarball does not require swig (we ship the files it generates), so we do not want ./configure to fail if swig is missing. If you build from git, you need to install all the additional dependencies listed at the top of HACKING. -- Alexandre Duret-Lutz
participants (2)
-
Alexandre Duret-Lutz -
Clément Gillard