Ben Boeckel

I agree. I don't care about the kernel. GNU/Linux, Android/Linux, and musl/Linux are all very different beasts for core compatibility. I suppose one could just write for Linux directly (a...

Whether the target triple is a string or an array of 3 strings is not material to me :) . The information is what's important.

Kernels support a variety of binary formats. DOS, ELF, a.out, Linux supports all kinds with `binfmt_misc`. I suspect that `Kernel` will mostly be useful for kernel-specific libraries such as libkeyutils...

Are there any further questions I can help answer? The author and implementer is right here too :) .

Yes, that's the place to start. All of the "Module" pages [here](https://vtk.org/doc/nightly/html/modules.html) should be useful though. Note that nitty-gritty details are only documented in the implementation itself, not via API...

A few things I see from just poking around (haven't run it locally yet): - I recommend lowercasing usage of the API calls. It's just easier to read (alas, CMake...

> Do you know of anyone who has written a tool that will lower-case the function, macro and command names and calls in CMake files? If one does not exist,...

> Right, but if you don't allow that, then people will just take to generating the dependency files if they need this flexibility (thereby defeating the purpose of removing this...

Maybe? This is something best investigated with a proper SDK setup to see how it behaves under different settings. `ONLY` certainly seems wrong though if `CMAKE_PREFIX_PATH` stops working as intended.

I think adding `PATHS bin` to the `find_library` call may be enough, but testing would be necessary.