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
I would like to put in a request for installed pkgconfig files for the installed mumps. I don't imagine that the source code generates anything, but you could create some simple files for the libraries installed during the conda-forge building steps. As a simple example:
prefix= <-WRITE $PREFIX TO HERE DURING BUILD
exec_prefix=${prefix}
libdir=${prefix}/lib
sharedlibdir=${libdir}
includedir=${prefix}/include
Name: dmumps_seq
Description: The sequential double MUMPS library
Version: <- WRITE THE VERSION STRING TO HERE DURING BUILD
Cflags: -I${includedir}
Libs: -L${libdir} -ldmumps_seq
I also do not know what this would correspond to on windows machines.
The text was updated successfully, but these errors were encountered:
👍 from me. This wouldn't help if the library is provided not via conda-forge, but would greatly simplify conda-forge-based linking. I've given a shot to write a wrapper that uses meson-python for builds , and my solution so far is not pretty.
@akhmerov I added these in #109. Could you check if they would work for you? I did them for the regular mumps libs, but not mumps_common or pord (it's unclear to me if users need to link those libs directly, since they are linked from the public-facing mumps libs).
Comment:
I would like to put in a request for installed pkgconfig files for the installed mumps. I don't imagine that the source code generates anything, but you could create some simple files for the libraries installed during the conda-forge building steps. As a simple example:
I also do not know what this would correspond to on windows machines.
The text was updated successfully, but these errors were encountered: