Can not find "Imaging.h" when doing pip3 install of bindings/python

1

Hi,
I am trying to get mqtt installed on the Rpi 4B that holds the hzeller/rpi-rgb-led-matrix, so I can run scripts to show images, video, whatever.

In the /home/dietpi/rpi-rgb-led-matrix/bindings/python directory, and have followed the readme on rpi-rgb-led-matrix/bindings/python at master · hzeller/rpi-rgb-led-matrix · GitHub

and I can’t get past the make build-python step.
I get this error where it can’t find “Imaging.h”.
You can see this in rpi-rgb-led-matrix/bindings/python/rgbmatrix/shims/pillow.c at master · hzeller/rpi-rgb-led-matrix · GitHub here:

#include “Imaging.h”
#include “pillow.h”

int** get_image32(void* im) {
ImagingMemoryInstance* image = (ImagingMemoryInstance*) im;
return image->image32;
}

So… where’s “Imaging.h” at the top there?

Edit:
I’ve also tried bypassing this make build-python step with sudo pip3 install . --break-system-packages but the same stumbling block appears, “Imaging.h”.

2

Refactor broken unsafe SetImagePillow() by ty-porter · Pull Request #1818 · hzeller/rpi-rgb-led-matrix · GitHub added some python fixes. Do they help your use case?

3

I haven’t tried that.
Instead, after posting this topic, I tried following this topic and after installing missing things, stumbling through, and crossing my fingers, I got things working.

5

to both of you, first get the latest version of the source which includes

Once you have done that, if you are pretty confident that there is a problem with the python support that is not on your side, you can file a new issue and once you have, please mark it as blocking this bug:

6

I’m getting the same imaging.h error over here. Removing ‘rgbmatrix/shims/pillow.c’ from the sources array as @deadlift89 mentioned seems to fix it, but no idea what that might be breaking downstream.

9

distutils should have been removed months ago, we will have to dig into how this was reverted. There’s no need to support it any longer as it was deprecated over 5 years ago.

Regarding the imaging header: it should be one of the system Pillow image headers. It’s possible Pillow is not installed or located somewhere the script doesn’t expect.

Does sudo apt-get update && sudo apt-get install python3-pillow resolve it?

11

Yes, I’m aware Python 3.11 requires either a venv or --break-system-packages. I don’t think that should matter as Pillow is installed in the system Python that ships with the OS which should pick up this header. This project is using the system Pillow install which is why I recommended installing via apt and not pip install Pillow which would definitely break.

13

I’m suggesting installing via apt and not pip. apt does not have anything to do with pip’s --break-system-packages flag

This error is in a C shim, so it has no context for any Python specific environment variables. When I wrote the shim, I tested it against a system Pillow installation which did not need an include flag (-I) during compilation. But it’s possible my setup differed from others leading to this problem.

15

Perfect, thanks for confirming. Short term we can add that to the build instructions but I agree, it should be automated. Would you like to create an issue to track this?

18

thanks for filing the issue (which I saw before this discussion). Hopefully one of the users who also use python bindings may be able to help, but keep in mind none of them are official devs for this lib any more than I am, so please be understanding if it takes a bit of time.

1 Like