Software integration method and tool, electronic equipment and storage medium

Abstract

The invention provides a software integration method and tool, and the method comprises the steps: obtaining module code files in underlying software engineering, compiling the module code file in each module to generate a module HEX file, compiling the module code files participating in compiling to generate a module LIB file, integrating the module HEX files of all the modules into an underlying HEX file, and integrating the underlying HEX file with the module HEX file. Integrating the module LIB files of all the modules into a bottom layer LIB file; obtaining an application layer code file in the integrated software engineering, compiling the application layer code file to generate an application layer HEX file, and compiling a module code file recorded in the user interface file to generate a bottom layer interface HEX file; and generating an integrated HEX file from an application layer HEX file, the bottom layer interface HEX file and the bottom layer LIB file. The technical problems that in the prior art, efficiency is low and errors cannot be avoided due to the fact that an integrated project is generated through an editing tool during project development are solved.

Description

Technical Field

[0001] The present invention relates to the field of software, and in particular to a software integration method, tool, electronic device and storage medium. Background Art

[0002] In the prior art, platform-based electric drive controller software integration has the following problems: The compilation tool can only manually add a single code file to participate in the compilation to generate HEX files and library files. However, a complete software project usually has thousands of code files, and this integration method is inefficient.

[0003] At present, the iterative process of distributed software development requires multiple integration of software modules and generation of library files. The manual integration method is inefficient on the one hand, and it is difficult to ensure the quality of the integration work on the other hand. When the structure of the software project changes, the link relationship between the underlying software project, the integrated software project and the library file project needs to be redeveloped, which is a huge workload. Summary of the invention

[0004] Based on the above problems, the present invention proposes a software integration method, tool, electronic device, storage medium and computer program product. The present invention solves the technical problems of low efficiency and inability to avoid mistakes caused by the editing tool used in the prior art to develop a project to configure a single code file, manually establish a GPJ project link code file, compile software and generate library files, and finally use a manual comparison method to generate an integrated project. The software integration method provided by the present invention can quickly implement compilation with one click without manual operation, which improves efficiency while avoiding mistakes caused by manual operation.

[0005] The present invention provides a software integration method, comprising: In response to external input, if the external input is the first option, then module code files corresponding to multiple different modules in the underlying software engineering are obtained, a user interface file is obtained, the user interface file records the module code files that are not involved in the compilation in each module, the module code files in each module are compiled to generate a module HEX file, the module code files that are not involved in the compilation are excluded according to the user interface file, the module code files that are involved in the compilation in each module are compiled to generate a module LIB file, the module HEX files of all modules are integrated into the underlying HEX file, and the module LIB files of all modules are integrated into the underlying LIB file; If the second option is input externally, the application layer code file is obtained in the integrated software project and compiled to generate an application layer HEX file, and the module code file recorded in the user interface file is compiled to generate an underlying interface HEX file; the application layer HEX file, the underlying interface HEX file and the underlying LIB file are generated into an integrated HEX file, and the underlying HEX file and the integrated HEX file are used to burn into the chip.

[0006] In addition, the obtaining of module code files corresponding to multiple different modules in the underlying software engineering includes: The module code files corresponding to a plurality of different modules in the underlying software project are obtained according to the predefined relative paths of the module code files, wherein the root path of the relative path is defined according to the path of the underlying software project.

[0007] In addition, compiling the module code files in each module to generate a module HEX file, excluding the module code files that do not participate in the compilation according to the user interface file, and compiling the module code files that participate in the compilation in each module to generate a module LIB file includes: Create a HEX_GPJ project and a LIB_GPJ project, add the module code file to the HEX_GPJ project for compilation to generate the module HEX file, exclude the module code files that do not participate in the compilation according to the user interface file, add the module code files that participate in the compilation to the LIB_GPJ project for compilation to generate the module LIB file.

[0008] In addition, the method of compiling the module code files in each module to generate a module HEX file, excluding the module code files not involved in the compilation according to the user interface file, and compiling the module code files involved in the compilation in each module to generate a module LIB file also includes: The folder information corresponding to each module is collected as a folder tree, and the module HEX file and module LIB file corresponding to each module are found through the path information provided by the folder tree.

[0009] In addition, compiling the module code files recorded in the user interface file to generate the underlying interface HEX file includes: obtaining the module code files that do not participate in the compilation in each module from the underlying software project and copying them to the underlying interface folder of the integrated software project, and obtaining the module code files that do not participate in the compilation in each module from the underlying interface folder and compiling them to generate the underlying interface HEX file.

[0010] In addition, the method further includes responding to a third option input from the outside to sequentially execute instructions corresponding to the first option and the second option.

[0011] The present invention further provides a software integration tool, which adopts the software integration method as described in any one of the above items, comprising: Provides an operation interface that provides multiple compilation options.

[0012] The present invention also provides an electronic device, comprising: at least one processor; and, a memory communicatively connected to at least one of the processors; wherein, The memory stores instructions that can be executed by at least one of the processors. The instructions are executed by at least one of the processors to enable the at least one processor to perform any of the software integration methods described above.

[0013] The present invention also proposes a storage medium, wherein the storage medium stores computer instructions, and when a computer executes the computer instructions, it is used to execute all the steps of the software integration method as described in any one of the above items.

[0014] The present invention also proposes a computer program product, comprising a computer program / instruction, wherein the computer program / instruction implements the software integration method as described in any one of the above items when executed by a processor.

[0015] The present invention solves the technical problems of low efficiency and inability to avoid mistakes caused by the editing tool used in the prior art to configure a single code file when developing a project, manually establish a GPJ project link code file, compile software and generate library files, and finally use a manual comparison method to generate an integrated project. The software integration method provided by the present invention can quickly implement compilation with one click without manual operation, which improves efficiency and avoids mistakes caused by manual operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A flowchart of a software integration method provided by one embodiment of the present invention; Figure 2 A software engineering schematic diagram of a software integration method provided by one embodiment of the present invention; Figure 3 A schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0017] The present invention is further described in detail below in conjunction with specific embodiments and drawings. It is only intended to elaborate on the specific embodiments of the present invention and does not impose any limitation on the present invention. The protection scope of the present invention shall be subject to the claims.

[0018] The present invention is further described in detail below in conjunction with specific embodiments and drawings. It is only intended to elaborate on the specific embodiments of the present invention and does not impose any limitation on the present invention. The protection scope of the present invention shall be subject to the claims.

[0019] Reference Figure 1 The present invention proposes a software integration method, comprising: Step S101, in response to external input, if the external input is the first option, then sequentially execute steps S102 to S103, obtain module code files corresponding to multiple different modules in the underlying software engineering, obtain a user interface file, the user interface file records the module code files that do not participate in the compilation in each module, compile the module code files in each module to generate a module HEX file, exclude the module code files that do not participate in the compilation according to the user interface file, compile the module code files that participate in the compilation in each module to generate a module LIB file, integrate the module HEX files of all modules into the underlying HEX file, and integrate the module LIB files of all modules into the underlying LIB file; Step S102, if the second option is input externally, then execute step S104 and step S105 in sequence, obtain the application layer code file in the integrated software project and compile to generate the application layer HEX file, compile the module code file recorded in the user interface file to generate the underlying interface HEX file; generate an integrated HEX file from the application layer HEX file, the underlying interface HEX file and the underlying LIB file, and the underlying HEX file and the integrated HEX file are used to burn into the chip.

[0020] In the prior art, the electric drive controller software mainly uses the microcontroller unit MCU (Micro controller Unit) as the carrier, and uses C language to develop various logical functions. To convert the C language logic into an executable HEX file that can be run by the controller, the following steps are required: 1. Compile the code: compile the C file to generate one or more intermediate files. 2. Link: merge the generated intermediate file with the necessary library file to generate an executable file. In order to improve the development efficiency and software reusability of the controller software, the code is divided into application layer code and underlying software code, where the application layer code is used to implement the logical calculation function, and the underlying software code is used to implement the hardware control and signal interaction function. When the controller hardware does not change, only the application layer code can be modified to achieve different functions, that is, various controllers are developed with the underlying software as the base platform. The underlying software code contains multiple modules such as communication, diagnosis, and complex drive, which are usually developed by multiple engineers, and then integrated into a bottom-level software project by an integration engineer, and the link relationship is developed, so that the underlying HEX file can be compiled. After debugging and verifying the underlying HEX file, the application layer code needs to be integrated. The underlying software engineering needs to reserve a part of the underlying interface source code that the application layer needs to call, and package the remaining code that the application layer does not need to call into a library file to prevent tampering. The interface source code, library files and application layer code in the underlying software engineering are integrated into an integrated software engineering. Similarly, the final HEX file can be successfully generated only after the link relationship is developed. The HEX file is used to burn into the chip.

