You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice if this package offered some functionality to pass arbitrary compilation/linkage/include arguments to an extension, but to have those arguments checked beforehand for whether they are valid for the current compiler or not; and to be able to provide fallbacks in case they don't work.
For example, one might want to pass compilation argument -march=native if the compiler supports it, or fall back to -mcpu=native if it doesn't (e.g. GCC in platforms like aarch64 and ppc64), or leave it blank if neither is supported.
Same for example for something like -lmkl_rt, with a fallback to -lblas as another example.
The text was updated successfully, but these errors were encountered:
Would be nice if this package offered some functionality to pass arbitrary compilation/linkage/include arguments to an extension, but to have those arguments checked beforehand for whether they are valid for the current compiler or not; and to be able to provide fallbacks in case they don't work.
For example, one might want to pass compilation argument
-march=native
if the compiler supports it, or fall back to-mcpu=native
if it doesn't (e.g. GCC in platforms like aarch64 and ppc64), or leave it blank if neither is supported.Same for example for something like
-lmkl_rt
, with a fallback to-lblas
as another example.The text was updated successfully, but these errors were encountered: