CMake: Navigating Multiple Compilers for a Single Language

CMake adheres to the principle of assigning a single CMAKE_CXX_COMPILER for all C source files within a CMakeLists.txt file. This approach poses challenges when attempting to combine host and cross-compilation within a single CMakeLists.txt file.

The Dilemma: Multiple Compilers for the Same Language

As per the original question, the crux of the issue lies in finding a solution to utilize multiple compilers for the same language, specifically C .

The Compromise: Limited Options

Unfortunately, CMake's design does not readily accommodate this requirement. CMake maintains a single set of compiler properties that apply to all targets within a CMakeLists.txt file. Consequently, to employ multiple compilers, it is necessary to execute CMake twice.

Alternatives: Custom Commands or Separate Files

One workaround involves the use of custom commands, essentially creating glorified shell scripts. However, this approach deviates from the desired objective.

A cleaner solution entails separating the compilation processes into distinct CMakeLists.txt files. While it prevents linking between different architectures, it eliminates the need for redundant code. To maintain consistency, common sections of the CMake scripts can be extracted into separate files and included via the include() function.

Drawbacks: Convenience to Complexity

The primary disadvantage of this approach is the loss of single-command compilation. To mitigate this, a wrapper script can be created in a preferred scripting language to invoke the necessary CMake commands.