[0021] In order to enable the compilation of underlying code engineering and integrated code engineering to be completed with one click, the present invention provides a software integration method, wherein the module code files recorded in the user interface file provide options for compilers, and the options include, in addition to the first option and the second option, multiple other options may also be included, such as a third option that integrates the corresponding functions of the first option and the second option, and an option of only compiling the user interface file may also be provided, which is used to compile the module code files recorded in the user interface file to generate an underlying interface HEX file, and an option of only compiling the application layer code file may also be provided, which is used to compile the application layer code to generate an application layer HEX file, and an option of only compiling the underlying LIB file may also be provided, which is used to compile the module code files involved in the compilation in each module to generate a module LIB file, and then integrate the module LIB files of all modules into an underlying LIB file.

[0022] If you only need to compile the underlying code, select the first option. When the software integration method detects that the external input is the first option, obtain the module code files corresponding to multiple different modules in the underlying software project, compile the module code files in each module to generate module HEX files, compile the module code files involved in the compilation in each module to generate module LIB files, integrate the module HEX files of all modules into the underlying HEX files, integrate the module LIB files of all modules into the underlying LIB files, and pre-write the module code files that do not participate in the compilation in each module into the user interface file, and exclude the module code files that do not participate in the compilation according to the user interface file. The first option corresponds to compiling the code files in the underlying software project. When the module code files in the underlying software project change, increase or decrease, the compiler can recompile the underlying software project with one click to prepare for the integration of the application layer.

[0023] If the external input is the second option, the application layer code file is obtained in the integrated software project and compiled to generate the application layer HEX file, and the module code file recorded in the user interface file is compiled to generate the underlying interface HEX file; the application layer HEX file, the underlying interface HEX file and the underlying LIB file are used to generate an integrated HEX file, and the underlying HEX file and the integrated HEX file are used to burn into the chip. The second option corresponds to compiling the code in the integrated software project, that is, the code that mainly processes the application layer. When the application layer code file is changed, increased or reduced, the compiler can recompile the integrated software project with one click to obtain a new burned-in file.

[0024] The underlying software engineering and the integrated software engineering are compiled separately, so that the underlying software engineering provides the application layer with the module code files recorded in the underlying LIB files and the user interface files, so that the application layer does not modify the original code files when calling the codes in the underlying software engineering.

[0025] There is no limit to the number of modules in the underlying software engineering here, and it can be continuously increased.

[0026] Reference Figure 2 , giving examples of direct engineering schematics of underlying software engineering and integrated software engineering.

[0027] At S1, the main GPJ project is automatically generated based on the module code folder.

[0028] At S2, the module code files that are not involved in the compilation are automatically retained according to the configuration and copied to the integrated software engineering in the form of source files. The source files and the underlying LIB files are provided to the integrated software engineering for use.

[0029] At S3, the underlying LIB files are generated and copied to the integrated software project.

[0030] At S4, the underlying HEX file is automatically generated.

[0031] The present invention solves the technical problems of low efficiency and inability to avoid mistakes caused by the editing tool used in the prior art to configure a single code file when developing a project, manually establish a GPJ project link code file, compile software and generate library files, and finally use a manual comparison method to generate an integrated project. The software integration method provided by the present invention can quickly implement compilation with one click without manual operation, which improves efficiency and avoids mistakes caused by manual operation.

[0032] In one embodiment, obtaining module code files corresponding to multiple different modules in the underlying software project includes: The module code files corresponding to multiple different modules in the underlying software project are obtained according to the relative path of the predefined module code files, and the root path of the relative path is defined according to the path of the underlying software project.

[0033] The module code files corresponding to different modules are processed to generate relative paths based on the underlying software project, ensuring that in the case of distributed software development, the underlying software projects on different computers can be linked to the corresponding module code files according to the relative paths.

