Software integration method, tool, electronic device, and storage medium

Abstract

The application provides a software integration method and tool, which comprises the following steps: obtaining module code files in a bottom software engineering, compiling the module code files in each module to generate module HEX files, compiling the module code files participating in the compilation to generate module LIB files, integrating the module HEX files of all modules to generate a bottom HEX file, and integrating the module LIB files of all modules to generate a bottom LIB file; obtaining application layer code files in an integrated software engineering and compiling the application layer code files to generate an application layer HEX file, and compiling module code files recorded in the user interface file to generate a bottom interface HEX file; and generating an integrated HEX file by using the application layer HEX file, the bottom interface HEX file and the bottom LIB file. The application solves the technical problem of low efficiency and inability to avoid mistakes caused by the method of generating an integrated engineering by using an editing tool in the prior art.

Description

TECHNICAL FIELD

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

[0002] In the prior art, the platformized electric drive controller software integration has the following problems:

[0003] The compiling tool can only add single code files to participate in compiling to generate HEX files and library files in a manual manner, however, a complete software engineering usually has several thousand code files, and such integration manner is inefficient.

[0004] In the current distributed software development iteration process, the integration of software modules and the generation of library files need to be performed multiple times, and the manual integration manner is inefficient and difficult to guarantee the quality of the integration work, and when the structure of the software engineering changes, the linking relationship of the underlying software engineering, the integrated software engineering and the library file engineering needs to be redeveloped, and the workload is extremely large. SUMMARY

[0005] Based on the above problems, the present application provides a software integration method, a tool, an electronic device, a storage medium and a computer program product. The present application solves the technical problem that the editing tool used in the development project in the prior art configures single code files, manually establishes GPJ engineering to link code files, compiles software and generates library files, and finally generates an integrated engineering in a manual manner, which is inefficient and cannot avoid mistakes. The software integration method provided by the present application can quickly realize one-key compilation without manual operation, which improves the efficiency and avoids mistakes caused by manual operation.

[0006] The present application provides a software integration method, comprising:

[0007] In response to an external input, if the external input is a first option, a plurality of module code files corresponding to different modules in an underlying software engineering are obtained, a user interface file is obtained, the user interface file records module code files in each module that do not participate in compilation, the module code files in each module are compiled to generate a module HEX file, the module code files that do not participate in compilation are excluded according to the user interface file, the module code files that participate in compilation in each module are compiled to generate a module LIB file, the module HEX files of all modules are integrated into an underlying HEX file, and the module LIB files of all modules are integrated into an underlying LIB file.

[0008] If a second option is inputted externally, application layer code files are acquired in the integrated software engineering and compiled to generate application layer HEX files, and module code files recorded in the user interface file are compiled to generate bottom layer interface HEX files; the application layer HEX files, the bottom layer interface HEX files and the bottom layer LIB files are generated into integrated HEX files, and the bottom layer HEX files and the integrated HEX files are used for burning into chips.

[0009] In addition, the acquiring of the module code files corresponding to the plurality of different modules in the bottom layer software engineering comprises:

[0010] The module code files corresponding to the plurality of different modules in the bottom layer software engineering are acquired according to the pre-defined relative paths of the module code files, and the root path of the relative paths is defined according to the path of the bottom layer software engineering.

[0011] In addition, the compiling of the module code files in each module to generate module HEX files, and the excluding of the module code files not participating in the compilation according to the user interface file, and the compiling of the module code files participating in the compilation in each module to generate module LIB files comprise:

[0012] The HEX_GPJ engineering and the LIB_GPJ engineering are created, the module code files are added to the HEX_GPJ engineering to compile to generate module HEX files, the module code files not participating in the compilation are excluded according to the user interface file, and the module code files participating in the compilation are added to the LIB_GPJ engineering to compile to generate the module LIB files.

