WO2022116437A1

WO2022116437A1 - Multi-architecture static library conflict processing method and apparatus, device, and storage medium

Info

Publication number: WO2022116437A1
Application number: PCT/CN2021/083792
Authority: WO
Inventors: 吴烁宇
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-12-03
Filing date: 2021-03-30
Publication date: 2022-06-09
Also published as: CN112506558A

Abstract

A multi-architecture static library conflict processing method and apparatus, a device, and a storage medium. The multi-architecture static library conflict processing method comprises: extracting a multi-architecture static library list having a static library conflict and separating same into a plurality of single-architecture static libraries; extracting a first symbol table of each single-architecture static library and performing reference symbol updating to obtain a second symbol table having a dependency relationship; decompressing each single-architecture static library, and extracting a target file list of each single-architecture static library and a third symbol table corresponding to each target file; with reference to the second symbol table, modifying a symbol name, a symbol structure size, and a memory start address of a corresponding symbol in the third symbol table; and re-compressing and merging the target files in the target file list corresponding to each single-architecture static library into a new multi-architecture static library. By means of the method, a static library conflict can be quickly positioned, the conflict can be resolved, and stable operation of a multi-architecture static library is ensured.

Description

Multi-architecture static library conflict processing method, apparatus, device and storage medium

This application claims the priority of the Chinese patent application filed on December 3, 2020 with the application number 202011393997.3 and the title of the invention is "Multi-architecture Static Library Conflict Handling Method, Apparatus, Equipment and Storage Medium", the entire contents of which are Incorporated in the application by reference.

technical field

The present application relates to the field of artificial intelligence, and in particular, to a multi-architecture static library conflict processing method, apparatus, device and storage medium.

Background technique

With the development of computer technology, there are more and more modules that need continuous iterative integration in the development of iOS/Mac platform application software. When the functions of new modules require partial transformation of the original static library, or when different modules rely on the same static library When there are local differences in the external interface of the static library between different versions of the library, in the process of compiling the software application, the problem of static library conflict will occur, which will affect the functions of each business module.

The inventor realizes that the existing methods for dealing with static library conflicts have limitations, and the static libraries processed by the existing static library conflict processing methods usually require a lot of manual verification work, and need to be modified and tested repeatedly. , it can be used normally, and there may be the risk that business functions cannot be used normally, and the processing efficiency is low, and it cannot meet the requirements of minimal changes and rapid and stable launch of complex services.

SUMMARY OF THE INVENTION

The main purpose of this application is to solve the technical problems of low efficiency and poor stability in handling static library conflicts.

A first aspect of the present application provides a multi-architecture static library conflict processing method, and the multi-architecture static library conflict processing method includes:

Scanning each multi-architecture static library respectively, extracting a multi-architecture static library list with static library conflicts, and separating each multi-architecture static library in the multi-architecture static library list into a plurality of single-architecture static libraries;

extracting the first symbol tables of the single-architecture static libraries, and updating the reference symbols for the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies;

Decompressing the single-architecture static libraries, and extracting the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

With reference to the second symbol table, modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table;

The target files in the target file list corresponding to each single-architecture static library are recompressed to obtain multiple non-conflicting new single-architecture static libraries, and the new single-architecture static libraries are merged into a new multi-architecture static library.

A second aspect of the present application provides a multi-architecture static library conflict processing apparatus, and the multi-architecture static library conflict processing apparatus includes:

an extraction module, configured to scan each multi-architecture static library respectively, extract a multi-architecture static library list with static library conflicts, and separate each multi-architecture static library in the multi-architecture static library list into a plurality of single-architecture static libraries;

an update module for extracting the first symbol tables of the single-architecture static libraries, and updating the reference symbols for the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies;

a decompression module, used for decompressing the single-architecture static libraries, and extracting the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

a modification module, configured to modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table with reference to the second symbol table;

The compression module is used to recompress the target files in the target file list corresponding to each single-architecture static library, obtain a plurality of non-conflicting new single-architecture static libraries, and merge the new single-architecture static libraries into new multi-architecture static libraries. Architecture static library.

A third aspect of the present application provides a multi-architecture static library conflict processing device, comprising: a memory and at least one processor, where an instruction is stored in the memory; the at least one processor invokes the instruction in the memory, So that the multi-architecture static library conflict processing device executes the steps of the multi-architecture static library conflict processing method as shown below:

A fourth aspect of the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, when the computer-readable storage medium runs on a computer, the computer executes the multi-architecture static library conflict processing method shown below A step of:

