Provide an arm64 version on PyPI about mavsdk-python HOT 20 CLOSED

@JonasVautherin manylinux2014 will solve that problem. WIP.

from mavsdk-python.

We now provide it on pypi: https://files.pythonhosted.org/packages/46/24/8a71b6147111d4819750e453321430d93d8b3ba5bacd79dd68f618f6df3d/mavsdk-0.15.0-py3-none-manylinux2014_aarch64.whl

from mavsdk-python.

Yes, through dockcross. I started looking into that last week, hopefully I can spend some more time on it soon!

from mavsdk-python.

@hrw: working on it, I got dockcross-manylinux2014-x64 to work on my machine (was pretty easy actually). Next is aarch64! See dockcross/dockcross#358!

BTW, do you know if there is a plan in supporting 32 bits arm architectures in manylinux as well (e.g. armv7)?

from mavsdk-python.

PEP599 lists armv7l but I do not track how it goes.

from mavsdk-python.

Travis CI does not support 32bit arm could be one of reasons.

from mavsdk-python.

@SasoPavlic I assume that's a grpcio problem. See grpc/grpc#21283.

from mavsdk-python.

This would indeed be nice.

The instructions to build for arm64 would be something along the lines of:

docker run --rm dockcross/linux-arm64 > ./dockcross-linux-arm64
chmod +x dockcross-linux-arm64
./dockcross-linux-arm64 cmake -Bbuild -S. -DBUILD_BACKEND=ON
./dockcross-linux-arm64 cmake --build build

And then we just need to figure out how to get the artefacts released and into PyPi.

from mavsdk-python.

Is there an equivalent to manylinux-x86_64 on arm? At least I found some discussions about it... Not sure 🤔.

Also I'm curious about whether we could have pip build mavsdk_server from sources, but I've never done that so I don't know if we can tell pip to git clone and then run cmake and cmake --build. Ideas?

from mavsdk-python.

@hrw thanks for the note.
https://www.python.org/dev/peps/pep-0599/

from mavsdk-python.

manylinux2014 is published already. Any plans to use it?

from mavsdk-python.

I think it should not be that. The point of the docker image is to cross-compile, so it doesn't have to run on an arm system... Good to know about PEP599, thanks for the information :-)

from mavsdk-python.

Maybe for you it is to cross-compile. I use them natively. Either on available machines or on CI systems.

from mavsdk-python.

Oh, I see. Thanks for the explanation 😊. Well, we'll see if that happens at some point. Right now I have issues running the aarch64 docker image 😕. But at least the x64 seems to be working!

from mavsdk-python.

Any update @JonasVautherin?

from mavsdk-python.

I haven't had time to move forward on that, but I did some research on how to do it in dockcross. I hope I'll find some time to continue it soon!

from mavsdk-python.

We tested a new wheel on Navq companion computer (aarch64v8) and is still installing forever (stops on grpcio package).
Command used: pip install wheel_file.whl

from mavsdk-python.

I have pixhawk4 with px4 software and I would like to send MAVLINK signals to my pixhawk from jetson Nano which has arm64 system. Is it possible or is there any update

from mavsdk-python.

@nihanaltaytass, MAVSDK and mavsdk_server work fine on Jetson. I have it running on a Jetson Xavier and Orin (both aarch64 systems). You can install both with just a pip install mavsdk. The version I am running is v1.4.0 on python 3.8.10. The the only thing is you may have to create a symlink from where mavsdk_server is installed and the ./local/bin folder.. or you can put it in your python_path. But in any case, it works great on linux arm.

from mavsdk-python.

@nihanaltaytass Hi. I'm currently working on the exact setup. Any updates???

If possible: https://github.com/thien94/vision_to_mavros/blob/master/scripts/d4xx_to_mavlink.py provide me any alternative to this.

from mavsdk-python.