build(cmake): support MSVC toolchains

[IvanaGyro]

Stack

#1109 → #1110 → #1116 → #1117 → #1118 → #1119 → #1113

This is the first split layer and remains based on #1109. Review only this PR's CMake/compiler portability diff; Pixi, CUDA dispatch, wheel packaging, release metadata, and workflow integration are isolated in the later PRs.

Summary

• add native MSVC compiler, sanitizer, GoogleTest, and small Windows-only test compatibility;
• keep MinGW and non-Windows compiler flags on their existing paths;
• make Boost, Python/pybind11, LAPACK/ARPACK, CUDA device-runtime, cuTENSOR, and cuQuantum discovery/export portable to Windows;
• keep CUDA response files enabled only where Windows command-line limits require them;
• keep installed CMake targets relocatable instead of exporting Pixi build paths;
• give the Python module's Windows import library a non-conflicting archive name;
• configure Type.cpp through lapacke_config.h so MSVC does not parse LAPACK 3.11 C99 complex declarations.

The __blasINTsize__ global is otherwise unused internally; its planned removal and the eventual deletion of this temporary Type.cpp header dependency are tracked in #1115.

Linux and macOS

All new platform behavior is guarded by WIN32/MSVC or preserves the prior non-Windows branch. The previous full stack passed macOS 14, macOS 15 Intel, Ubuntu x86-64, and Ubuntu ARM wheel jobs; the split will rerun those checks independently.

Validation

• repository-pinned pre-commit hooks pass;
• incremental MSVC/OpenBLAS compilation passes for Type.cpp.obj;
• a separate lapack_wrapper.hpp consumer (Complexmem_cpu.cpp.obj) also compiles;
• CMake configures the existing CPU and CUDA build trees;
• the CUDA-dependent source rewrite is intentionally absent and reviewed separately in fix(cuda): avoid NVCC/cudafe++ crashes on Windows when processing MSVC STL multi-variant visitation. #1116.

Part of #1114.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1fc237fa81

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Re-find LAPACKE for installed OpenBLAS targets

When a Windows build uses the default OpenBLAS backend, this re-finds only LAPACK, while CytnxBKNDCMakeLists.cmake:162 still publicly links the build-time ${LAPACK_LIBRARIES} and ${LAPACKE_LIBRARIES} without the BUILD_INTERFACE guard used by the MKL path. Consequently, after the Pixi/build environment is removed or the installation is relocated, CytnxTargets.cmake still references the old .lib paths; appending LAPACK::LAPACK neither removes those paths nor guarantees the separately discovered LAPACKE symbols. Make the Windows OpenBLAS link entries build-only and resolve LAPACKE in the consumer environment as well. CLAUDE.mdL105-L106

Useful? React with 👍 / 👎.