-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[lapack-reference] expose the lapacke option of lapack-reference #41911
base: master
Are you sure you want to change the base?
Conversation
cf74a18
to
1615154
Compare
LAPACKE needs to be its own port |
@Neumann-A We can later add a generic LAPACKE port. This is simply exposing the option of |
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 |
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. |
This adds the missing
lapacke
CMake option oflapack-reference
so that vcpkg follows the upstream options.Reference-LAPACK/lapack@1573c82/CMakeLists.txt#L344
./vcpkg x-add-version --all
and committing the result.