Yasuhito FUTATSUKI wrote on Mon, 11 May 2020 17:55 +0900: > On 2020/05/10 1:39, Daniel Shahaf wrote: > > A minor issue in current trunk: > > > > [[[ > > % …/configure -q --enable-maintainer-mode --without-swig 'RUBY=none' > > configure: WARNING: Python.h not found; disabling python swig bindings > > ]]] > > > > That warning should not be printed when --without-swig is passed. > > > > It's printed by SVN_FIND_SWIG, which _does_ know whether that flag was > > passed (it was passed iff «$where = no»), but I'm not sure what the > > right fix is. > > I think it is not the problem of --without-swig option but the problem > of usage of PYTHON environment variable, or how to specify the target > of Python bindings. > > Even if users don't want to build Python bindings, they can't set > 'PYTHON=none', like Ruby or Perl bindings. > > On the other hand, they can build Python bindings without SWIG, > if there exists pre-generated bindings source files.
Makes sense. I guess we should add a --enable-swig-python argument, then? Cheers, Daniel
