Porting python build scripts (libevdev showcase)

Showcase
1

I got bitten by the static bug some time ago, and was looking at what it would take to build compositors statically, specifically river.

Somewhere in that dep graph i found libevdev and decided to give it a try. I’m still new with zig, and esepecially the build system.

https://codeberg.org/allyourcodebase/libevdev

In the build process of libevdev sits a python script, which after some effort could be ported to zig, wich greatly improved my understanding of the build system and the std.Io.Writer api.

At the moment i am doing a form of snapshot testing to verify the port, but it has to be updated manually (oh my, what are we? machines?).

So naturally i looked at running the python code through the github allyourcodeebase cpython port.

Ideally, it would support running python as a build step, without any external dependencies.

but it seems like the current cpython packaged version assumes/requires dynamic linking. Has anyone tried getting this to work?

2

AFAIK most of Python lives in the DLL and the python executable ist just a small wrapper for the CLI. It should be possible to link it statically, though. IIRC this was the default for some platforms.