In the technical solution provided by the present application, the conflicting multi-architecture static libraries are first separated into single-architecture static libraries. Since there may be interdependencies between the single-architecture static libraries, all the symbol tables of the single-architecture static libraries need to be checked. The reference symbol is updated to get the symbol table with dependencies. Then, according to the symbol table with dependencies, match the object file decompressed from the single-architecture static library, and rename the symbols in the matched object file, so as to solve the symbol conflict between multi-architecture static libraries The problem. The present application uniformly renames the object file symbols in the conflicting multi-architecture static library, thereby efficiently generating a new stable multi-architecture static library.

Description of drawings

1 is a schematic diagram of a first embodiment of a multi-architecture static library conflict processing method in an embodiment of the present application;

2 is a schematic diagram of a second embodiment of a method for handling multi-architecture static library conflicts in an embodiment of the present application;

3 is a schematic diagram of an embodiment of a multi-architecture static library conflict processing apparatus in an embodiment of the present application;

FIG. 4 is a schematic diagram of an embodiment of a multi-architecture static library conflict processing device in an embodiment of the present application.

Detailed ways

Embodiments of the present application provide a method, apparatus, device, and storage medium for dealing with multi-architecture static library conflicts. "Three", "fourth", etc., if present, are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" or "having" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed steps or units, but may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

For ease of understanding, the following describes the specific process of the embodiment of the present application, with reference to FIG. 1 , the first embodiment of the method for handling multi-architecture static library conflicts in the embodiment of the present application includes:

101. Scan each multi-architecture static library respectively, extract a multi-architecture static library list with static library conflicts, and separate each multi-architecture static library in the multi-architecture static library list into multiple single-architecture static libraries;

It can be understood that the execution body of the present application may be a multi-architecture static library conflict processing device, and may also be a terminal or a server, which is not specifically limited here. The embodiments of the present application take the server as an execution subject as an example for description.

In this embodiment, when an iOS/Mac platform application integrates a static library, a conflict may occur between two multi-architecture static libraries, and the functions/class names/global variables exposed by each static library to external use are called the static library's function/class name/global variable. The reason for the conflict is that the names of external symbols are repeated. These external symbols are stored in the symbol table of the Mach-O file of each static library, and the symbol table can be extracted through the command line.

In this embodiment, the static library provided to the application for reference may be composed of several sub-static libraries as the basic unit of compilation, and a static library is composed of compressed object files (.o files). When the application needs to support multiple CPU architectures (such as arm64/armv7/x86_64) to compile, the multi-architecture (Fat) static library is composed of multiple single-architecture (Thin) static libraries packaged. Therefore, if there are several sub-static libraries, the Thin static library needs to be extracted separately for each sub-static library. The Thin static library under different CPU architectures may have differences in code implementation, and the symbol table needs to be processed separately for the single-CPU architecture.

Optionally, in an embodiment, step 101 includes:

Scan each multi-architecture static library separately to confirm that the static library has been integrated and the static library to be integrated;

respectively extracting the fourth symbol table of the integrated static library and the fifth symbol table of the static library to be integrated;

judging whether there are duplicate symbol names between the fourth symbol table and the fifth symbol table;

If it exists, it is determined that there is a static library conflict, and the multi-architecture static library corresponding to the static library conflict is added to the preset list to obtain a multi-architecture static library list;

Each multi-architecture static library in the multi-architecture static library list is separated into a plurality of single-architecture static libraries.

In this optional embodiment, there are two methods for identifying static library conflicts: one is for static libraries provided externally in the form of SDK, and after extracting the overall external symbols of the static library that may have conflicts, perform privatization and naming processing to obtain Conflict-free static library; second, for the internal integration of the application, extract the compiled application main project Mach-O file symbol table, as well as the static library Mach-O file symbol table to be added to the project, and export the external code implemented by the internal code. The symbol list and object file information are checked and compared to confirm that there is a static library where symbols and object files conflict.

102. Extract the first symbol tables of the single-architecture static libraries, and update the reference symbols for the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies;

In this embodiment, there may be an interdependence relationship between the single-architecture static libraries, and this interdependence relationship can be determined by the symbol table of each single-architecture static library. For example, when an undefined external symbol identifier b is found in static library A, and the symbol b is an external symbol implemented by internal code in static library B, that is, symbol b is defined in static library B, then it is considered static Library A depends on static library B. When it is recognized that the static library A depends on the static library B, the symbol table update operation needs to be performed. The specific operation method is to extract the symbol table of the static library B, and export and add it to the symbol table of the static library A. Perform the corresponding symbol table update operation for each static library with external dependencies in turn.

Optionally, in an embodiment, step 102 includes:

extracting the first symbol tables of the single-architecture static libraries, and determining the interdependence between the single-architecture static libraries;

According to the interdependence between the single-architecture static libraries, the reference symbols are updated on the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies.

In this optional embodiment, in order to rename symbols uniformly, it is necessary to update the reference symbols of the internal interdependent static libraries, so that missing symbols are not generated during renaming, and errors are avoided when the integrated static library is subsequently imported. The static library with updated reference symbols is used as the second symbol table with dependencies to match the symbols that need to be modified in the object file.

103. Perform decompression processing on the single-architecture static libraries, and extract the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

In this embodiment, the static library can be simply regarded as a set of object files (.o), that is, a file formed by many object files after being compressed and packaged. For example, the most commonly used C language static library libc is located in /usr/lib/libc.a, which is part of the glibc project. And glibc itself is developed in C language, it consists of hundreds of C language source code files, that is to say, after the compilation is completed, there are the same number of object files, such as printf.o, scanf.o for input and output; File operations include fread.o, fwrite.o; time and date include date.o, time.o; memory management includes malloc.o, etc. Providing these scattered object files directly to the users of the library will cause inconvenience in file transfer, management and organization to a large extent, so the ar compression program is usually used to compress these object files together, and number and organize them. Indexing, to facilitate search and retrieval, forms a static library file. In this embodiment, the static library can be decompressed through the command line: ar-x <library.a/binary>, and several object files and symbol tables corresponding to each object file are extracted from the decompression result.

104. With reference to the second symbol table, modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table;

In this embodiment, after the second symbol table with dependencies is obtained, the symbol tables of each target file are matched according to the symbols in the second symbol table, and the symbols in the second symbol table included in each target file are matched, and the symbols in the second symbol table are matched according to the symbols in the second symbol table. The preset renaming rules modify the matched symbols. In order to integrate the executable of the static library, the size of the symbol structure of the new symbol and the starting address of the memory need to be modified accordingly. In this embodiment, the target file where the symbol to be modified is located is searched out according to the updated symbol table of the reference symbol, so as to rename the conflicting symbol in the target file.

Optionally, in an embodiment, step 104 includes:

Taking each symbol name in the second symbol table as a matching keyword, traverse the third symbol table corresponding to each target file in turn to obtain a matching result;

If the matching result is not empty, modify the symbol name, symbol structure size and memory start address of the matching symbol corresponding to the matching result according to the preset modification rule.

Optionally, in an embodiment, using each symbol name in the second symbol table as a matching keyword, traversing the third symbol table corresponding to each target file in sequence, and obtaining a matching result includes:

S1, take a symbol name of an unmatched symbol in the second symbol table as a matching keyword, and match with a third symbol table corresponding to an unmatched target file to obtain a matching result;

S2, judging whether there is an unmatched symbol in the second symbol table;

S3, if there is an unmatched symbol in the second symbol table, cyclically execute S1-S2;

S4, if there is no unmatched symbol in the second symbol table, then determine whether there is an unmatched target file;

S5. If there is an unmatched target file, execute S1-S4 in a loop;

S6, if there is no unmatched target file, determine whether there is an unmatched second symbol table;

S7. If there is an unmatched second symbol table, cyclically execute S1-S6.

In this optional embodiment, the symbol renaming program needs to perform two-layer traversal. The first layer traverses the target file list corresponding to the CPU architecture, the second layer traverses the symbol table corresponding to the target file, and uses the target file as the modification unit to perform symbol renaming. . When it is judged that the target file has the symbol information that needs to be modified, the old symbol name in the single target file is modified to the new symbol name generated according to the naming rule.

In this optional embodiment, the symbol renaming program judges the CPU architecture type by reading the Mach-O file structure of the target file, skips the HEADER part, searches for the LC_SYMTAB identifier, and obtains the Symbol Table Offset, and the symbol is in units of nlist/nlist_64 (Defined in mach-o/nlist.h), retrieve the matching symbol names in turn, when the symbol to be modified is found, modify the nlist/nlist_64 structure size and n_un.n_strx as the new symbol name, and readjust the symbol The memory start address of the subsequent symbol structure.

Optionally, in one embodiment, if the matching result is not empty, modifying the symbol name, symbol structure size and memory start address of the matching symbol corresponding to the matching result according to a preset modification rule includes:

If the matching result is not empty, add the same modifier symbol before the symbol name of each matching symbol to obtain a plurality of new symbols;

adding the new symbols to the first symbol table corresponding to the single-architecture static library;

Adjust the size of the symbol structure and the starting address of the memory corresponding to each new symbol in the first symbol table of each single-architecture static library.

In this optional embodiment, the symbol modification rule can be in multiple ways. For example, a modified prefix can be added uniformly on the basis of the original symbol to be modified, and the modified prefix can be customized as a unified prefix symbol, such as " _<prefix>". In addition, it is best to implement the same modification rules for all matched symbols, so that the original App application project that directly calls the interface of the newly added module conflicting static library can be used to modify the name of the called class/method/global variable synchronously, for example, Corresponding to the prefix symbol, the "<prefix>_" prefix is added before the original name.

105. Recompress the target files in the target file list corresponding to each single-architecture static library, obtain a plurality of non-conflicting new single-architecture static libraries, and merge the new single-architecture static libraries into a new multi-architecture static library .

In this embodiment, the modified target files are compressed and merged into a single-architecture static library. If there is a single-architecture static library with multiple CPU architectures, the modified single-architecture static library is merged into a multi-architecture static library. When exporting as SDK static library, in order to reduce the workload of external application integration, multiple multi-architecture static libraries will be merged into one static library as much as possible for unified external output. When merging, different single-architecture static libraries will be named with duplicate targets. The file names are renamed and then repackaged into a single multi-arch static library output.

In the embodiment of the present application, the conflicting multi-architecture static libraries are first separated into single-architecture static libraries. Since there may be interdependencies among the single-architecture static libraries, all the symbols need to be referenced to the symbol tables of the single-architecture static libraries. Update to get the symbol table with dependencies. Then, according to the symbol table with dependencies, match the object file decompressed from the single-architecture static library, and rename the symbols in the matched object file, so as to solve the symbol conflict between multi-architecture static libraries The problem. The present application uniformly renames the object file symbols in the conflicting multi-architecture static library, thereby efficiently generating a new stable multi-architecture static library.

Referring to FIG. 2, the second embodiment of the multi-architecture static library conflict processing method in the embodiment of the present application includes:

201. Scan each multi-architecture static library respectively, extract a multi-architecture static library list with static library conflicts, and separate each multi-architecture static library in the multi-architecture static library list into multiple single-architecture static libraries;

202. Extract the first symbol table of each single-architecture static library;

203. Deriving all external symbols in the first symbol tables, and determining the interdependence between the single-architecture static libraries according to the dependency between the external symbols;

204. Screen out a plurality of static library groups with dependent calling relationships from the interdependencies between the single-architecture static libraries, wherein the static library group includes a first static library and a second static library, and all The second static library depends on the first static library;

205, respectively add the symbol table of the first static library in the described each static library group in the symbol table of the second static library, obtain the corresponding second symbol table with dependency of the each single-architecture static library;

In this embodiment, in order to rename symbols uniformly, it is necessary to update the reference symbols of the internal interdependent static libraries, so that no missing symbols are generated during renaming, and errors occur when the integrated static library is subsequently imported. The static library with updated reference symbols is used as the second symbol table with dependencies to match the symbols that need to be modified in the object file.

206, performing decompression processing on the single-architecture static libraries, and extracting the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

207. With reference to the second symbol table, modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table;

208. Recompress the target files in the target file list corresponding to each single-architecture static library, obtain a plurality of non-conflicting new single-architecture static libraries, and merge the new single-architecture static libraries into a new multi-architecture static library .

In the embodiment of the present application, since there may be interdependencies among the single-architecture static libraries, it is necessary to export the external symbol tables of the static libraries for dependency analysis. When an undefined external symbol is found in one static library, and the undefined external symbol has internal code implementation in another static library, then it is determined that the two static libraries are mutually dependent. Then add the defined static library symbol table to the static library symbol table with undefined symbols to obtain the symbol table with dependencies. Through dependency relationship analysis, the embodiment of the present application can comprehensively modify conflicting symbols, thereby avoiding the risk of error reporting caused by omission.

The multi-architecture static library conflict processing method in the embodiment of the present application has been described above, and the multi-architecture static library conflict processing device in the embodiment of the present application is described below. Referring to FIG. 3, the multi-architecture static library conflict processing device in the embodiment of the present application is described. One embodiment includes:

The extraction module 301 is configured to scan each multi-architecture static library respectively, extract a multi-architecture static library list with static library conflicts, and separate each multi-architecture static library in the multi-architecture static library list into a plurality of single-architecture static libraries;

an update module 302, configured to extract the first symbol tables of the single-architecture static libraries, and update the reference symbols of the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies;

The decompression module 303 is configured to perform decompression processing on the single-architecture static libraries, and extract the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

Modifying module 304, configured to modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table with reference to the second symbol table;

The compression module 305 is used to recompress the target files in the target file list corresponding to each single-architecture static library, obtain a plurality of non-conflicting new single-architecture static libraries, and merge the new single-architecture static libraries into a new single-architecture static library. Multi-arch static library.

Optionally, in an embodiment, the extraction module 301 is specifically configured to:

If there is, it is determined that there is a static library conflict, and the multi-architecture static library corresponding to the static library conflict is added to the preset list to obtain a multi-architecture static library list.

Optionally, in an embodiment, the update module 302 is further configured to:

Extract the first symbol table of each single-architecture static library, and determine the interdependence between the single-architecture static libraries;

Optionally, in an embodiment, the update module 302 is further configured to:

Deriving all external symbols in the first symbol tables, and determining the interdependence between the single-architecture static libraries according to the dependency between the external symbols;

From the interdependencies between the single-architecture static libraries, a plurality of static library groups with dependent calling relationships are screened, wherein the static library group includes a first static library and a second static library, and the first static library Two static libraries depend on the first static library;

The symbol table of the first static library in each static library group is respectively added to the symbol table of the second static library to obtain the second symbol table with dependencies corresponding to each of the single-architecture static libraries.

Optionally, in an embodiment, the modifying module 304 includes:

The first modification submodule is used to traverse the third symbol table corresponding to each target file in turn by using each symbol name in the second symbol table as a matching keyword to obtain a matching result;

The second modification sub-module is configured to modify the symbol name, symbol structure size and memory start address of the matching symbol corresponding to the matching result according to a preset modification rule if the matching result is not empty.

Optionally, in an embodiment, the first modification submodule includes:

A matching unit, used for taking a symbol name of an unmatched symbol in the second symbol table as a matching keyword, and matching with a third symbol table corresponding to an unmatched target file to obtain a matching result;

a first judging unit for judging whether there is an unmatched symbol in the second symbol table;

a first circulation unit, for cyclically executing a matching unit and a first judging unit if there is an unmatched symbol in the second symbol table;

a second judging unit, configured to judge whether there is an unmatched target file if there is no unmatched symbol in the second symbol table;

The second circulation unit is used for cyclically executing the matching unit, the first judgment unit, the first circulation unit and the second judgment unit if there is an unmatched target file;

The third judgment unit is used to judge whether there is an unmatched second symbol table if there is no unmatched target file;

The third loop unit is configured to loop through the matching unit, the first judgment unit, the first loop unit, the second judgment unit, the second loop unit and the third judgment unit if there is an unmatched second symbol table.

Optionally, in an embodiment, the second modification submodule is specifically used for:

Before the symbol name of each matching symbol, add the same modifier symbol to obtain multiple new symbols;

Figure 3 above describes the multi-architecture static library conflict processing device in the embodiment of the present application in detail from the perspective of modular functional entities, and the following describes the multi-architecture static library conflict processing device in the embodiment of the present application in detail from the perspective of hardware processing.

FIG. 4 is a schematic structural diagram of a multi-architecture static library conflict processing device provided by an embodiment of the present application. The multi-architecture static library conflict processing device 500 may vary greatly due to different configurations or performances, and may include one or more than one Central processing units (CPU) 510 (eg, one or more processors) and memory 520, one or more storage media 530 (eg, one or more mass storage devices) that store application programs 533 or data 532. Among them, the memory 520 and the storage medium 530 may be short-term storage or persistent storage. The program stored in the storage medium 530 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the multi-architecture static library conflict processing apparatus 500 . Furthermore, the processor 510 may be configured to communicate with the storage medium 530 to execute a series of instruction operations in the storage medium 530 on the multi-architecture static library conflict processing device 500 .

The multi-architecture static library conflict processing device 500 may also include one or more power supplies 540, one or more wired or wireless network interfaces 550, one or more input and output interfaces 560, and/or, one or more operating systems 531, For example Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art can understand that the structure of the multi-architecture static library conflict processing device shown in FIG. 4 does not constitute a limitation on the multi-architecture static library conflict processing device, and may include more or less components than those shown in the figure, or a combination of certain some components, or a different arrangement of components.

The present application also provides a multi-architecture static library conflict processing device, the multi-architecture static library conflict processing device includes a memory and a processor, the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, causes processing The controller executes the steps of the multi-architecture static library conflict processing method in the above embodiments.

The present application also provides a computer-readable storage medium. The computer-readable storage medium may be a non-volatile computer-readable storage medium. The computer-readable storage medium may also be a volatile computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to execute the steps of the multi-architecture static library conflict processing method.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: The technical solutions described in the embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the present application.

Claims

A multi-architecture static library conflict processing method, wherein the multi-architecture static library conflict processing method comprises:

Scanning each multi-architecture static library respectively, extracting a multi-architecture static library list with static library conflicts, and separating each multi-architecture static library in the multi-architecture static library list into a plurality of single-architecture static libraries;

extracting the first symbol tables of the single-architecture static libraries, and updating the reference symbols for the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies;

Decompressing the single-architecture static libraries, and extracting the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

With reference to the second symbol table, modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table;

The target files in the target file list corresponding to each single-architecture static library are recompressed to obtain multiple non-conflicting new single-architecture static libraries, and the new single-architecture static libraries are merged into a new multi-architecture static library.
The method for processing multi-architecture static library conflicts according to claim 1, wherein said scanning each multi-architecture static library separately, and extracting a list of multi-architecture static libraries with static library conflicts includes:

Scan each multi-architecture static library separately to confirm that the static library has been integrated and the static library to be integrated;

respectively extracting the fourth symbol table of the integrated static library and the fifth symbol table of the static library to be integrated;

judging whether there are duplicate symbol names between the fourth symbol table and the fifth symbol table;

If there is, it is determined that there is a static library conflict, and the multi-architecture static library corresponding to the static library conflict is added to the preset list to obtain a multi-architecture static library list.
The multi-architecture static library conflict processing method according to claim 1, wherein the extracting the first symbol table of each single-architecture static library, and referencing the first symbol table of each single-architecture static library Update, get a second symbol table with dependencies including:

extracting the first symbol tables of the single-architecture static libraries, and determining the interdependence between the single-architecture static libraries;

According to the interdependence between the single-architecture static libraries, the reference symbols are updated on the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies.
The multi-architecture static library conflict processing method according to claim 1 or 3, wherein the updating of the reference symbols on the first symbol tables of the single-architecture static libraries to obtain the second symbol table with dependencies comprises:

Deriving all external symbols in the first symbol tables, and determining the interdependence between the single-architecture static libraries according to the dependency between the external symbols;

From the interdependencies between the single-architecture static libraries, a plurality of static library groups with dependent calling relationships are screened, wherein the static library group includes a first static library and a second static library, and the first static library Two static libraries depend on the first static library;

The symbol table of the first static library in each static library group is respectively added to the symbol table of the second static library to obtain the second symbol table with dependencies corresponding to each of the single-architecture static libraries.
The method for handling multi-architecture static library conflicts according to claim 1, wherein, by referring to the second symbol table, modifying the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table include:

Taking each symbol name in the second symbol table as a matching keyword, traverse the third symbol table corresponding to each target file in turn to obtain a matching result;

If the matching result is not empty, modify the symbol name, symbol structure size and memory start address of the matching symbol corresponding to the matching result according to the preset modification rule.
The multi-architecture static library conflict processing method according to claim 5, wherein the third symbol table corresponding to each target file is sequentially traversed by using each symbol name in the second symbol table as a matching keyword, The matching results obtained include:

S1, take a symbol name of an unmatched symbol in the second symbol table as a matching keyword, and match with a third symbol table corresponding to an unmatched target file to obtain a matching result;

S2, judging whether there is an unmatched symbol in the second symbol table;

S3, if there is an unmatched symbol in the second symbol table, cyclically execute S1-S2;

S4, if there is no unmatched symbol in the second symbol table, then determine whether there is an unmatched target file;

S5. If there is an unmatched target file, execute S1-S4 in a loop;

S6, if there is no unmatched target file, determine whether there is an unmatched second symbol table;

S7. If there is an unmatched second symbol table, cyclically execute S1-S6.
The multi-architecture static library conflict processing method according to claim 5, wherein, if the matching result is not empty, modify the symbol name and symbol structure size of the matching symbol corresponding to the matching result according to a preset modification rule And the memory start address includes:

If the matching result is not empty, add the same modifier symbol before the symbol name of each matching symbol to obtain a plurality of new symbols;

adding the new symbols to the first symbol table corresponding to the single-architecture static library;

Adjust the size of the symbol structure and the starting address of the memory corresponding to each new symbol in the first symbol table of each single-architecture static library.
A multi-architecture static library conflict processing device, wherein the multi-architecture static library conflict processing device comprises:

