CMake：配置命名空间式头文件引用及项目结构调整问询

Got it, let's fix this so you can use namespace-style header includes properly. Here's the step-by-step solution aligned with modern CMake best practices:

Step 1: Adjust Your Directory Structure #

To support the <XYZ/...> include syntax, we need to nest your header files under a subfolder matching your project name—this is the standard convention to avoid header name conflicts and enable clean namespace includes.

Before:

XYZ/
├── include/
│   ├── library.h
│   ├── module_1.h
│   └── module_2.h
├── src/
│   ├── library.cc
│   ├── module_1.cc
│   └── module_2.cc
└── CMakeLists.txt

After:

XYZ/
├── include/
│   └── XYZ/  <!-- New subfolder matching your project name -->
│       ├── library.h
│       ├── module_1.h
│       └── module_2.h
├── src/
│   ├── library.cc
│   ├── module_1.cc
│   └── module_2.cc
└── CMakeLists.txt

Step 2: Update Your CMakeLists.txt #

Your original config uses global include settings which aren't scoped to your target. Let's rewrite it to properly configure include paths for your library:

cmake_minimum_required(VERSION 3.5)
project(XYZ)

# Scope C++ 17 standard to only your library (avoids global conflicts)
target_compile_features(XYZ PRIVATE cxx_std_17)

# Create the shared library, explicitly list source files (avoid GLOB for reliability)
add_library(XYZ SHARED
    src/library.cc
    src/module_1.cc
    src/module_2.cc
)

# Set include directories for both your library and any projects linking against it
target_include_directories(XYZ
    PUBLIC
        ${PROJECT_SOURCE_DIR}/include
)

Why This Works: #

• The PUBLIC keyword ensures that both your library's source files and any external code linking to XYZ will have ${PROJECT_SOURCE_DIR}/include in their include search path.
• With the nested include/XYZ/ folder, the compiler will resolve #include <XYZ/module_2.h> directly to ${PROJECT_SOURCE_DIR}/include/XYZ/module_2.h—exactly what you need.

Step 3: Update Your Include Statements #

Now in module_2.cc (or any other source file), you can safely use:

#include <XYZ/module_1.h>
#include <XYZ/library.h>

Bonus Tips: #

• Skip using file(GLOB) to auto-collect source files—CMake won't detect new files added later, so explicit lists are more reliable.
• Using target_compile_features instead of a global CMAKE_CXX_STANDARD setting keeps your project's configuration clean and avoids unintended side effects for other targets.

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