kodi: remove jre override, use jre_headless

[georgewhewell]

Since #89731 is merged we can remove jre override on kodi builds.

Also, we can use headless build which reduce dependency tree a bit, useful for ARM platforms

tested on x86

Motivation for this change

reduce dependency tree on ARM

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[andir]

This is also an update from jre8 to 14. Is that intended? Any downsides with that? I can only test if it compiles but thought it might be worth mentioning.

[aanderse]

I don't think java is used for much in kodi. I think it is just bluray support maybe... a quick search says:

https://forums.gentoo.org/viewtopic-t-1089736-start-0.html

Kodi only uses Java at build time to generate some files. It does not use it at runtime. I understand that, but something else might use it if it detects it, browsers etc.

I'm not too concerned about the bump 🤷‍♂️

Maybe @peterhoeg would like to comment.

[georgewhewell]

This is also an update from jre8 to 14. Is that intended? Any downsides with that? I can only test if it compiles but thought it might be worth mentioning.

since it compiles + runs it seems happy with 14 (and as @aanderse say its just build-time dependency)

[peterhoeg]

@georgewhewell - ofborg doesn't evaluate kodi on arm64 but since that's what you are specifically targeting with this PR, is there any chance you could massage that into happening?

[lheckemann]

@peterhoeg this is an error happening on ofborg aarch64 evals generally recently, not related to these changes.