[0034] Optionally, based on the suffix of the module code file, record the names and directories of all module code files involved in the compilation and collect them as doc_list, and replace the absolute paths of all module code files in doc_list with relative paths, so as to ensure that in the case of distributed software development, different computers can be linked to the corresponding module code files according to the relative paths.

[0035] In one embodiment, compiling the module code files in each module to generate a module HEX file, excluding the module code files not involved in the compilation according to the user interface file, and compiling the module code files involved in the compilation in each module to generate a module LIB file includes: Create HEX_GPJ project and LIB_GPJ project, add module code files to HEX_GPJ project for compilation to generate module HEX files, exclude module code files that do not participate in compilation according to user interface files, and add module code files that participate in compilation to LIB_GPJ project for compilation to generate module LIB files.

[0036] In order to meet the needs of distributed development, the module code files in each module are compiled to generate module HEX files, the module code files involved in the compilation in each module are compiled to generate module LIB files, and then all module HEX files are linked to generate underlying HEX files, and all module LIB files are linked to generate underlying LIB files. First, the module HEX file and module LIB file are generated separately for each module, so that when one of the modules is changed, increased or reduced, the module HEX file and module LIB file can be regenerated for this module, and it is also for the underlying software engineering to be able to link the various module HEX files and module LIB files in order when generating the underlying HEX files and underlying LIB files.

[0037] Optionally, the folder information corresponding to each module is collected as dir_list, and each module HEX file and module LIB file are found through the path information provided by dir_list.

[0038] Optionally, in the previous work, preparations are made. First, according to the suffix of the module code file, the names and directories of all module code files involved in the compilation are recorded and collected as doc_list. The absolute paths of all module code files in doc_list are replaced with relative paths. Create a GPJ main project, link all module HEX files through the GPJ main project to generate underlying HEX files, and link all module LIB files to generate underlying LIB files. The specific steps are as follows: add the module code files in doc_list to the sub-GPJ project corresponding to the module to participate in the compilation and linking. The HEX sub-GPJ project will add all files, and the LIB sub-GPJ project will remove the module code files listed in the user interface file User.txt (also known as USER.TXT) to ensure that the module code files that need to be modified in the application layer do not participate in the generation of library files. Add the header file directory in the module code file to the GPJ main project. After the configuration of the GPJ main project is completed, the underlying HEX file and the underlying LIB file can be compiled and generated. In one embodiment, the module code files in each module are compiled to generate a module HEX file, the module code files not involved in the compilation are excluded according to the user interface file, and the module code files involved in the compilation in each module are compiled to generate a module LIB file, and further includes: The folder information corresponding to each module is collected as a folder tree, and the module HEX file and module LIB file corresponding to each module are found through the path information provided by the folder tree.

[0039] The folder information corresponding to each module is collected as a folder tree, and the module HEX file and module LIB file corresponding to each module are found through the path information provided by the folder tree, which improves the search efficiency and provides a basis for one-click search.

[0040] In one embodiment, the folder information corresponding to each module is collected as a folder tree, and the module HEX file and module LIB file corresponding to each module are found through the path information provided by the folder tree. The folder information corresponding to each module is collected as a folder tree, i.e., dir_list, and each module HEX file and module LIB file are found through the path information provided by dir_list.

[0041] In one embodiment, compiling the module code files recorded in the user interface file to generate the underlying interface HEX file includes: obtaining the module code files that do not participate in the compilation in each module from the underlying software project and copying them to the underlying interface folder of the integrated software project, and obtaining the module code files that do not participate in the compilation in each module from the underlying interface folder and compiling them to generate the underlying interface HEX file.

[0042] Find the bottom interface folder in the created integrated software project. If not found, create a bottom interface folder, obtain the module code files that do not participate in the compilation in each module in the bottom software project and copy them to the bottom interface folder of the integrated software project. The module code files in the bottom interface folder are provided to the application layer, and the application layer can modify them according to its own needs. By providing the modifiable module code files to the application layer, the application layer can only modify its related code files, and will not modify or misoperate other bottom files.

[0043] In one embodiment, a third option is further included in response to external input, and the third option includes instructions of the first option and the second option.

