Alexander Neumann

> Can you show what a before/after of this change would imply? Test case added in https://github.com/microsoft/vcpkg/pull/24493/commits/7bcc75aa78ee17de02c1eb091a97322c485602b8. Port fails in current master. Here is the diff of the CMakeCache generated...

> Setting VCPKG_HOST_TRIPLET in cmake before configuring a manifest project would be a nightmare explosion of cmake presets / duplicate code determining the platform. If you are building nativly just...

> I take the approval of https://github.com/microsoft/vcpkg/pull/29153 as an indication that we don't want that. @dg0yt > Or just follow https://code.qt.io/cgit/qt/qttools.git/tree/configure.json?h=v5.15.7-lts-lgpl and we don't have to discuss at all. (even...

> Today I discovered that the LAPACK and BLAS CMake stuff doesn't work well with new gfortran on static triplets: Only with Fortran enabled, FindBLAS.cmake is successful. static lib blas...

> static lib blas needs static lib gfortran, and the latter only comes as a implicit link library for language Fortran. why does static lib need static lib gfortran? It...

~~blocked by #28734~~ (only if you want to count something being blocked by something already broken in master and only working in CI due to asset caching.)

> Can you write it on top with a task? It will much easier to track. Not necessary since the block is resolved by adjusting the ci.baseline. (since the port...

> I don't think pushing the versioning system in service of that role, as proposed here, is a good fit. @BillyONeal I removed that part since that was optional to...

@sarlinpe: I am not responsible for getting stuff merged. I just propose changes via PRs.

> Can you explain why windows-static is changed? beacuse there should only be one BLAS implementation being provided. The problem in static builds is that lapack-reference cannot link openblas due...