Re: ✘Major build change pushed

[Curtis Olson]

Hi Gary,

Can you give any guidance on how to properly run the python "client" scripts within this new architecture?  My first attempt reported:

./gpssubframe: can't load Python gps libraries -- check PYTHONPATH.
No module named 'gps'

My second attempt (with PYTHONPATH set to "${GPSD_SOURCE_ROOT}/gps" reported:

./gpssubframe: can't load Python gps libraries -- check PYTHONPATH.
attempted relative import with no known parent package

I always feel like I get lucky when I get my own python project imports to work from a different path.  Has this been tested in the new build layout, or am I just missing something or doing something dumb?

Thanks,

Curt.

On Sun, Nov 8, 2020 at 3:03 PM Gary E. Miller <gem@rellim.com> wrote:

Yo All!

I had hoped to hold off on merging the buildtmp patches a bit longer to
check some rough edges, but the merge conflicts got into an infinite
loop.  So I merged into master while it was still possible.

If all you do is:
        scons -c
        scons && scons install

Then you will not notice any changes.

The big change is that compiled/derived files do not go back in
the file tree.  They go in a new directory under the root:
        gpsd-3.21.1~dev

If you edit a file in gpsd-3.21.1~dev it will get lost.

If you make a patch, you still patch the file in the place that
git put it.  Then scons sweeps it into the build directory.

What used to be in SConstruct is now in SConscript.  The new SConstruct
just makes the build tmp directory (gpsd-3.21.1~dev) and builds with
SConscript in that place.

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

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

--

Curtis Olson

University of Minnesota, Aerospace Engineering and Mechanics, UAS Lab