Why is SuiteSparse built as shared and static library? #873
Answered
by
mmuetzel
jhacsonmeza
asked this question in
Q&A
|
Sorry for this naive question, but I don't understand why SuiteSparse is built by default as a shared and static library. I'm building SuiteSparse to compile another library. I just want to understand if for my case it's just enough to build SuiteSparse only as shared library. |
Answered by
mmuetzel
Oct 7, 2024
Replies: 1 comment 1 reply
|
Afaict, shared and static libraries are built for (most of) SuiteSparse to make life easier for distributors (like Debian, Homebrew, ...). That way they can distribute binary packages that allow developers using these packages to decide whether they prefer shared or static linking. If you already know that you'll only need shared libraries and you are building SuiteSparse yourself, you can disable building static libraries. |
1 reply
|
I understand. Thank you for the clarification. |
Answer selected by
jhacsonmeza
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Afaict, shared and static libraries are built for (most of) SuiteSparse to make life easier for distributors (like Debian, Homebrew, ...). That way they can distribute binary packages that allow developers using these packages to decide whether they prefer shared or static linking.
If you already know that you'll only need shared libraries and you are building SuiteSparse yourself, you can disable building static libraries.