<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hey all,<div><br></div><div>This has been brought up before (sort of) here:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/26533">http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/26533</a></div><div><br></div><div>FindMPI doesn't currently give you the libraries, includes, etc. for different languages. MPI compilers can (and typically do) have different includes/libraries depending on the language you're using. It was noted above that you don't get the fortran libraries for MPI using the current macro. Another problem with the current setup is that you're also likely to inadvertently get the C++ includes with the current FindMPI, unless you explicitly disable them using things like -DOMPI_SKIP_MPICXX. This can get you unwanted C++ symbols in your MPI libraries (because the MPI C++ interface and headers suck, but that's a whole different story).</div><div><br></div><div>I'd be interested in fixing this. But I would like guidance on how to do it. My inclination would be to make a new version that gives you not just MPI_FOUND, MPI_LIBRARIES, etc.. but MPI_<LANG>_FOUND, MPI_<LANG>_LIBRARIES, MPI_<LANG>_INCLUDE_PATH, etc. If you read the thread above, someone suggested using components for this back in January, but that was left on the table and seems not to have been implemented.</div><div><br></div><div>What's the best way to implement proper language support in the FindMPI module?</div><div><br></div><div>-Todd</div><div><br></div><div><br></div></body></html>