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

[Gary E. Miller]

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?

"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?

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

pgpwq97WaF4Ld.pgp
Description: OpenPGP digital signature