[0013] In addition, the compiling of the module code files in each module to generate module HEX files, and the excluding of the module code files not participating in the compilation according to the user interface file, and the compiling of the module code files participating in the compilation in each module to generate module LIB files further comprise:

[0014] The folder information corresponding to each module is collected as a folder tree, and the module HEX files and the module LIB files corresponding to each module are found through the path information provided by the folder tree.

[0015] In addition, the compiling of the module code files recorded in the user interface file to generate bottom layer interface HEX files comprises: acquiring the module code files not participating in the compilation in each module from the bottom layer software engineering and copying them into a bottom layer interface folder of the integrated software engineering, and acquiring the module code files not participating in the compilation in each module from the bottom layer interface folder to compile to generate bottom layer interface HEX files.

[0016] In addition, it further comprises sequentially executing the instructions corresponding to the first option and the second option in response to a third option inputted externally.

[0017] The present application also provides a software integration tool, which adopts the software integration method as claimed in any one of the preceding claims, comprising:

[0018] An operation interface is provided, which provides multiple compiling options.

[0019] The present application also provides an electronic device, which comprises:

[0020] at least one processor; and,

[0021] a memory in communication connection with the at least one processor; wherein,

[0022] the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the software integration method as claimed in any one of the preceding claims.

[0023] The present application also provides a storage medium, which stores computer instructions for performing all steps of the software integration method as claimed in any one of the preceding claims when the computer executes the computer instructions.

[0024] The present application also provides a computer program product, which comprises computer program / instructions, and is characterized by that the computer program / instructions are executed by a processor to implement the software integration method as claimed in any one of the preceding claims.

[0025] The present application solves the technical problem of low efficiency and inability to avoid mistakes in the prior art, in which an editing tool used in a development project configures a single code file, manually establishes a GPJ engineering link code file, compiles software and generates a library file, and finally generates an integrated engineering in a manual manner. BRIEF DESCRIPTION OF DRAWINGS

[0026] Figure 1 A flowchart of the software integration method provided by an embodiment of the present application is shown in the figure;

[0027] Figure 2 A software engineering schematic diagram of the software integration method provided by an embodiment of the present application is shown in the figure;

[0028] Figure 3 A hardware structure schematic diagram of the electronic device provided by an embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0029] The application will be described in further detail below with reference to the embodiments and drawings. The embodiments are only intended to illustrate the application in detail and do not impose any limitation on the application, and the protection scope of the application is defined by the claims.

[0030] The application will be described in further detail below with reference to the embodiments and drawings. The embodiments are only intended to illustrate the application in detail and do not impose any limitation on the application, and the protection scope of the application is defined by the claims.

[0031] With reference to Figure 1 , the application provides a software integration method, comprising:

[0032] In step S101, in response to an external input, if a first option of the external input is selected, sequentially execute steps S102 to S103, acquire module code files corresponding to a plurality of different modules in a bottom-layer software engineering, acquire a user interface file, the user interface file records module code files not participating in compilation in each module, compile the module code files in each module to generate a module HEX file, exclude the module code files not participating in compilation according to the user interface file, compile the module code files participating in compilation in each module to generate a module LIB file, integrate the module HEX files of all modules into a bottom-layer HEX file, and integrate the module LIB files of all modules into a bottom-layer LIB file.

[0033] In step S102, if a second option of the external input is selected, sequentially execute steps S104 and S105, acquire an application-layer code file in an integrated software engineering and compile to generate an application-layer HEX file, compile the module code files recorded in the user interface file to generate a bottom-layer interface HEX file, generate an integrated HEX file from the application-layer HEX file, the bottom-layer interface HEX file and the bottom-layer LIB file, and the bottom-layer HEX file and the integrated HEX file are used for burning into a chip.

