python3Packages.pillow & python3Packages.pillow-simd: Fix cross compilation

[kip93]

Fixes the build time error:
ModuleNotFoundError: No module named 'setuptools'.

Description of changes

Added setuptools on nativeBuildInputs, so that it's available at build time when cross compiling.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux (cross compiled from x86_64-linux)
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.11 Release Notes (or backporting 23.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[FRidh]

The hook should make setuptools available, even when cross-compiling.

[kip93]

From what I can see it only gets added if using setuptools format, but pillow uses pyproject. And I can see many packages that use pyproject adding setuptools manually, so it does not seem like I'm doing something crazy here.

[Majiir]

LGTM. Confirmed this fixes cross-compiling for armv7l.

bdf1a96 (from #244135) changed pillow's format from setuptools to pyproject. Other packages in that same PR added setuptools to nativeBuildInputs for this purpose, so I think you are in the clear.

[ghost]

Fixed pkgsCross.*.python3Packages.pillow for me.

[vcunat]

This causes over 13k rebuilds in total. Why merge directly to master?

[kip93]

Don't the docs say that small changes go to master? Or did I miss something?

I just saw that the CONTRIBUTING.md file got recently expanded from the time I created this PR, maybe I just missed something new there, I'll go re-read it. Sorry!

EDIT: Yes, I just saw the new flow of merged pull requests section about branches. Again, SORRY!

[vcunat]

The automatic red rebuild-* labels are there to signify that the PR is probably too large a rebuild. I'm sure it's expected that contributors with little experience may not know things like that; so IMHO this is more of a responsibility of the person who does the merge (though it's nice when others notice and comment about it, too).

[vcunat]

Reapplied in 094bfcf