[lapack-reference] expose the lapacke option of lapack-reference

[aminya]

This adds the missing lapacke CMake option of lapack-reference so that vcpkg follows the upstream options.

Reference-LAPACK/lapack@1573c82/CMakeLists.txt#L344

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version.
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[Neumann-A]

LAPACKE needs to be its own port

[aminya]

LAPACKE needs to be its own port

@Neumann-A We can later add a generic LAPACKE port. This is simply exposing the option of lapack-reference, not touching the lapack port.

https://github.com/Reference-LAPACK/lapack/blob/1573c8275433f137107f02bb48017c2165e3ce96/CMakeLists.txt#L344

[Neumann-A]

This is simply exposing the option of lapack-reference, not touching the lapack port.

No LAPACKE depends on LAPACK and you can switch implementations lapack. as such LAPACKE is a port which depends on the lapack port!

[aminya]

This is simply exposing the option of lapack-reference, not touching the lapack port.

No LAPACKE depends on LAPACK and you can switch implementations lapack. as such LAPACKE is a port which depends on the lapack port!

Lapacke depends on lapack, but the lapacke code in lapack-reference works out of the box with lapck-reference.
What you're describing is adding patches to make that work with any lapack implementation, which is workable. However, multiple changes should be made to this code to make it usable with other lapack implementations (e.g MKL), which is not the goal of this pull request and is not a blocker.

https://github.com/Reference-LAPACK/lapack/blob/1573c8275433f137107f02bb48017c2165e3ce96/LAPACKE/CMakeLists.txt

[Neumann-A]

You don't understand that the netlib lapack git consistent of different projects in the same repo. As such you are exposing a different project via a feature which is not the correct way to do this in vcpkg. Lapacke is logical different project and needs its own port.

[JonLiu1993]

Tested feature lapacke successfully in the following triplet:

• x86-windows
• x64-windows
• x64-windows-static

[dg0yt]

IIUC the community advice, based on blas/lapack experience, was to package lapacke(-reference) separate from lapack-reference, with a dependency on lapack.

[dg0yt]

LAPACKE needs to be its own port

Draft: #42345