A proper rework of Halide CMake packaging problems mentioned in #7281
Quoting @alexreinking 's comments below:

The package decomposition I want in the end is as follows:

1. HalideHelpers (interfaces) includes all the platform-independent CMake helpers, header-only/source-injection libraries, etc.
2. HalideBuildTools includes all the libraries and executables intended to run on the host system. This is where the (to-be-created) gengen tool and the autoschedulers should go in the end.
3. Halide includes the libraries meant to be linked into the target applications.

to make find_package(Halide REQUIRED) do what find_package(HalideHelpers REQUIRED) does today and if users know they want JIT mode they can add that as a component as in find_package(Halide REQUIRED JIT)

The medium-term vision is to ship a gengen utility binary in its own package that can produce runtimes.