如何在Linux环境下管理原Visual Studio多项目解决方案的开发？

Hey there, I totally get where you're coming from—switching from Visual Studio's tightly integrated project system to Linux can feel disorienting, especially when your thesis code is tied to .vcxproj files that don’t mean anything outside Windows. Let’s walk through solving your core problems and getting your build process sorted out.

1. Ditch .vcxproj for a Cross-Platform Build System: CMake #

The best tool for this job is CMake—it’s industry-standard for multi-platform C/C++ projects, and it lets you define your project structure in a way that works on Linux, Windows, and macOS. Here’s how to set it up for your 4 static libraries + 1 executable setup:

Step 1: Organize Your Project Structure #

First, tidy up your code into a clean hierarchy (adjust to match your existing setup):

your-thesis-project/
├── CMakeLists.txt       # Root build configuration
├── lib1/                # First static library
│   ├── CMakeLists.txt
│   ├── include/         # Public headers for lib1
│   │   └── lib1.h
│   └── src/             # Source files for lib1
│       └── lib1.cpp
├── lib2/                # Second static library
│   ├── CMakeLists.txt
│   ├── include/
│   └── src/
├── ... (repeat for lib3, lib4)
└── app/                 # Your executable
    ├── CMakeLists.txt
    ├── include/
    └── src/
        └── main.cpp

Step 2: Root CMakeLists.txt #

This file ties all your subprojects together. Example content:

cmake_minimum_required(VERSION 3.10)
project(ThesisProject)

# Set your C++ standard (match what you used in VS)
set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

# Add each subproject to the build
add_subdirectory(lib1)
add_subdirectory(lib2)
add_subdirectory(lib3)
add_subdirectory(lib4)
add_subdirectory(app)

Step 3: Static Library CMakeLists.txt (e.g., lib1/CMakeLists.txt) #

Define the library and its public header paths:

# Create a static library from lib1's source files
add_library(lib1 STATIC
    src/lib1.cpp
    # Add other source files here
)

# Make lib1's public headers accessible to dependent projects
target_include_directories(lib1
    PUBLIC
        ${CMAKE_CURRENT_SOURCE_DIR}/include
)

Step 4: Executable CMakeLists.txt (app/CMakeLists.txt) #

Link your executable to the static libraries:

add_executable(thesis-app
    src/main.cpp
    # Add other app source files here
)

# Link against your static libraries
target_link_libraries(thesis-app
    PRIVATE
        lib1
        lib2
        lib3
        lib4
)

2. Fixing Include Paths (No More Ugly ../) #

The target_include_directories command with the PUBLIC flag is the magic here. When you mark a library’s include directory as PUBLIC, any project that links against it (like your executable) will automatically have that path added to its header search list.

Instead of writing:

#include "../lib1/include/lib1.h"

You can just write:

#include "lib1.h"

Or even use angle brackets if you prefer:

#include <lib1.h>

CMake handles all the path resolution behind the scenes.

3. IDE Options for Linux (You Don’t Have to Use a Plain Text Editor!) #

You mentioned feeling like IDEs are "almost missing" on Linux—don’t worry, there are great options:

• CLion: JetBrains’ C/C++ IDE has top-tier CMake integration, auto-completion, and debugging tools. It’s paid, but students can get a free license.
• VS Code + CMake Tools Extension: A free alternative—install the CMake Tools and C/C++ extensions, and it will auto-detect your project, let you build/debug from the editor, and provide full intellisense.

4. Building Your Project #

Once your CMake files are set up, building is straightforward:

1. Create a separate build directory (keeps your source tree clean):

   mkdir build && cd build
   

2. Generate build files (Makefiles by default on Linux):

   cmake ..
   

3. Compile the project (use all CPU cores for faster builds):

   make -j$(nproc)
   

Final Quick Tips #

• Commit your CMake files to Git alongside your code—this keeps your build configuration synced between Windows and Linux.
• If you hit system library dependencies (like missing SSL or math libraries), install them via apt-get (e.g., sudo apt-get install libssl-dev).

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