CMake跨平台构建：如何根据平台自动选择Clang/clang-cl编译器？

Great choices picking Clang for your cross-platform build setup—your reasoning is totally on point:

• Using the same compiler family across platforms absolutely cuts down on those annoying compatibility bugs that pop up when moving between GCC and MSVC.
• Clang-cl’s MSVC ABI compatibility lets you call WINAPI just like you would with MSVC, which is a huge win for Windows development without ditching Clang’s consistency.

Here’s how to set up CMake to automatically choose the right Clang variant for your platform, tailored for your Qt + Ninja setup:

Step 1: Set Compiler Logic Early in CMakeLists.txt #

You’ll want to define your compiler selection before calling project() or find_package(Qt...)—CMake uses the compiler settings to configure dependencies like Qt correctly.

Add this at the very top of your CMakeLists.txt:

# Enforce Ninja generator (skip if you always pass -G Ninja via command line)
set(CMAKE_GENERATOR Ninja CACHE INTERNAL "" FORCE)

# Auto-select Clang variant based on platform
if(WIN32)
  # Windows: Use clang-cl (MSVC-compatible Clang frontend)
  set(CMAKE_C_COMPILER clang-cl CACHE PATH "C compiler" FORCE)
  set(CMAKE_CXX_COMPILER clang-cl CACHE PATH "C++ compiler" FORCE)
  
  # Optional: Add MSVC-compatible flags for ABI consistency and strictness
  add_compile_options(
    /Zc:__cplusplus  # Expose correct C++ version macros
    /permissive-     # Disable non-standard MSVC extensions
    /W4              # Enable high warning level
  )
else()
  # Unix-like (Linux/macOS): Use standard Clang
  set(CMAKE_C_COMPILER clang CACHE PATH "C compiler" FORCE)
  set(CMAKE_CXX_COMPILER clang++ CACHE PATH "C++ compiler" FORCE)
  
  # Optional: Add common Clang flags for code quality
  add_compile_options(
    -Wall
    -Wextra
    -Wpedantic
  )
endif()

Step 2: Proceed with Qt Configuration #

Once the compiler is set up, you can configure your Qt project as usual. For Qt 6, the standard setup looks like this:

# Define your project
project(YourQtApp VERSION 1.0 LANGUAGES CXX)

# Qt 6 standard setup (handles MOC, UIC, RCC automatically)
find_package(Qt6 REQUIRED COMPONENTS Core Widgets)
qt_standard_project_setup()

# Add your executable and link Qt libraries
add_executable(YourQtApp
  main.cpp
  mainwindow.cpp
  mainwindow.h
  mainwindow.ui
)

target_link_libraries(YourQtApp PRIVATE Qt6::Core Qt6::Widgets)

# Optional: Set Qt-specific target properties
set_target_properties(YourQtApp PROPERTIES
  WIN32_EXECUTABLE ON  # For Windows GUI apps
  MACOSX_BUNDLE ON     # For macOS app bundles
)

Key Notes for Smooth Setup #

• Path Configuration: On Windows, make sure the LLVM bin directory (e.g., C:\Program Files\LLVM\bin) is in your system PATH, or specify the full path to clang-cl.exe in CMAKE_CXX_COMPILER (e.g., "C:/Program Files/LLVM/bin/clang-cl.exe"). On Unix-like systems, ensure clang and clang++ are installed (use sudo apt install clang on Ubuntu, or brew install llvm on macOS if needed).
• Verify Compiler Selection: After running CMake, check the output for lines like -- The CXX compiler identification is Clang 17.0.6 or -- The CXX compiler identification is Clang 17.0.6 with MSVC-like command-line to confirm the right variant is being used. You can also add message(STATUS "Using C++ compiler: ${CMAKE_CXX_COMPILER}") to your CMakeLists to print it explicitly.
• Qt Compatibility: Qt’s build system works seamlessly with both Clang and clang-cl. The qt_standard_project_setup() function will handle all necessary compiler-specific adjustments for Qt’s tools (MOC, UIC, etc.).

内容的提问来源于stack exchange，提问作者Wahib Mkadmi