DLL(Dynamic Link Library) (2/2)Introduction(Engish)

The main two usage methods

The main two usage methods are Explicit Linking and Implicit Linking.

Let’s look at their main differences so that we don’t get confused in subsequent implementations.

Explicit Linking

1. During runtime, loading DLL and obtaining function pointers are required before using functions from the library.
2. The main steps include loading the DLL, obtaining function pointers, invoking functions, and releasing resources.
3. Achieved using LoadLibrary and GetProcAddress functions.
4. Suitable for cases requiring higher code flexibility, finer-grained control, and avoiding excessive dependencies.
5. Suitable for developing flexible and highly configurable programs.

Implicit Linking

1. During compile time, DLL-related information is embedded into the executable file, eliminating the need to explicitly load DLLs.
2. The main steps include including relevant header files, adding the .lib file to the linker configuration, and automatically linking functions from the DLL during compilation.
3. Implemented using #pragma comment(lib, “YourLibrary.lib”) or adding the .lib file in project settings.
4. Suitable for cases requiring simplified development processes, improved development efficiency, and reduced developer workload.
5. Suitable for faster development and lower requirements on code structure.

The simplest classification method is whether .lib files are used; .lib files are used in implicit linking, while they are not required in explicit linking.