[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SWIG_PY_OPTS question (Re: svn commit: r1875742 - /subversion/trunk/build/generator/gen_make.py)

From: Yasuhito FUTATSUKI <futatuki_at_poem.co.jp>
Date: Fri, 27 Mar 2020 11:55:16 +0900

On 2020/03/27 8:55, Stefan Sperling wrote:
> Can anyone tell whether we need to pass additional options to
> swig via SWIG_PY_OPTS at this stage? Do we need -py3 for example?

If we use 3.0.10 <= SWIG < 4.0.0 in release process and want to
generate code for Python 3:

  SWIG_PY_OPTS="-python -py3 -nofastunpack -modern"

If we use SWIG >= 4.0.0 and want to generate code for Python 3:
  
  SWIG_PY_OPTS="-python -py3 -nofastunpack"

If we want to generate code for Python 2, use 1.3.24 <= SWIG < 4.0.0 and

  SWIG_PY_OPTS="-python -classic"

We can't bundle code for Python 3 and Python 2 at the same time.

Cheers,

-- 
Yasuhito FUTATSUKI <futatuki_at_yf.bsdclub.org> / <futatuki_at_poem.co.jp>
Received on 2020-03-27 03:57:50 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.