Re: [gpsd-dev] report on my build nits

[Fred Wright]

On Mon, 23 Sep 2019, Greg Troxel wrote:
> "Gary E. Miller" <address@hidden> writes:
> > On Mon, 23 Sep 2019 23:26:12 +0200
> > Bernd Zeimetz <address@hidden> wrote:
> > > On 9/21/19 3:23 AM, Gary E. Miller wrote:
> > > > > I need to set PYTHON because I have no program named "python".
> > > > > Despite differing with PEPfoo, my system views it as necessary for
> > > > > soundness to bind each python-using program to a specific python
> > > > > version at build/install time, rather than letting it pick up some
> > > > > possibly-different python at run time.  Not going to get resolved,
> > > >
> > > > Yeah, little gpsd can do about broken distros that do not follow
> > > > upstream preferences.
> > >
> > > Thats not the only problem here.
> > > we need to be able to build for all supported python versions in a
> > > distribution, so we need to be able to choose the python interpreter.
> >
> > Easy.  Use the "target_python=python3.7" scons config option.
>
> I did that, and the test suite had problems, I think because
> target_python didn't get used for the tests that are written in python.

It *does* get used for the tests, and I see no evidence to the contrary. 
Note, however, if you 'build' and 'check' with different target_python 
settings, it will probably fail to notice that the extensions were built 
for the wrong Python version, and thus won't work properly.  You'd need to 
go out of your way to do that, though, since the options are sticky.

The only real bug I'm aware of is that the default target_python doesn't 
work if your system has no 'python' command.  I'll look at fixing that. 
Note that an explicitly blank target_python uses whatever Python is being 
used by SCons.

Fred Wright