# Feature Request: FindBLAS should report which vendor it found
**URL:** https://discourse.cmake.org/t/feature-request-findblas-should-report-which-vendor-it-found/14210
**Category:** Development
**Created:** [June 6, 2025, 7:56pm UTC](https://discourse.cmake.org/t/feature-request-findblas-should-report-which-vendor-it-found/14210 "2025-06-06T19:56:05Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Jacobfaib](https://discourse.cmake.org/u/Jacobfaib)
#### Post date: [June 6, 2025, 7:56pm UTC](https://discourse.cmake.org/t/feature-request-findblas-should-report-which-vendor-it-found/14210/1 "2025-06-06T19:56:05Z")
It is useful to know which BLAS implementation `find_package(BLAS)` has found, because the user might want to make use of non-standard API.
For example, you might want to set the number of OpenMP threads used by the library, and since that isn’t standard API, each implementation has a different way of saying this.
Current workarounds for this are either:
1. Manually do `set(BLA_VENDOR "some_vendor")` and call `find_package(BLAS)` until it succeeds.
2. Check the cache for `BLAS__LIBRARIES` and find the one that was found.
But these are deficient for the following reasons:
1. For (1) what happens when CMake adds support for another BLAS implementation? Or removes support for a particular vendor? Now my code probably doesn’t work anymore.
2. For (1) what happens if the order in which I do my loop is not the same order as FindBlas.cmake would do? Now I would potentially find a different BLAS.
3. For (2) it should be clear this is bad, if solely for the fact that it relies on private cache variables.
So this is something CMake should export to the user.
---
### Author:  [@brad.king](https://discourse.cmake.org/u/brad.king)
#### Post date: [June 9, 2025, 2:10pm UTC](https://discourse.cmake.org/t/feature-request-findblas-should-report-which-vendor-it-found/14210/2 "2025-06-09T14:10:08Z")
See [CMake Issue 26724](https://gitlab.kitware.com/cmake/cmake/-/issues/26724).