Hi George,
The obvious way to compile front-end tools is to create another directory,
e.g., front-end-build and run cmake therein to re-configure and build
with a front-end compiler.
However, since only a relatively small subset of the files needs to be
compiled for the front-end, it is
Hi Chuck,
Thanks for your e-mail.
Yes, the different build directory strategy is definitely the clean way to
do this.
However, it is my experience that folks not familiar with CMake tend to get
a knee-jerk reaction when required to configure and build seperately.
Especially, when something like
Hi George,
You could (ab)use the assembler plugin system for that. Define your
own CMake-ASM-BGQ*.cmake files and use the assembler to compile the
sources.
Here's how I did this a couple of years ago for the BG/P.
In the CMakeLists.txt file for the files that need to be compiled with
the BG/P
Hi Marcel,
Thanks for your e-mail. I am not sure if your approach wil fully satisfy my
use case. I need to compile on both the back-end and front-end.
My question really boils down to whether it's possible to use two different
compilers for the same language within the same configuration.
I was
Dear all,
I am working on a project where on certain platforms, namely, on a BG/Q or
Cray, we have to cross-compile the code, but still, there are parts of the
code that should only be compiled for the front end, login nodes.
Typically, we have a toolchain file, which among other things sets:
-
