Skip to content
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

SuiteSparse 7.7.0 #778

Merged
merged 107 commits into from
Mar 22, 2024
Merged

SuiteSparse 7.7.0 #778

merged 107 commits into from
Mar 22, 2024

Conversation

DrTimothyAldenDavis
Copy link
Owner

No description provided.

DrTimothyAldenDavis and others added 30 commits January 29, 2024 14:38
…backend.

There are different versions of Clang on Windows:

Some of those versions use a GNU-compatible command line interface. Other
versions use a MSVC-compatible command line interface (`clang-cl`).

Additionally, either of those versions could use a MSVC-compatible
backend or a MinGW-compatible backend.

CMake sets the MSVC variable if the compiler uses a MSVC-compatible
command line interface *and* a MSVC-compatible backend.
The naming convention for import libraries differs between the
MSVC-compatible (`.lib`) and MinGW-compatible backends (`.dll.a`).

Use the same naming conventions for static libraries that are used for
MSVC also for the Clang that uses a GNU-compatible command line
interface but a MSVC-compatible backend.

This should be fixing #749.
For `clang-cl`, both `_MSC_VER` and `__clang__` are set.
Move check for `_MSC_VER` to before check for `__clang__` to allow
identifying `clang-cl` as a MSVC compatible compiler.
ParU depends on UMFPACK.
Add rules to automatically add UMFPACK to the list of packages to be built
if ParU is selected unless `SUITESPARSE_USE_SYSTEM_UMFPACK` is set.
CMake: Use MSVC naming convention for compilers that simulate a MSVC backend.
GraphBLAS: Correctly identify `clang-cl` as MSVC-compatible compiler
GraphBLAS: Avoid possibility of compatible types in `_Generic` selections
Root CMakeLists.txt: Automatically pull in UMFPACK when building ParU.
Document `SUITESPARSE_C_TO_FORTRAN` in `README.md`
…RSE_C_TO_FORTRAN instead, with better docs
ParU: Explicitly include <cinttypes> in header that uses `PRId64`
Updated to 2024
Homogenized all names, and orders.
@DrTimothyAldenDavis DrTimothyAldenDavis merged commit ca264af into dev Mar 22, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants