命令行构建Qt OPC UA插件时advApi32.lib链接失败求助

You’re hitting a standard Windows linker issue here: the advapi32.lib system library (which contains the Cryptography API functions mbedTLS relies on for entropy polling) isn’t being included in the link step. Your earlier attempts to add LIBS += -ladvapi32 to random .pro files didn’t work because you probably weren’t modifying the right configuration file that controls the Open62541/mbedTLS linkage. Here are actionable solutions you can try via command line or targeted file edits:

Solution 1: Inject the Library Directly via qmake Command Line #

This is the quickest fix that avoids modifying source files. Pass the library link flag directly to qmake when generating the Makefile:

qmake "LIBS += -ladvapi32" path/to/your/QtOpcUa/root/opcua.pro

Replace path/to/your/QtOpcUa/root/opcua.pro with the actual path to the main .pro file of the Qt OPC UA plugin. After running this, proceed with your normal nmake command. The quoted LIBS parameter will override or supplement any existing library settings in the .pro files.

Solution 2: Modify the Open62541 Submodule's .pro File #

If the command line approach doesn’t work, target the specific submodule that links against Open62541 and mbedTLS:

1. Navigate to the Open62541-related subdirectory in your Qt OPC UA source code. This is typically something like src/plugins/opcua/open62541.
2. Open the .pro file in this directory (e.g., opcua_open62541.pro).
3. Add the following line at the end of the file:

LIBS += -ladvapi32

4. Re-run qmake and nmake as usual.

The reason your earlier .pro edits failed is that Qt OPC UA’s build structure isolates submodules—changes to the top-level .pro weren’t being propagated to the Open62541 linkage step.

Solution 3: Verify mbedTLS's Build Configuration (If Built from Source) #

If you compiled mbedTLS from source instead of using a pre-built package, it’s possible mbedTLS itself wasn’t linked against advapi32.lib during installation:

1. Return to your mbedTLS source directory.
2. If you used qmake to build mbedTLS, add LIBS += -ladvapi32 to its main .pro file.
3. If you used CMake, update the CMakeLists.txt to include:

target_link_libraries(mbedcrypto PRIVATE advapi32)

4. Recompile and reinstall mbedTLS, then repeat the Qt OPC UA build steps.

Quick Notes #

• Ensure your Visual Studio environment is properly initialized (run vcvarsall.bat for your target architecture) so the linker can find advapi32.lib—it’s a system library, so VS should handle the path automatically.
• Use lowercase for the library flag: -ladvapi32—Windows library names are case-insensitive, but qmake’s -l convention uses lowercase for consistency.

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