[0044] Obtain module code files corresponding to multiple different modules in the underlying software engineering, compile the module code files in each module to generate module HEX files, compile the module code files involved in the compilation in each module to generate module LIB files, integrate the module HEX files of all modules into underlying HEX files, integrate the module LIB files of all modules into underlying LIB files, pre-write the module code files that do not participate in the compilation in each module into the user interface file, and exclude the module code files that do not participate in the compilation according to the user interface file; obtain the application layer code files in the integrated software engineering and compile them to generate application layer HEX files, compile the module code files recorded in the user interface file to generate underlying interface HEX files; generate an integrated HEX file from the application layer HEX file, the underlying interface HEX file and the underlying LIB file, and the underlying HEX file and the integrated HEX file are used to burn into the chip.

[0045] Through one-click operation, the compilation and linking of the underlying software engineering and the integrated software engineering are realized, and the underlying HEX file and the integrated HEX file are directly generated.

[0046] In one embodiment, a software integration method is also proposed, including: Obtain module code files corresponding to multiple different modules in the underlying software engineering, compile the module code files in each module to generate module HEX files, compile the module code files involved in the compilation in each module to generate module LIB files, integrate the module HEX files of all modules into the underlying HEX files, integrate the module LIB files of all modules into the underlying LIB files, pre-write the module code files that do not participate in the compilation in each module into the user interface file, and exclude the module code files that do not participate in the compilation according to the user interface file; The bottom layer HEX file is used to burn into the chip, and the bottom layer LIB file, the user interface file and the module code file recorded in the user interface file are provided for use in the integrated software engineering. The software integration method provided by the present invention can quickly implement compilation with one click.

[0047] In one embodiment, an application layer software integration method is also proposed, including: Obtain the application layer code file in the integrated software project and compile it to generate the application layer HEX file, compile the module code file recorded in the user interface file to generate the underlying interface HEX file; generate the integrated HEX file from the application layer HEX file, the underlying interface HEX file and the underlying LIB file, and the integrated HEX file is used to burn into the chip; The underlying LIB file, the user interface file, and the module code file recorded in the user interface file are obtained from the underlying software project.

[0048] The software integration method provided by the present invention can quickly implement compilation with one click.

[0049] The present invention further provides a software integration tool, which adopts any of the software integration methods described above, and comprises: Provides an operation interface that provides multiple compilation options.

[0050] The present invention solves the technical problems of low efficiency and inability to avoid mistakes caused by the editing tool used in the prior art to configure a single code file when developing a project, manually establish a GPJ project link code file, compile software and generate library files, and finally use a manual comparison method to generate an integrated project. The software integration method provided by the present invention can quickly implement compilation with one click without manual operation, which improves efficiency and avoids mistakes caused by manual operation.

[0051] Reference Figure 3 The present invention also provides a hardware structure diagram of an electronic device, including: at least one processor 301; and, A memory 302 is communicatively connected to at least one of the processors 301; wherein, The memory 302 stores instructions that can be executed by at least one processor. The instructions are executed by the at least one processor so that the at least one processor can perform the above software integration method.

[0052] Figure 3 A processor 301 is taken as an example.

[0053] The electronic device is preferably a controller of the vehicle. The electronic device may further include: an input device 303 and a display device 304 .

[0054] The processor 301, the memory 302, the input device 303 and the display device 304 may be connected via a bus or other means, and the figure takes the connection via a bus as an example.

[0055] The memory 302 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions / modules corresponding to the software integration method in the embodiment of the present application, for example, Figure 2 The processor 301 executes various functional applications and data processing by running the non-volatile software programs, instructions and modules stored in the memory 302, that is, the software integration method in the above embodiment is implemented.

[0056] The memory 302 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required by at least one function; the data storage area may store data created according to the use of the software integration method, etc. In addition, the memory 302 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 302 may optionally include a memory remotely arranged relative to the processor 301, and these remote memories may be connected to the device for executing the software integration method via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0057] The input device 303 can receive user clicks and generate signal inputs related to user settings and function control of the software integration method. The display device 304 can include display devices such as a display screen.

[0058] One or more modules are stored in the memory 302 and when executed by one or more processors 301 , the software integration method in any of the above method embodiments is executed.

[0059] The present invention solves the technical problems of low efficiency and inability to avoid mistakes caused by the editing tool used in the prior art to configure a single code file when developing a project, manually establish a GPJ project link code file, compile software and generate library files, and finally use a manual comparison method to generate an integrated project. The software integration method provided by the present invention can quickly implement compilation with one click without manual operation, which improves efficiency and avoids mistakes caused by manual operation.

