Windows（CLion）环境下Irrlicht库安装编译问题求助

Hey there! Let's work through getting your Irrlicht cross-platform project up and running on Windows—since you’re already solid with Linux, this should just be a matter of adjusting your setup to fit Windows’ quirks.

First, forget dropping .lib/.exp files into your project root—we’ll set up a reusable installation that works for all your Irrlicht projects:

• Download the official Windows precompiled package from the Irrlicht website (pick the version matching your toolchain: 32/64-bit, Visual Studio or MinGW).
• Extract it to a fixed, space-free path (e.g., C:\Libraries\irrlicht-1.8.5). The extracted folder will have three key subdirectories:
  • include: All the Irrlicht header files (this is where your compiler looks for #include <irrlicht.h>)
  • lib/Win32-VisualStudio or lib/Win64-VisualStudio: The static/dynamic library files for Visual Studio
  • bin: The runtime .dll files needed to run your executable

Your current config has Linux-specific hardcoding that breaks on Windows. Here’s a revised, cross-platform-friendly version with explanations:

cmake_minimum_required(VERSION 3.9)
project(bomberman)
set(CMAKE_CXX_STANDARD 11)
set(EXECUTABLE_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/bin)

# Let CMake know where to find Irrlicht (adjust the default path if you installed elsewhere)
set(IRRLICHT_DIR "C:/Libraries/irrlicht-1.8.5" CACHE PATH "Path to your Irrlicht installation")

# Find Irrlicht and populate standard CMake variables for includes/libraries
find_package(Irrlicht REQUIRED)

# Include directories: use CMake variables instead of hardcoded Linux paths
include_directories(
    ${IRRLICHT_INCLUDE_DIR}  # Auto-detected from IRRLICHT_DIR
    ${PROJECT_SOURCE_DIR}/inc
    ${PROJECT_SOURCE_DIR}/include
)

# Add your executable and link against Irrlicht
add_executable(bomberman src/main.cpp)
target_link_libraries(bomberman PRIVATE ${IRRLICHT_LIBRARY})

# Windows-specific: Copy the Irrlicht DLL to your output folder so the exe can find it at runtime
if(WIN32)
    # Pick the right DLL based on 32/64-bit build
    set(IRRLICHT_DLL "${IRRLICHT_DIR}/bin/Win32-VisualStudio/Irrlicht.dll")
    if(CMAKE_SIZEOF_VOID_P EQUAL 8)
        set(IRRLICHT_DLL "${IRRLICHT_DIR}/bin/Win64-VisualStudio/Irrlicht.dll")
    endif()
    # Auto-copy DLL after building
    add_custom_command(TARGET bomberman POST_BUILD
        COMMAND ${CMAKE_COMMAND} -E copy_if_different
        ${IRRLICHT_DLL}
        $<TARGET_FILE_DIR:bomberman>
    )
endif()

Key improvements:

• No more hardcoded /usr/include/irrlicht—uses IRRLICHT_INCLUDE_DIR which works on both OSes
• Uses modern target_link_libraries instead of global link_libraries (cleaner, scoped to your executable)
• Auto-copies the required DLL to your output folder on Windows (avoids "missing DLL" runtime errors)

• Stick to CMake variables: Never hardcode paths that only exist on Linux or Windows—use cache variables like IRRLICHT_DIR to keep your config flexible
• Match toolchains: If you prefer GCC on Windows, use the MinGW-compiled Irrlicht libraries instead of Visual Studio ones (some precompiled packages include both)
• Test both OSes often: Keep your Linux build working alongside Windows to catch cross-platform bugs early (e.g., path separators, file system behavior)
• Use CMake Presets: Create a CMakePresets.json file with separate configurations for Linux and Windows—this lets you switch environments in CLion/Git Bash with one click

• CMake can’t find Irrlicht: Double-check that IRRLICHT_DIR points to the root of your extracted Irrlicht folder, not just the lib or include subdir. If the default FindIrrlicht.cmake fails, you can manually set IRRLICHT_INCLUDE_DIR and IRRLICHT_LIBRARY instead.
• Linker errors: Make sure your build architecture (32/64-bit) matches the Irrlicht library you’re linking. Mismatches here will throw unresolved symbol errors.
• Runtime crashes: If the exe runs but crashes immediately, confirm the correct DLL is in the same folder as your executable—the post-build command in the CMake config should handle this, but you can copy it manually if needed.

内容的提问来源于stack exchange，提问作者Benjamin Sx