> Op 29-okt.-2014, om 15:58 heeft Ward Poelmans <ward.poelm...@ugent.be> het > volgende geschreven: > >> In that case, then what’s the benefit of having multiple CMake modules, e.g. >> CMake-3.0.0-intel-2014b, CMake-3.0.0-foss-2014b, CMake-3.0.0-GCC-4.8.3? I >> would think that, depending on the version you load, CMake would also know >> it has to take the compiler with which it was built… > > There is no benefit of having multiple CMake with different > toolchains. We already discussed multiple times what to do with > toolchain independent modules (stuff like autotools, cmake, bison, > ...) and haven't come up with the perfect solution. They way EB > currently works, we need to build CMake for each toolchain. What > CMake-3.0.0-intel-2014b means is: CMake 3.0 build with intel 2014b > toolchain, not CMake 3.0 which always uses intel 2014b toolchain to > build stuff.
I understand — it’s an EB “issue” we have to live with. No problem. Just to know: is that subject to change anywhere in the future (e.g., starting from EB version 2 or so)? >> If easy build takes care of this, then what does it do ‘extra’? > > It sets a bunch of environmental variables and gives some arguments to > CMake where to look for includes, libraries, etc. Run easybuild with > the -l option, and you will see what it does (or just look into the > cmakemake class). As long as we are sure that this happens, it’s fine for us, so we will check those to see what happens exactly… Thanks for the pointer. > The fastest way to build something with the intel toolchain using a > CMake build system is: CC=icc CXX=icpc cmake . I guess once we find out what happens exactly we’ll be making something similar available to our users. — Regards, Franky