[0034] In the prior art, the electric drive controller software mainly takes a micro controller unit (MCU) as a carrier, and uses C language to develop various logical functions. To convert the C language logic into an executable file (HEX file) that can be run by the controller, the following steps are needed: 1. Compiling code: compiling C files to generate one or more intermediate files. 2. Linking: merging the generated intermediate files with necessary library files to generate an executable file. In order to improve the development efficiency of the controller software and the software reusability, the code is divided into application layer code and bottom layer software code. The application layer code is used to implement logical calculation functions, and the bottom layer software code is used to implement hardware control and signal interaction functions. When the controller hardware does not change, only the application layer code needs to be modified to achieve different functions, that is, the bottom layer software is used as a base platform to develop various controllers. The bottom layer software code includes communication, diagnosis, complex drive and other modules, which are usually developed by multiple engineers and integrated into a bottom layer software project by an integration engineer to develop link relationships, so that the bottom layer HEX file can be compiled. After the bottom layer HEX file is debugged and verified, the application layer code needs to be integrated. The bottom layer software project needs to reserve a part of the bottom layer interface source code that needs to be called by the application layer, and pack the code that does not need to be called by the application layer into a library file to prevent tampering. The interface source code in the bottom layer software project, the library file and the application layer code are integrated into an integrated software project, and the link relationships are developed to successfully generate the final HEX file. The HEX file is used to burn into a chip.

[0035] In order to make the compilation work of the bottom layer code project and the integrated code project one-key, a software integration method is provided in the present application. The module code file recorded in the user interface file provides options for the compiler. In addition to the first option and the second option, the options can also include a variety of other options, such as a third option that combines the functions corresponding to the first option and the second option. The user interface file can also provide an option for compiling only the module code file recorded in the user interface file to generate a bottom layer interface HEX file. The application layer code file can also provide an option for compiling only the application layer code to generate an application layer HEX file. The bottom layer LIB file can also provide an option for compiling only the bottom layer LIB file, which is used to compile the module code file participating in the compilation in each module to generate a module LIB file, and then integrate the module LIB files of all modules into a bottom layer LIB file.

[0036] If only the underlying code needs to be compiled, the first option is selected. When the software integration method detects that the external input is the first option, the module code files corresponding to the plurality of different modules in the underlying software engineering are obtained, the module code files in each module are compiled to generate module HEX files, the module code files participating in the compilation in each module are compiled to generate module LIB files, the module HEX files of all modules are integrated into an underlying HEX file, the module LIB files of all modules are integrated into an underlying LIB file, the module code files not participating in the compilation in each module are pre-written in a user interface file, and the module code files not participating in the compilation are excluded according to the user interface file. The first option corresponds to compiling the code files in the underlying software engineering. When the module code files in the underlying software engineering change, increase or decrease, the compiler can one-key recompile the underlying software engineering, and prepare for the integration of the application layer.

[0037] If the external input is the second option, the application layer code files in the integrated software engineering are obtained and compiled to generate an application layer HEX file, and the module code files recorded in the user interface file are 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 for burning into a chip. The second option corresponds to compiling the code in the integrated software engineering, that is, mainly processing the code of the application layer. When the application layer code files change, increase or decrease, the compiler can one-key recompile the integrated software engineering to obtain a new burning file.

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

[0039] Here, the number of modules in the underlying software engineering is not limited and can be continuously increased.

[0040] Referring to Figure 2 , an example is given to illustrate the direct engineering diagram of the underlying software engineering and the integrated software engineering.

[0041] At S1, the main GPJ project is automatically generated according to the module code folder.

[0042] At S2, the module code files not participating in the compilation are reserved according to the configuration and copied to the integrated software engineering, and exist in the form of source files. The source files and the underlying LIB file are provided for the integrated software engineering.

[0043] At S3, the underlying LIB file is generated and copied to the integrated software engineering.

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

[0045] The present application solves the technical problem of low efficiency and inability to avoid errors in the prior art caused by the configuration of the editing tool used in the development project, the manual establishment of GPJ engineering link code files, the compilation of software and the generation of library files, and finally the manual comparison to generate integrated engineering. The software integration method provided by the present application can quickly compile with one key, without the need for manual operation, improving efficiency while avoiding errors caused by manual operation.

[0046] In one embodiment, obtaining the module code files corresponding to the plurality of different modules in the underlying software engineering includes:

[0047] According to the pre-defined relative path of the module code file, the module code files corresponding to the plurality of different modules in the underlying software engineering are obtained, and the root path of the relative path is defined according to the path of the underlying software engineering.

[0048] The module code files corresponding to different modules are processed to generate a relative path based on the underlying software engineering, so that in the case of distributed software development, the underlying software engineering on different computers can link to the corresponding module code files according to the relative path.

[0049] Optionally, according to the suffix of the module code file, the names and directories of all module code files participating in the compilation are recorded, collected as doc_list, and the absolute paths of all module code files in doc_list are replaced with relative paths, so that in the case of distributed software development, the corresponding module code files can be linked according to the relative path on different computers.

[0050] In one embodiment, the module code files in each module are compiled to generate module HEX files, and the module code files participating in the compilation in each module are compiled to generate module LIB files, including:

[0051] The HEX_GPJ project and the LIB_GPJ project are created, the module code files are added to the HEX_GPJ project for compilation to generate module HEX files, and the module code files participating in the compilation are added to the LIB_GPJ project for compilation to generate module LIB files.

[0052] In order to meet the requirement of distributed development, the module code files in each module are compiled to generate module HEX files, the module code files participating in the compilation in each module are compiled to generate module LIB files, then all the module HEX files are linked to generate a bottom-layer HEX file, and all the module LIB files are linked to generate a bottom-layer LIB file. The module HEX file and the module LIB file are generated separately for each module, so that when one of the modules is changed, increased or decreased, only the module HEX file and the module LIB file of the module need to be regenerated, and the bottom-layer software engineering can sequentially link the module HEX files and the module LIB files when generating the bottom-layer HEX file and the bottom-layer LIB file.

[0053] Optionally, the folder information corresponding to each module is collected as dir_list, and the path information provided by the dir_list is used to find the module HEX file and the module LIB file of each module.

[0054] Optionally, in the foregoing work, the preparation work is done first, the names and the directories of all the module code files participating in the compilation are recorded according to the suffixes of the module code files, collected as doc_list, and the absolute paths of all the module code files in the doc_list are replaced with relative paths. The specific steps of creating a GPJ master project, linking all the module HEX files to generate a bottom-layer HEX file, and linking all the module LIB files to generate a bottom-layer LIB file through the GPJ master project are as follows: the module code files in the doc_list are added to the corresponding sub-GPJ project of the module to participate in the compilation and linking, the HEX sub-GPJ project adds all the files, and the LIB sub-GPJ project excludes the module code files listed in the user interface file User.txt (also referred to as USER.TXT), so as to ensure that the module code files that need to be modified in the application layer do not participate in the generation of the library file. The header file directory in the module code file is added to the GPJ master project, and after the GPJ master project is configured, the bottom-layer HEX file and the bottom-layer LIB file can be compiled and generated.

[0055] In one of the embodiments, the module code files in each module are compiled to generate module HEX files, the module code files not participating in the compilation are excluded according to a user interface file, and the module code files participating in the compilation in each module are compiled to generate module LIB files, and the method further includes:

[0056] The folder information corresponding to each module is collected as a folder tree, and the path information provided by the folder tree is used to find the module HEX file and the module LIB file corresponding to each module.

[0057] The folder information corresponding to each module is collected as a folder tree, and the module HEX file and the module LIB file corresponding to each module are found through the path information provided by the folder tree, thereby improving the searching efficiency and providing a basis for one-key searching.

[0058] In one embodiment, the folder information corresponding to each module is collected as a folder tree, and the module HEX file and the 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 the module HEX file and the module LIB file are found through the path information provided by the dir_list.