[0060] An embodiment of the present invention provides a storage medium, which stores computer instructions. When a computer executes the computer instructions, it is used to execute all the steps of the software integration method as described above.

[0061] In the context of the present disclosure, a storage medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or apparatus. The storage medium may be a machine-readable signal medium or a machine-readable storage medium. Alternatively, the storage medium may be a non-temporary computer-readable storage medium, for example, a non-temporary computer-readable storage medium may be a ROM, a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0062] An embodiment of the present invention provides a computer program product, including a computer program / instruction, which implements the software integration method as described above when executed by a processor.

[0063] The above description is only the principle and preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this field, several other modifications can be made based on the principle of the present invention, which should also be considered as the protection scope of the present invention.

[0064] The above description is only the principle and preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this field, several other modifications can be made based on the principle of the present invention, which should also be considered as the protection scope of the present invention.

Claims

1. A software integration method, characterized in that: include: In response to external input, if the external input is the first option, then module code files corresponding to multiple different modules in the underlying software engineering are obtained, a user interface file is obtained, the user interface file records the module code files that are not involved in the compilation in each module, the module code files in each module are compiled to generate a module HEX file, the module code files that are not involved in the compilation are excluded according to the user interface file, the module code files that are involved in the compilation in each module are compiled to generate a module LIB file, the module HEX files of all modules are integrated into the underlying HEX file, and the module LIB files of all modules are integrated into the underlying LIB file; If the second option is input externally, the application layer code file is obtained in the integrated software project and compiled to generate an application layer HEX file, and the module code file recorded in the user interface file is compiled to generate an underlying interface HEX file; the application layer HEX file, the underlying interface HEX file and the underlying LIB file are generated into an integrated HEX file, and the underlying HEX file and the integrated HEX file are used to burn into the chip.

2. The software integration method according to claim 1, characterized in that: The obtaining of module code files corresponding to multiple different modules in the underlying software engineering includes: The module code files corresponding to a plurality of different modules in the underlying software project are obtained according to the predefined relative paths of the module code files, wherein the root path of the relative path is defined according to the path of the underlying software project.

3. The software integration method according to claim 1, characterized in that: The method of compiling the module code files in each module to generate a module HEX file, excluding the module code files not involved in the compilation according to the user interface file, and compiling the module code files involved in the compilation in each module to generate a module LIB file includes: Create a HEX_GPJ project and a LIB_GPJ project, add the module code file to the HEX_GPJ project for compilation to generate the module HEX file, exclude the module code files that do not participate in the compilation according to the user interface file, add the module code files that participate in the compilation to the LIB_GPJ project for compilation to generate the module LIB file.

4. The software integration method according to claim 3, characterized in that: The method of compiling the module code files in each module to generate a module HEX file, excluding the module code files not involved in the compilation according to the user interface file, and compiling the module code files involved in the compilation in each module to generate a module LIB file also includes: The folder information corresponding to each module is collected as a folder tree, and the module HEX file and module LIB file corresponding to each module are found through the path information provided by the folder tree.

5. The software integration method according to claim 1, characterized in that: The compiling of the module code files recorded in the user interface file to generate the underlying interface HEX file includes: obtaining the module code files that do not participate in the compilation in each module from the underlying software project and copying them to the underlying interface folder of the integrated software project, and obtaining the module code files that do not participate in the compilation in each module from the underlying interface folder and compiling them to generate the underlying interface HEX file.

6. The software integration method according to any one of claims 1 to 5, characterized in that: The method also includes responding to a third option input from the outside to sequentially execute instructions corresponding to the first option and the second option.

7. A software integration tool, characterized in that: The software integration method according to any one of claims 1 to 6 comprises: An operation interface is provided, wherein the operation interface provides multiple compilation options.

8. An electronic device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to at least one of the processors; wherein, The memory stores instructions that can be executed by at least one of the processors, and the instructions are executed by at least one of the processors to enable at least one of the processors to execute the software integration method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium stores computer instructions, and when a computer executes the computer instructions, it is used to execute all steps of the software integration method according to any one of claims 1 to 6.

10. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instruction is executed by a processor, the software integration method as described in any one of claims 1 to 6 is implemented.

Images