Re: find usage of gcov-clean target in Makefile.in

On 2019/12/05 11:03, Daniel Shahaf wrote:
> Yasuhito FUTATSUKI wrote on Thu, 05 Dec 2019 01:31 +00:00:

>> This need to generate SWIG language bindings C source and support codes
>> before configure to build them, and then, I awared that
>> 'autogen.sh --release' is now broken on generation of swig-py source
>> because of SWIG_PY_OPTS variable introduced on swig-py3 branch merge.
>> SWIG_PY_OPTS variable is now set by configure script, depends on which
>> is its target py2 or py3, and SWIG version is prior 4.0 or not, however
>> autogen.sh should be run before configure :)
>>
>> I ran
>> "env SWIG_PY_OPTS='-python -py3 -nofastunpack -modern' sh ./autogen.sh"
>> for work around.

It's actually

"env SWIG_PY_OPTS='-python -py3 -nofastunpack -modern' sh ./autogen.sh --release"

because I ran it for swig-py source generation. The autogen.sh without
"--release" works.

One more problem is that swig-pl, swig-py, swig-rb C source (and
support code) generation by swig don't work in a build directory out
of the source tree.

(There was another minor problem to run autogen.sh --release on my
FreeBSD environment, because swig package on FreeBSD install
swig as ${PREFIX}/bin/swig3.0, and autogen-standalone.mk generated
by build/generator/gen_make.py always use "SWIG = swig", so I made
a symbolic link to it as 'swig' in command search path.)

Cheers,

-- 
Yasuhito FUTATSUKI <futatuki_at_yf.bsdclub.org>/<futatuki_at_poem.co.jp>