[0059] In one embodiment, compiling the module code file recorded in the user interface file to generate the underlying interface HEX file includes: obtaining the module code file not participating in the compilation in each module from the underlying software project and copying it to the underlying interface folder of the integrated software project, and obtaining the module code file not participating in the compilation in each module from the underlying interface folder to compile and generate the underlying interface HEX file.

[0060] In the created integrated software project, the underlying interface folder is found, if not found, the underlying interface folder is created, the module code file not participating in the compilation in each module is obtained from the underlying software project and copied to the underlying interface folder of the integrated software project, and the module code file in the underlying interface folder is provided for the application layer, which can modify and operate it according to its own needs. By providing the module code file that can be modified by the application layer, the application layer can only modify the relevant code file, and cannot modify and misoperate other underlying files.

[0061] In one embodiment, it further includes a third option in response to an external input, and the third option includes instructions of the first option and the second option.

[0062] The process involves: acquiring module code files corresponding to multiple different modules in the underlying software engineering; compiling the module code files in each module to generate module HEX files; compiling the module code files that participate in the compilation of each module to generate module LIB files; integrating the module HEX files of all modules into a bottom-level HEX file; integrating the module LIB files of all modules into a bottom-level LIB file; pre-writing the module code files that do not participate in the compilation of each module into the user interface file; excluding the module code files that do not participate in the compilation based on the user interface file; acquiring application layer code files in the integration software engineering and compiling them to generate application layer HEX files; compiling the module code files recorded in the user interface file to generate bottom-level interface HEX files; and generating an integrated HEX file from the application layer HEX file, bottom-level interface HEX file, and bottom-level LIB file. The bottom-level HEX file and the integrated HEX file are then used to burn into the chip.

[0063] With a single click, the underlying software engineering and integrated software engineering can be compiled and linked, directly generating underlying HEX files and integrated HEX files.

[0064] In one embodiment, a software integration method is also proposed, comprising:

[0065] Obtain the 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 that participate in the compilation in each module to generate module LIB files, integrate the module HEX files of all modules into an underlying HEX file, integrate the module LIB files of all modules into an underlying LIB file, 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 based on the user interface file;

[0066] The underlying HEX file is used to burn into the chip, while the underlying LIB file, user interface file, and module code files recorded in the user interface file are provided for use by the integration software engineering. The software integration method provided by this invention enables one-click and rapid compilation.

[0067] In one embodiment, an application-layer software integration method is also proposed, comprising:

[0068] In integrated software engineering, the application layer code file is obtained and compiled to generate the application layer HEX file. 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 combined to generate the integrated HEX file, which is used to burn into the chip.

[0069] The underlying LIB file, user interface file, and module code files recorded in the user interface file are obtained from the underlying software engineering.

[0070] The software integration method provided by this invention enables compilation to be completed quickly with a single click.

[0071] The present invention also proposes a software integration tool, employing any of the software integration methods described above, comprising:

[0072] It provides a user interface with various compilation options.

[0073] This invention solves the technical problems of inefficiency and unavoidable errors inherent in the existing technology that uses editing tools to configure individual code files, manually create GPJ project linking files, compile software and generate library files, and finally manually compare and generate an integrated project. The software integration method provided by this invention enables one-click and rapid compilation, eliminating the need for manual operation, thus improving efficiency and avoiding errors caused by manual operation.

[0074] Reference Figure 3 The present invention also proposes a hardware structure diagram of an electronic device, comprising:

[0075] At least one processor 301; and,

[0076] A memory 302 communicatively connected to at least one of the processors 301; wherein,

[0077] The memory 302 stores instructions that can be executed by at least one processor, which enables the at least one processor to perform the aforementioned software integration method.

[0078] Figure 3 Take processor 301 as an example.

[0079] The electronic device is preferably a vehicle controller. The electronic device may also include an input device 303 and a display device 304.

[0080] The processor 301, memory 302, input device 303 and display device 304 can be connected by a bus or other means. The figure shows an example of connection by bus.

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

[0082] Memory 302 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and applications required for at least one function; the data storage area may store data created according to the use of the software integration method, etc. Furthermore, memory 302 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 302 may optionally include memory remotely located relative to processor 301, and these remote memories may be connected via a network to the apparatus performing the software integration method. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0083] Input device 303 can receive user clicks and generate signal inputs related to user settings and function control in the software integration method. Display device 304 may include display devices such as a display screen.

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

[0085] This invention solves the technical problems of inefficiency and unavoidable errors inherent in the existing technology that uses editing tools to configure individual code files, manually create GPJ project linking files, compile software and generate library files, and finally manually compare and generate an integrated project. The software integration method provided by this invention enables one-click and rapid compilation, eliminating the need for manual operation, thus improving efficiency and avoiding errors caused by manual operation.

[0086] One embodiment of the present invention provides a storage medium that stores computer instructions, which, when executed by a computer, are used to perform all the steps of the software integration method described above.

[0087] In the context of this disclosure, a storage medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. The storage medium can be a machine-readable signal medium or a machine-readable storage medium. Optionally, the storage medium can be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), compact disc ROM (CD-ROM), magnetic tape, floppy disk, and optical data storage device.

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

[0089] The above description is merely the principle and preferred embodiment of the present invention. It should be noted that, for those skilled in the art, several other modifications can be made based on the principle of the present invention, and these modifications should also be considered within the scope of protection of the present invention.

[0090] The above description is merely the principle and preferred embodiment of the present invention. It should be noted that, for those skilled in the art, several other modifications can be made based on the principle of the present invention, and these modifications should also be considered within the scope of protection 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, the module code files corresponding to multiple different modules in the underlying software engineering are obtained, and the user interface file is obtained. The user interface file records the module code files in each module that are not included in the compilation. The module code files in each module are compiled to generate module HEX files. The module code files that are not included in the compilation are excluded according to the user interface file. The module code files in each module that are included in the compilation are compiled to generate module LIB files. 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 engineering and compiled to generate the application layer HEX file. 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 the integrated HEX file. The underlying HEX file and the integrated HEX file are used to burn into the chip. The process of compiling the module code files in each module to generate a module HEX file, excluding module code files that are not included in the compilation based on the user interface file, and compiling the module code files that are included in the compilation in each module to generate a module LIB file, further includes: Collect the folder information corresponding to each module into a folder tree, and find the module HEX file and module LIB file corresponding to each module through the path information provided by the folder tree; The step of 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 are not included in the compilation of each module from the underlying software project and copying them to the underlying interface folder of the integrated software project; obtaining the module code files that are not included in the compilation of each module from the underlying interface folder and compiling them to generate the underlying interface HEX file.

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

3. The software integration method according to claim 1, characterized in that, The process of compiling the module code files in each module to generate a module HEX file, excluding module code files that are not included in the compilation based on the user interface file, and compiling the module code files that are included in the compilation to generate a module LIB file includes: Create a HEX_GPJ project and a LIB_GPJ project. Add the module code files to the HEX_GPJ project and compile them to generate the module HEX file. Exclude the module code files that are not included in the compilation based on the user interface file. Add the module code files that are included in the compilation to the LIB_GPJ project and compile them to generate the module LIB file.

4. The software integration method according to any one of claims 1-3, characterized in that, It also includes a third option in response to external input, which sequentially executes the instructions corresponding to the first option and the second option.

5. A software integration tool, characterized in that, The software integration method described in any one of claims 1-4 includes: A user interface is provided, which offers a variety of compilation options.

6. 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 executable by at least one of the processors, which enable the at least one processor to perform the software integration method as described in any one of claims 1-4.

7. A storage medium, characterized in that, The storage medium stores computer instructions, which, when executed by a computer, are used to perform all the steps of the software integration method as described in any one of claims 1-4.

8. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the software integration method as described in any one of claims 1-4.

Images