Windows预编译静态库用/MT/MTd遇LNK4098错误求助

Hey Ryan, let's work through this LNK4098 error and your questions about runtime library usage. First, let's break down what's going on and how to fix it.

First: Are /MT and /MTd Correct for Static Libs? #

Absolutely. For static libraries on Windows:

• /MTd is the correct runtime for Debug builds (static, multi-threaded debug)
• /MT is correct for Release builds (static, multi-threaded)
  Libsodium's precompiled packages are built with these runtimes, so using the matching libs for each build mode is the right approach—your intuition here is spot-on.

What's Causing the LNK4098 Error? #

This warning (which often escalates to an error) happens when different parts of your project link against conflicting C runtime libraries. In your case, the most likely culprits are:

1. Mismatched library selection for fastbuild mode
   Your current config maps windows_fastbuild_build to the Debug lib (lib/dbg/libsodium.lib, which uses /MTd), but Bazel's fastbuild mode typically uses a runtime closer to Release (or uses /MD by default). Mixing a /MTd static lib with a project using /MD or /MT creates a runtime conflict.

2. Bazel's default runtime doesn't match Libsodium's static libs
   By default, Bazel uses dynamic runtimes (/MD for Release, /MDd for Debug) on Windows. But you're linking static Libsodium builds that use static runtimes (/MT//MTd). This mismatch triggers the LNK4098 warning.

How to Fix Your Bazel Configuration #

Let's adjust your sodium.BUILD file to align runtimes and fix the fastbuild mapping:

Step 1: Correct the Fastbuild Library Mapping #

If Libsodium doesn't provide a dedicated fastbuild lib, map fastbuild to the Release opt lib (since fastbuild is optimized for speed over debug info):

srcs = select({
    ":windows_dbg_build": ["lib/dbg/libsodium.lib"],
    ":windows_fastbuild_build": ["lib/opt/libsodium.lib"],  # Use Release lib for fastbuild
    ":windows_opt_build": ["lib/opt/libsodium.lib"],
    "//conditions:default": ["lib/opt/libsodium.a"],
})

Step 2: Force Runtime Consistency with Copts and Linkopts #

Add compilation and link options to ensure your project uses the same static runtimes as Libsodium, and exclude conflicting default libraries:

cc_library(
    name = "sodium",
    srcs = select({...}),  # Keep the corrected srcs from Step 1
    hdrs = glob(["sodium/**/*.h"]),
    defines = ["SODIUM_STATIC"],
    # Enforce static runtime matching Libsodium's build
    copts = select({
        ":windows_dbg_build": ["/MTd"],
        ":windows_fastbuild_build": ["/MT"],
        ":windows_opt_build": ["/MT"],
        "//conditions:default": [],
    }),
    # Exclude conflicting dynamic runtime libs
    linkopts = select({
        ":windows_dbg_build": ["/NODEFAULTLIB:LIBCMD", "/NODEFAULTLIB:MSVCRTD"],
        ":windows_opt_build": ["/NODEFAULTLIB:LIBCM", "/NODEFAULTLIB:MSVCRT"],
        ":windows_fastbuild_build": ["/NODEFAULTLIB:LIBCM", "/NODEFAULTLIB:MSVCRT"],
        "//conditions:default": [],
    }),
    visibility = ["//visibility:public"],
)

Step 3: Ensure Global Project Consistency #

To make sure your entire project uses the same static runtime, add these lines to your project's .bazelrc file:

# Windows static runtime defaults
build:windows --copts="/MT"
build:windows-dbg --copts="/MTd"
build:windows-fastbuild --copts="/MT"

Final Checks #

• Double-check that you've extracted the Libsodium files correctly into third_party/sodium (so paths like lib/dbg/libsodium.lib exist)
• Verify that no other dependencies in your project are using dynamic runtimes (/MD//MDd)—this would reintroduce the conflict

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