an extraction module, configured to scan each multi-architecture static library respectively, extract a multi-architecture static library list with static library conflicts, and separate each multi-architecture static library in the multi-architecture static library list into a plurality of single-architecture static libraries;

an update module for extracting the first symbol tables of the single-architecture static libraries, and updating the reference symbols for the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies;

a decompression module, used for decompressing the single-architecture static libraries, and extracting the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

a modification module, configured to modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table with reference to the second symbol table;

The compression module is used to recompress the target files in the target file list corresponding to each single-architecture static library, obtain a plurality of non-conflicting new single-architecture static libraries, and merge the new single-architecture static libraries into new multi-architecture static libraries. Architecture static library.
A multi-architecture static library conflict processing device, wherein the multi-architecture static library conflict processing device includes: a memory and at least one processor;

The at least one processor invokes the instructions in the memory, so that the multi-architecture static library conflict processing device executes the steps of the multi-architecture static library conflict processing method as follows:

Scanning each multi-architecture static library respectively, extracting a multi-architecture static library list with static library conflicts, and separating each multi-architecture static library in the multi-architecture static library list into a plurality of single-architecture static libraries;

extracting the first symbol tables of the single-architecture static libraries, and updating the reference symbols for the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies;

Decompressing the single-architecture static libraries, and extracting the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

With reference to the second symbol table, modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table;

The target files in the target file list corresponding to each single-architecture static library are recompressed to obtain multiple non-conflicting new single-architecture static libraries, and the new single-architecture static libraries are merged into a new multi-architecture static library.
The multi-architecture static library conflict processing device according to claim 9, wherein the multi-architecture static library conflict processing device is executed by the processor to scan each multi-architecture static library separately, and extract the multi-architectures with static library conflicts When listing the static libraries, the steps include:

Scan each multi-architecture static library separately to confirm that the static library has been integrated and the static library to be integrated;

respectively extracting the fourth symbol table of the integrated static library and the fifth symbol table of the static library to be integrated;

judging whether there are duplicate symbol names between the fourth symbol table and the fifth symbol table;

If there is, it is determined that there is a static library conflict, and the multi-architecture static library corresponding to the static library conflict is added to the preset list to obtain a multi-architecture static library list.
The multi-architecture static library conflict processing device according to claim 9, wherein the multi-architecture static library conflict processing device is executed by the processor to extract the first symbol table of each single-architecture static library, and perform the extraction of the first symbol table of each single-architecture static library. When the first symbol table of each single-architecture static library is updated with reference symbols to obtain the second symbol table with dependencies, the steps include:

extracting the first symbol tables of the single-architecture static libraries, and determining the interdependence between the single-architecture static libraries;

According to the interdependencies among the single-architecture static libraries, the reference symbols are updated to the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies.
The multi-architecture static library conflict processing device according to claim 9 or 11, wherein the multi-architecture static library conflict processing device is executed by the processor to perform the processing on the first symbol tables of the single-architecture static libraries. When referencing symbol update, the steps to obtain the second symbol table with dependencies include:

Deriving all external symbols in the first symbol tables, and determining the interdependence between the single-architecture static libraries according to the dependency between the external symbols;

From the interdependencies between the single-architecture static libraries, a plurality of static library groups with dependent calling relationships are screened, wherein the static library group includes a first static library and a second static library, and the first static library Two static libraries depend on the first static library;

The symbol table of the first static library in each static library group is respectively added to the symbol table of the second static library to obtain the second symbol table with dependencies corresponding to each of the single-architecture static libraries.
The multi-architecture static library conflict processing device according to claim 9, wherein the multi-architecture static library conflict processing device is executed by the processor to refer to the second symbol table and modify the third symbol table. The steps corresponding to the symbol name, symbol structure size and memory start address of the symbol include:

Taking each symbol name in the second symbol table as a matching keyword, traverse the third symbol table corresponding to each target file in turn to obtain a matching result;

If the matching result is not empty, modify the symbol name, symbol structure size and memory start address of the matching symbol corresponding to the matching result according to the preset modification rule.
The multi-architecture static library conflict processing device according to claim 13 , wherein the multi-architecture static library conflict processing device is executed by the processor and uses each symbol name in the second symbol table as a matching keyword. , traverse the third symbol table corresponding to each target file in turn, and the steps of obtaining a matching result include:

S1, take a symbol name of an unmatched symbol in the second symbol table as a matching keyword, and match with a third symbol table corresponding to an unmatched target file to obtain a matching result;

S2, judging whether there is an unmatched symbol in the second symbol table;

S3, if there is an unmatched symbol in the second symbol table, cyclically execute S1-S2;

S4, if there is no unmatched symbol in the second symbol table, then determine whether there is an unmatched target file;

S5. If there is an unmatched target file, execute S1-S4 cyclically;

S6, if there is no unmatched target file, determine whether there is an unmatched second symbol table;

S7. If there is an unmatched second symbol table, cyclically execute S1-S6.
The multi-architecture static library conflict processing device according to claim 13, wherein the multi-architecture static library conflict processing device is executed by the processor, and if the matching result is not empty, modifying the device according to a preset modification rule When the matching result corresponds to the symbol name, symbol structure size and memory start address of the matching symbol, the steps include:

If the matching result is not empty, add the same modifier symbol before the symbol name of each matching symbol to obtain a plurality of new symbols;

adding the new symbols to the first symbol table corresponding to the single-architecture static library;

Adjust the size of the symbol structure and the starting address of the memory corresponding to each new symbol in the first symbol table of each single-architecture static library.
A computer-readable storage medium storing instructions on the computer-readable storage medium, wherein when the instructions are executed by a processor, the steps of the multi-architecture static library conflict processing method described below are implemented:

Scanning each multi-architecture static library respectively, extracting a multi-architecture static library list with static library conflicts, and separating each multi-architecture static library in the multi-architecture static library list into a plurality of single-architecture static libraries;

extracting the first symbol tables of the single-architecture static libraries, and updating the reference symbols for the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies;

Decompressing the single-architecture static libraries, and extracting the target file list of each single-architecture static library and the third symbol table corresponding to each target file from the decompression result;

With reference to the second symbol table, modify the symbol name, symbol structure size and memory start address of the corresponding symbol in the third symbol table;

The target files in the target file list corresponding to each single-architecture static library are recompressed to obtain multiple non-conflicting new single-architecture static libraries, and the new single-architecture static libraries are merged into a new multi-architecture static library.
The computer-readable storage medium according to claim 16, wherein the instruction for processing the multi-architecture static library conflict is executed by the processor to scan each multi-architecture static library separately, and extract the multi-architecture static library conflict with the static library. When listing the steps in the library, include:

Scan each multi-architecture static library separately to confirm that the static library has been integrated and the static library to be integrated;

respectively extracting the fourth symbol table of the integrated static library and the fifth symbol table of the static library to be integrated;

Judging whether there are duplicate symbol names between the fourth symbol table and the fifth symbol table;

If it exists, it is determined that there is a static library conflict, and the multi-architecture static library corresponding to the static library conflict is added to the preset list to obtain a multi-architecture static library list.
17. The computer-readable storage medium of claim 16, wherein the multi-architecture static library conflict handling instructions are executed by the processor to extract the first symbol table of each single-architecture static library, and perform a When the first symbol table of each single-architecture static library is described to update the reference symbols to obtain the second symbol table with dependencies, the steps include:

extracting the first symbol tables of the single-architecture static libraries, and determining the interdependence between the single-architecture static libraries;

According to the interdependencies among the single-architecture static libraries, the reference symbols are updated to the first symbol tables of the single-architecture static libraries to obtain a second symbol table with dependencies.
The computer-readable storage medium of claim 16 or 18, wherein the instructions for multi-architecture static library conflict handling are executed by the processor to reference the first symbol table of each single-architecture static library When symbols are updated, the steps to obtain the second symbol table with dependencies include:

Deriving all external symbols in the first symbol tables, and determining the interdependence between the single-architecture static libraries according to the dependency between the external symbols;

From the interdependencies between the single-architecture static libraries, a plurality of static library groups with dependent calling relationships are screened, wherein the static library group includes a first static library and a second static library, and the first static library Two static libraries depend on the first static library;

The symbol table of the first static library in each static library group is respectively added to the symbol table of the second static library, so as to obtain a second symbol table with dependencies corresponding to each of the single-architecture static libraries.
The computer-readable storage medium according to claim 16, wherein the instruction of the multi-architecture static library conflict handling is executed by the processor by referring to the second symbol table, and modifying the corresponding data in the third symbol table. The steps for the symbol name, symbol structure size, and memory start address of the symbol include:

Taking each symbol name in the second symbol table as a matching keyword, traverse the third symbol table corresponding to each target file in turn to obtain a matching result;

If the matching result is not empty, modify the symbol name, symbol structure size and memory start address of the matching symbol corresponding to the matching result according to the preset modification rule.