On Thu, Dec 1, 2016 at 2:02 PM Chuck Atkins <chuck.atk...@kitware.com>
wrote:
>
> I think the logic is a bit backwards on this and if you were to make a
> change, I'd suggest it be there and re-order a few things such that if MPI
> things haven't been already explicitly set then the *first* thing to do
> (rather than last) is test the regular compilers, then if those don't work,
> search for and interrogate the MPI wrappers.
>
> - Chuck
>
I agree, and further more, why does it not interrogate the MPI wrapper if
set as FC or CC? Would there be any harm in attempting to pull out the
{LIBRARIES,INCLUD_DIRS} etc.?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
