-
Notifications
You must be signed in to change notification settings - Fork 5
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
horace_mex and issues with cpp_communicator #1753
Comments
abuts
added a commit
that referenced
this issue
Sep 27, 2024
abuts
added a commit
that referenced
this issue
Sep 27, 2024
abuts
added a commit
that referenced
this issue
Sep 27, 2024
abuts
added a commit
that referenced
this issue
Sep 27, 2024
abuts
added a commit
that referenced
this issue
Sep 30, 2024
abuts
added a commit
that referenced
this issue
Sep 30, 2024
abuts
added a commit
that referenced
this issue
Sep 30, 2024
abuts
added a commit
that referenced
this issue
Sep 30, 2024
abuts
added a commit
that referenced
this issue
Sep 30, 2024
…rm.m and parallel_config.m # Conflicts: # herbert_core/classes/MPIFramework/@ClusterSlurm/ClusterSlurm.m
abuts
added a commit
that referenced
this issue
Oct 2, 2024
abuts
added a commit
that referenced
this issue
Oct 3, 2024
abuts
added a commit
that referenced
this issue
Oct 9, 2024
…(but related to the alignment ticket) and made to push the build with changed integration scripts
abuts
added a commit
that referenced
this issue
Oct 10, 2024
fixed through #1754 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
users complain that loading Horace-4 from distribution and trying to install it on clean windows machine causes problem.
cpp_communicator
does not have all its references (dll-s) satisfied on the system.To at least partially address this:
cpp_communicator
an independent on othercheck_horace_mex
checks to allow mex to be enabled regardless to mpi.mpiexec_mpi
)horace_mex
to allow users who is not familiar withcmake
building libraries on their systems.The text was updated successfully, but these errors were encountered: