Technical Analysis and porting of Dynamic Link Library in Linux

 

Abstract: Implementation and Design of Dynamic Link Library Technology Program Common technologies include dynamic libraries in Windows and Linux systems. dynamic libraries can effectively reduce program size, save space, improve efficiency, and increase program scalability, it facilitates modular management. However, because the dynamic libraries of different operating systems have different formats, dynamic library programs need to be transplanted when calling different operating systems. This article analyzes and compares the two types of dynamic operating system library technology, and provides the methods and experience of porting the dynamic library compiled by Visual C ++ to Linux.

1. Introduction

Dynamic library (DLL) is a frequently used technology in programming. It aims to reduce the program size, save space, improve efficiency, and have high flexibility. It is easier to upgrade the software version by using the dynamic library technology. Unlike the static Link Library, functions in the dynamic library are not part of the execution program, but loaded as needed according to the execution requirements.CodeIt can be shared in multiple programs at the same time.

This method can be used in both Windows and Linux operating systems for software design, but their calling methods and programming methods are different. This article first analyzes the dynamic library calling methods and programming methods commonly used in these two operating systems, and then analyzes and compares the differences between the two methods, finally, based on the actual porting experience, this article introduces how to port the Windows dynamic library compiled by VC ++ to Linux.

2. Dynamic library technology

2.1 Windows dynamic library technology

Dynamic Link Library is an important technical means for Windows applications to share resources, save memory space, and improve usage efficiency. Common dynamic libraries include external functions and resources, and some dynamic libraries only contain resources, such as Windows Font Resource files, which are called resource dynamic link libraries. Generally, the dynamic library uses. dll,. DRV,. Fon, and so on as the suffix. The corresponding windows static library usually ends with. Lib, and Windows itself implements some major system functions in the form of dynamic library modules.

The Windows dynamic library is loaded into the virtual space of the process at runtime, and the memory allocated from the virtual address space of the calling process becomes part of the calling process. Dll can only be accessed by the thread of the process. The DLL handle can be used by the calling process, and the call Process Handle can be used by the DLL. The DLL module contains various export functions to provide external services. A dll can have its own data segment but does not have its own stack. It uses the same stack mode as the application that calls it. a dll has only one instance in the memory; DLL implements code encapsulation; DLL compilation and specificProgramming LanguageIt has nothing to do with the compiler. You can use DLL to implement mixed language programming. Any object (including variables) created by the code in the DLL function is owned by the thread or process that calls it.

Based on different call methods, dynamic library calls can be divided into static call methods and dynamic call methods.

(1) Static call, also known as implicit call, is the encoding used by the compilation system to load the DLL and uninstall the DLL when the application ends (the Windows system is responsible for counting the number of DLL calls ), the call method is simple and can meet common requirements. The call method is usually to add the. Lib file generated when a dynamic Connection Library is generated to the project of the application. To use a function in the DLL, you only need to declare it in the source file. The LIB file contains the symbolic name and selectable Identification Number of each DLL export function and the DLL file name, excluding the actual code. The information contained in the Lib file enters the generated application. The called DLL file is loaded into the memory when the application is loaded.

(2) Dynamic calling, that is, the explicit calling method, is implemented by the programmer using the API function to load and uninstall the DLL to call the DLL. It is complicated, but can use the memory more effectively, is an important way to compile large-scale applications. In Windows, functions related to dynamic library calls include:

① Loadlibrary (or afxloadlibrary of MFC) to load dynamic libraries.
② Getprocaddress: Get the function to be introduced and convert the symbol name or ID number to the internal DLL address.
③ Freelibrary (or afxfreelibrary of MFC) to release the dynamic link library.

Creating a dynamic library in Windows is also very convenient and simple. In Visual C ++, you can create a DLL program directly written in C language without using MFC, or create a DLL program based on the MFC class library. Each dll must have an entry point. In VC ++, dllmain is a default entry function. Dllmain is responsible for initialization and termination. The dynamic library output function also has two conventions, which are based on the call Convention and name modification convention. The functions defined by the DLL program are divided into internal functions and export functions. The functions exported by the dynamic library are called by other program modules. You can use the following methods to export functions:

① Use the export part of the module definition file to specify the function or variable to be input.
② Use the modifier _ declspec (dllexport) provided by MFC ).
③ Use the/Export command line to output related functions in the command line mode.

In a Windows dynamic library, you sometimes need to write a module definition file (. Def), which is a text file consisting of module statements used to describe the DLL attributes.

Technical Analysis and porting of Dynamic Link Library in Linux (2)   2.2 Linux shared object technology

In Linux, many shared object technologies are used. Although they correspond to dynamic libraries in windows, they are not called dynamic libraries. The corresponding shared object file uses. So as the suffix. For convenience, this concept is not specifically distinguished in this article. There are many shared objects ending with so in the/lib of the Linux System and the/usr/x11r6/lib directory of the standard graphic interface. Similarly, in Linux, there is also a static function library call method, and the corresponding suffix ends with.. Linux uses the shared object technology to facilitate sharing between programs, save space occupied by programs, and increase program scalability and flexibility. Linux also allows developers to replace system modules with the modules in their libraries through LD-PRELOAD variables.

Like Windows systems, it is easier to create and use dynamic libraries in Linux. You can add the-shared option when compiling the source program of the function library. In this way, the generated execution program is the dynamic link library. Generally, such a program is suffixed with so. In the process of Linux dynamic library program design, the process is usually to write user interface files, usually. h file, compile the actual function file. C or. CPP is the suffix, and then write the MAKEFILE file. This can be avoided for smaller dynamic library programs, but this design makes the program more reasonable.

After the dynamic Connection Library is compiled and generated, it can be called in the program. In Linux, you can use multiple calling methods, the same as the Windows System directory (.. system32, etc.), you can copy the dynamic library file to the/lib directory or create a symbolic connection in the/lib directory for all users to use. The following describes functions frequently used in Linux to call dynamic libraries. However, when using a dynamic library, the source program must contain the dlfcn. h header file, which defines the prototype of the function used to call the dynamic link library.

(1) _ open the Dynamic Link Library: dlopen, function prototype void * dlopen (const char * filename, int flag );
Dlopen is used to open the dynamic link library with the specified name (filename) and return the operation handle.

(2) function execution address: dlsym. The prototype of the function is void * dlsym (void * handle, char * symbol );
Dlsym returns the Execution Code address of the function corresponding to the symbol Based on the handle and symbol of the dynamic link library.

(3) Close the Dynamic Link Library: dlclose. The function prototype is int dlclose (void * handle );
Dlclose is used to close the dynamic link library of the specified handle. It will be uninstalled only when the usage count of this dynamic link library is 0.

(4) dynamic library error function: dlerror. The prototype of the function is const char * dlerror (void). When the dynamic link library operation function fails to be executed, dlerror can return error information, if the return value is null, the operation function is successfully executed.

After obtaining the function execution address, you can call the functions in the dynamic library according to the function interface declaration provided by the dynamic library in the Use Program of the dynamic library. When compiling the MAKEFILE file of the program that calls the dynamic library, you must add the compilation options-rdynamic and-LDL.

In addition to writing and calling dynamic libraries in this way, the Linux operating system also provides a more convenient dynamic library calling method, which also facilitates the calling of other programs, this method is similar to the implicit link in windows. The dynamic library name is "lib *. So .*". In this naming method, the first * indicates the name of the dynamically linked library, and the second * indicates the version number of the dynamic library, or the version number does not exist. In this call method, you need to maintain the configuration file/etc/ld of the dynamic link library. so. conf to make the dynamic link library used by the system. Usually, the directory name of the dynamic link library is appended to the dynamic link library configuration file. If the file has an X Window System release version, the file has/usr/x11r6/lib, which points to the directory of the dynamic link library of the X Window System. To make the dynamic link library shared by the system, you also need to run the management command./sbin/ldconfig of the dynamic link library. When compiling the referenced dynamic library, can I use it in GCC? L or-l options or directly reference the required dynamic link library for compilation. In Linux, you can use the LDD command to check the program dependency shared library.

Technical Analysis and porting of Dynamic Link Library in Linux (3)   3. Comparison and Analysis of Dynamic libraries of the two systems

Windows and Linux use the dynamic link library technology for the same purpose, but because of the different operating systems, they are still different in many aspects. The following describes the following aspects.

(1) dynamic library programming. In Windows, the execution file format is PE, and the dynamic library requires a dllmain function as the initial population, the _ declspec (dllexport) keyword is usually required when exporting the function declaration. In Linux, the GCC-compiled execution file is in ELF format by default, and does not require initialization entry or special Declaration on functions. This is easier to compile.

(2) dynamic library Compilation: in windows, there is a convenient debugging and compilation environment. You do not need to compile makefile files on your own. But in Linux, You need to compile makefile files by yourself, therefore, you must master certain makefile writing skills. In addition, the Linux compilation rules are usually relatively strict.

(3) For dynamic library calling, both Windows and Linux can use explicit or implicit calling for the dynamic library, but the specific calling methods are also different.

(4) view the dynamic library output function. In Windows, there are many tools and software that can be used to view the functions output in the DLL, for example, the command line dumpbin and the depends program in the VC ++ tool. In Linux, nm is usually used to view the output function. You can also use LDD to view the shared object files implicitly linked by the program.

(5) dependency on the operating system. The two dynamic libraries depend on their respective operating systems and cannot be used across platforms. Therefore, dynamic libraries that implement the same functions must provide different dynamic library versions for two different operating systems.

Technical Analysis and porting of Dynamic Link Library in Linux (4)   4. Dynamic library migration method

If you want to compile a dynamic link library that can be used in both systems, the initial development is usually completed in the debugging environment provided by Windows VC ++, after all, the graphical editing and debugging interfaces provided by VC ++ are much more convenient than vi and GCC. After the test is completed, the dynamic library program is transplanted. Generally, the default GCC compilation rules are more strict than the default compilation rules of VC ++. Many warning errors may occur in GCC debugging even if there are no warning errors under VC ++, you can use the-W option in GCC to disable the warning error.

The following describes the rules and experiences to be followed for program porting.

(1) Try not to change the sequence of original dynamic library header files. Usually in the C/C ++ language, the sequence of header files is quite related. In addition, although the C/C ++ language is case sensitive, Linux must be the same as the header file when the header file is included, because the ext2 file system is case sensitive to the file name; otherwise, the file cannot be compiled correctly, in Windows, the header file can be correctly compiled in case.

(2) Unique header files of different systems. In Windows, the windows. h header file is usually included. If the underlying communication function is called, The Winsock.. h header file is included. Therefore, when porting to a Linux system, You Need To comment out the header files unique to these windows systems and some constant definitions for some Windows systems, and add header files supported by all underlying Linux communications.

(3) data type. VC ++ has many unique data types, such as _ int16 ,__ int32, true, socket, etc. They are not supported by the GCC compiler. The common practice is to copy the statements defined for the data in windows. h and basetypes. h to a header file and then include the header file in Linux. For example, you can change the socket type to int.

(4) keywords. In VC ++, there are many keywords not used in standard C, such as bool, byte, DWORD, __asm, and so on. They are usually used as far as possible to facilitate transplantation, if it is unavoidable, you can use # ifdef and # endif to write two versions for Linux and Windows.
(5) modify the function prototype. Generally, if you use a standard dynamic library written in C/C ++, you do not need to rewrite the function. However, because of the differences between the two systems, you need to change the function call method. For example, in the network communication dynamic library compiled by Linux, use the close () function instead of the closesocket () function in the Windows operating system to close the socket. In addition, there is no file handle in Linux. To open the file, you can use open and fopen functions. For the usage of these two functions, see [2].

(6) Write makefile. In Windows, the VC ++ compiler is usually responsible for debugging. However, GCC requires you to compile the MAKEFILE file by yourself. You can also refer to the MAKEFILE file generated by VC ++. For dynamic library migration, you must add the-shared option when compiling the dynamic library. For programs that use mathematical functions, such as idempotence,-LM must be added when a dynamic library is called.

(7) other notes

① Program design structure analysis is an essential step for porting the dynamic library program compiled by another user. Generally, the dynamic library program does not contain operations such as interfaces, so it is relatively easy.
② In Linux, permissions on files or directories are divided into owners, groups, and others. Therefore, when accessing a file, pay attention to whether to perform read or write operations on the file. If you perform write operations on the file, pay attention to the permission to modify the file or directory. Otherwise, the file cannot be written.
③ When using a pointer, define a pointer to allocate only four bytes of memory to it. If you want to assign a value to the variable pointed to by the pointer, you must use the malloc function to allocate memory for it or define it as a variable without defining it as a pointer. This is more rigorous than Windows compiling in Linux. Similarly, a structure cannot contain values in a function. If you want to transmit values in a structure in a function, you must define the structure in the function as a structure pointer.
④ Path identifier, which is "/" in Linux and "/" in windows. Note that dynamic library search paths are different in Windows and Linux.
⑤ Programming and debugging skills. There are different debugging skills for different debugging environments, which are not described here.

5. Conclusion

This article systematically analyzes the implementation and usage of dynamic libraries in Windows and Linux, and comprehensively analyzes and compares the differences between the two call methods from programming, compilation, calling, and operating system dependencies, based on the actual program porting experience, the methods for porting Windows dynamic library compiled by VC ++ to Linux and the issues needing attention are given, and the sample pieces of the program are also given, in the actual program porting process, due to the system design and other aspects, the precautions for porting may be far more complex than the above, this article provides some useful experiences and skills for program porting of different operating systems Through summarization.