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
Currently, users have to select DLB libraries either with C MPI bindings or Fortran MPI bindings. E.g. libdlb_mpi.so vs. libdlb_mpif.so. This works well in scenarios where the user of DLB is familiar with the code. However, often this is not the case, e.g. pre-installed applications.
I suggest to provided a version of the library which includes both MPI bindings, e.g. libdlb_mpicf.so. For instance, Extrae does this.
The text was updated successfully, but these errors were encountered:
Since just a few months, we now include the Fortan symbols in the libdlb_mpi.so library. We were still not confident enough to remove the libdlb_mpif.so, but we preferred to have only one common library rather than three versions.
Currently, users have to select DLB libraries either with C MPI bindings or Fortran MPI bindings. E.g.
libdlb_mpi.so
vs.libdlb_mpif.so
. This works well in scenarios where the user of DLB is familiar with the code. However, often this is not the case, e.g. pre-installed applications.I suggest to provided a version of the library which includes both MPI bindings, e.g.
libdlb_mpicf.so
. For instance, Extrae does this.The text was updated successfully, but these errors were encountered: