> why does it not interrogate the MPI wrapper if set as FC or CC?
>
CC, CXX, and FC env vars are just used to initialize the
CMAKE_{C,CXX,Fortran}_COMPILER variables wihch CMake will then use as the
"regular" compilers for a given language. If those regular compilers
already work with MPI then th
On Thu, Dec 1, 2016 at 2:02 PM Chuck Atkins
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)
>
> As far as enhancements to FindMPI go, It might be worthwhile to check if
> FC, CC,CXX match any obvious MPI wrappers, and then set MPI__compiler
> and select the MPI version from there: If the user set the compiler
> explicitly to an MPI wrapper, that's likely the MPI they intend to use
> I
Toolset "v140_clang_c2" allows me to generate (& build) Clang/C2 projects
with Generator "Visual Studio 15 Win64", and Toolset "v140" regular MS "cl"
compiler projects.
Generator "NMake Makefiles" does not support any -T toolset specification;
all I can successfully generate (& build) are Makefil
Hello,
On Windows, is there any better way to strip out drive letter from path besides
using REGEX REPLACE? I looked at get_filename_component but didn't find
anything appropriate.
What I'm doing at higher level is transposition of CMAKE_INSTALL_PREFIX with
DESTDIR variable, like what install(
