能否借助make工具重新创建Eclipse CDT C++项目？

Absolutely feasible—this is a smart way to avoid cluttering your repo with Eclipse-specific metadata files while still letting anyone on your team spin up a ready-to-use CDT project with a single command. Here's a breakdown of how to make this work:

Core Approach: Use Eclipse CDT's Headless Mode #

Eclipse CDT comes with a headless build/creation tool that lets you generate and configure projects entirely from the command line. You can wrap this functionality in a Makefile target to automate the process.

Step 1: Write the Makefile Target #

Here’s a practical example of a Makefile that generates an Eclipse CDT executable project with source files, include paths, and a custom build command:

# Path to your Eclipse installation (adjust this for your system)
ECLIPSE := /opt/eclipse/cdt/eclipse
# Your project details
PROJECT_NAME := MyCppApp
PROJECT_TYPE := Executable
TOOLCHAIN := Linux GCC
# Source and include configurations
SRC_FILES := $(wildcard src/*.cpp src/**/*.cpp)
INCLUDE_DIRS := include src/utils

# Convert include dirs to the format Eclipse expects (space-separated)
INCLUDE_PATHS := $(addprefix -I,$(INCLUDE_DIRS))

.PHONY: eclipse clean-eclipse

# Target to generate Eclipse project files
eclipse:
	$(ECLIPSE) -nosplash \
		-application org.eclipse.cdt.managedbuilder.core.headlessbuild \
		-createProject $(PROJECT_NAME) . $(PROJECT_TYPE) "$(TOOLCHAIN)" \
		-add $(SRC_FILES) \
		-setIncludePaths $(INCLUDE_PATHS) \
		-setBuildCommand "make all" \
		-setBuildArguments "-j$$(nproc)"

# Target to clean up Eclipse metadata
clean-eclipse:
	rm -rf .project .cproject .settings

Step 2: Key Notes for Success #

• Verify Eclipse CDT Headless Support: Ensure your Eclipse installation has the CDT headless build components. Most standard CDT packages include this, but if not, you can install it via Eclipse's marketplace or update manager.
• Platform Adjustments: On Windows, the Eclipse executable path will look like C:\Program Files\Eclipse\eclipse.exe, and you’ll need to adjust path separators and shell commands (e.g., use del instead of rm).
• Maintain Configurations: Keep your project’s core settings (like compiler flags, include paths) in the Makefile or a separate .mk include file. This way, you only update configurations in one place, and the Eclipse project stays in sync.
• Multi-Project Workspaces: If you have multiple projects, you can extend the Makefile to loop through each project’s config and generate all of them in one go, or even create a full Eclipse workspace.

Alternative: Use CMake (If You Already Use It) #

If your project already uses CMake for build management, you can skip writing custom Makefile logic and generate Eclipse CDT projects directly with:

cmake -G "Eclipse CDT4 - Unix Makefiles" -DCMAKE_BUILD_TYPE=Debug ../

This generates all the necessary .project and .cproject files based on your CMakeLists.txt, which is often cleaner if CMake is already part of your workflow.

Either way, you’ll keep your repo focused on source code and build logic, not IDE-specific files.

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