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
T)
>
>
> CMakeDetermineASM-BGPCompiler.cmake:
>
> set(ASM_DIALECT "-BGP")
> set(CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT ${CMAKE_ASM_COMPILER})
> include(CMakeDetermineASMCompiler)
> set(ASM_DIALECT)
>
>
> CMakeTestASM-BGPCompiler.cmake:
>
> set(ASM_DIALE
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:
- C
