Introducing a way to builder kernels for Windows platforms

[mfuntowicz]

This PR attempts to replicate what is being done with NixOS on Windows platform through a PowerShell scripts kbuild.ps1.

It leverages build2cmake as much as possible and attempts to move some parts currently handle in Nix directly in CMake to avoid dupplication as much as possible (when feasible).

It also introduce two CMake functions to automatically generate the layout required by kernels::get_local_kernel and hub based build, so it easy to debug and publish.

[mfuntowicz]

Example invocation :

Local build with kernels::get_local_kernel compatible layout

kbuilder.ps1 -SourceFolder ./examples/activation -BuildConfig Release -Backend cuda -ArchList 8.9 -Build -LocalInstall -InstallPrefix .\examples\activation\build -Force

Local build with kernels remote layout (hub)

kbuilder.ps1 -SourceFolder ./examples/activation -BuildConfig Release -Backend cuda -ArchList 8.9 -Build -KernelsInstall -InstallPrefix .\examples\activation\build -Force

[danieldk]

Great work!

I would like to keep all CMake extensions Windows-only for the reasons outlined in the comments.

Except changes like this of course:

if(NOT MSVC)
    target_link_options({{ ops_name }} PRIVATE -static-libstdc++)
endif()

[danieldk]

Is this the same version Python and PyTorch are compiled with? (Not sure how ABI compat works on Windows)

[danieldk]

Really nice to have this, looks great!