MantisBT - CMake
View Issue Details
0011954CMakeModulespublic2011-03-09 13:482016-06-10 14:31
ChristianG 
Kitware Robot 
normalminoralways
closedmoved 
Windows7
CMake 2.8.4 
 
0011954: FindMPI fails with OpenMPI_v1.5.1-win32.exe installation
The FindMPI script doesn't work with an installation of OpenMPI_v1.5.1-win32.exe .
The output of the various "--showme:" calls is assumed to be GCC (or similar) syntax, but the Microsoft compilers use a slightly different syntax for include dirs etc.

The attached patch tries to fix the problem (and it works for me), but it isn't really nice ;) . The biggest problem is that I couldn't get find_library to find "standard" windows libraries like Ws2_32.lib .
No tags attached.
patch cmake_findmpi.patch (3,282) 2011-03-09 13:48
https://public.kitware.com/Bug/file/3747/cmake_findmpi.patch
Issue History
2011-03-09 13:48ChristianGNew Issue
2011-03-09 13:48ChristianGFile Added: cmake_findmpi.patch
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030241
2016-06-10 14:28Kitware RobotNote Added: 0041815
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030241)
David Cole   
2012-08-11 11:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041815)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.