|
From: | Florian Kiera |
Subject: | Re: Cross compile gpsd-3.20.1~dev for arm with buildroot |
Date: | Tue, 23 Jun 2020 10:47:40 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 |
Am 22.06.20 um 12:57 schrieb Greg Troxel:
No need to feel sorry for; I just wanted to state it clear, might went overboard.I see; sorry for the incorrect accusation.
Still must work somehow and I haven't experienced that many issues with python compiled things yet; just gpsd. Cross compiling itself can be tricky.two thoughts: python is well known for not cross compiling well. You may be in new territory
I am not quite following, but it may be that build code setting HOST_DIR does not grasp the concept that if it is under DESTDIR, then that part should be removed to get a DESTDIR relative path. I think there may be trouble from mixing DESTDIR-aware build code from code that is not really aware but is using a path that has DESTDIR in it.
There could be a check whether DESTDIR and python_libdir contain the same path (a huge part of it). At least for cross compiling with buildroot it would work.
In fact python and its library is always under /lib|/usr/lib|/usr/lib32|/usr/lib64 isnt it? So why does it need to check from where it is called instead of some other work arounds?
I don't know which environment variables you can get while using scons, may there is one that suits better for the purpose of finding the python path?
[Prev in Thread] | Current Thread | [Next in Thread] |