Re: [PATCH 2/3] SConstruct: Use target_python when constructing extension name

[Ladislav Michl]

Hello Gary,

On Mon, Feb 03, 2020 at 03:09:19PM -0800, Gary E. Miller wrote:
> Yo Ladislav!
> 
> This one confuses me.  You are concerned about cross-cmpiling, right?
> 
> > +        # get version part of python extension name
> > +        ext_python_ver = config.GetPythonValue('ext version string',
> > +                                               'import sys',
> > +                                               '"_".join(map(str, '
> > +                                               'sys.version_info))')
> > +
> 
> Well, config.GetPythonValue() uses the target_python, but it works
> by executing the target_python on the build host, not the target
> host.  If the build host is on Intel, and building for MIPS, then the
> target_python will not run on the build host.
> 
> So config.GetPythonValue() will fail.
> 
> Or maybe target_python is starting an emulation environment and running
> the target python in it?

It is not exactly emulation environment, it is rather cross-python.
So it is very same version as target_python, but running on host aiming
at target. Consider it an aid for situations as this one.

> "target_python" is intended so you can built gpsd for one local python,
> say python3.7, while scons is running on another local python, say
> python2.7.
> 
> Or am I missing something?

No, you are right. I'm open to whatever solution not naming modules
after scons python. It is rather minor issue as these names are not
used on target system anyway.

Thank you,
        ladis