如何将版本化SDL目标隐藏于无版本目标后？实现统一依赖入口

Absolutely, your approach is totally feasible—and using aliases or re-exports is exactly the right way to hide SDL version details from the rest of your project. This is a common pattern in codebases of all sizes to decouple dependencies from specific versions, making future upgrades way less painful.

Since you’re referencing targets like //third_party/sdl:sdl, I’ll assume you’re using Bazel (the syntax matches), but similar logic applies to other build systems like CMake too. Here’s how to implement it:

Option 1: Use an Alias (Simplest Approach) #

Create a top-level BUILD file in third_party/sdl/ that defines an alias pointing to your currently active SDL version. This lets other parts of your project depend on //third_party/sdl:sdl without knowing the specific version under the hood.

Example third_party/sdl/BUILD file:

alias(
    name = "sdl",
    actual = "//third_party/sdl/2_0_9:sdl",
    visibility = ["//visibility:public"], # Make this accessible to all project targets
)

When you want to upgrade to 2.0.10 later, you just change the actual value to //third_party/sdl/2_0_10:sdl—no need to update every target that depends on SDL.

Option 2: Re-Export via a Wrapper Target (More Flexible) #

If you need to add extra configuration (like compiler flags, link options, or additional dependencies) on top of the raw SDL version, use a wrapper library that re-exports the specific version’s target.

Example third_party/sdl/BUILD file for C++ projects:

cc_library(
    name = "sdl",
    deps = ["//third_party/sdl/2_0_9:sdl"],
    visibility = ["//visibility:public"],
    linkstatic = True, # Adjust based on whether you need static/dynamic linking
    # Add any project-specific compiler flags here if needed
)

This works similarly to an alias but gives you room to tweak the dependency without modifying the version-specific SDL BUILD files.

Key Notes for Success #

• Consistent Target Names: Make sure every versioned SDL directory (2_0_9/, 2_0_8/, etc.) uses the same target name (e.g., sdl) for their main library. This ensures switching versions only requires updating the alias/wrapper’s actual or deps field.
• Test Easily: You can temporarily switch the alias to point to an older/newer version to run compatibility tests across your project, which is super helpful before a full upgrade.
• Other Build Systems: For CMake, you’d use add_library(sdl ALIAS sdl_2_0_9) in a top-level CMakeLists.txt, then link against sdl elsewhere. The core idea stays the same—hide the version behind a stable target.

This pattern keeps your project’s dependency graph clean, reduces technical debt, and makes version upgrades a one-line change instead of a tedious hunt through every file that references SDL.

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