Software platform using third party library function intermodulation method and intermodulation system

Abstract

The present invention provides a third-party program library function intermodulation method and an intermodulation system for a software platform, wherein the third-party program library function intermodulation method for a software platform comprises: constructing multiple third-party program libraries; checking the legality of the third-party program libraries; and multiple third-party program libraries calling each other, realizing a universal calling framework through a software platform, so that functions registered by the third-party program library in the software platform can be shared among all loaded third-party program libraries, and when the current third-party program library needs to call other third-party program libraries, it is not necessary to load other third-party program libraries, and access to other third-party program libraries can be realized by using a function table containing other third-party program libraries shared to the current third-party program library by the software platform, and when other third-party program libraries are not loaded, the software platform and the current third-party program library can both be informed of this situation, so that the current third-party program library can be smoothly loaded and provide part of the functions.

Description

Technical Field

[0001] The invention belongs to the field of computer technology, and in particular relates to a third-party program library function intermodulation method and an intermodulation system for a software platform. Background Art

[0002] The Windows-based software platform expands its functions by importing third-party libraries. Among the third-party libraries imported by the software platform, there is a situation where a third-party library calls other third-party libraries. The traditional approach is to modify the current third-party library and implement the call to other third-party libraries by implicitly or explicitly adding other third-party libraries.

[0003] The problem brought by the existing technical solution is that the method of modifying the current third-party program library to support the call of other third-party program libraries requires additional workload of the current third-party program library. As other third-party program libraries are changed, the current third-party program library must also be changed synchronously; at the same time, if the current third-party program library calls other third-party program libraries by explicitly loading other third-party program libraries, if the other third-party program libraries do not exist, the current third-party program library cannot be loaded either.

[0004] Therefore, based on the above technical problems, it is necessary to design a new software platform to use a third-party program library function intermodulation method and an intermodulation system. Summary of the invention

[0005] The purpose of the present invention is to provide a third-party program library function intermodulation method and intermodulation system for a software platform.

[0006] In order to solve the above technical problems, the present invention provides a method for intermodulating a software platform with a third-party program library function, comprising:

[0007] Build multiple third-party libraries;

[0008] Verify the legitimacy of third-party libraries; and

[0009] Multiple third-party libraries call each other.

[0010] Further, the method for constructing multiple third-party program libraries includes:

[0011] Building each third-party program library through the software platform, that is, building an initialization submodule, a capability acquisition submodule and an internal submodule in each third-party program library through the software platform, and building a release submodule in the third-party program library;

[0012] The release submodule is adapted to automatically release the resources applied for by the third-party program library when the third-party program library is uninstalled.

[0013] Further, the method of constructing the initialization submodule through the software platform includes:

[0014] An initialization submodule is generated through the software platform header file and the software platform API list in the software platform, so that after the initialization submodule is called, the third-party program library obtains the address information of each API in the API list provided by the software platform.

[0015] Further, the method of constructing the capability acquisition submodule through the software platform includes:

[0016] The software platform loads the software platform version number, the corresponding list of user logic callback sub-modules and the corresponding third-party program library dependent external sub-module list to generate a capability acquisition sub-module. When the external program calls the capability acquisition sub-module, it obtains the version information of the software platform corresponding to the third-party program library, the list information of user logic callback sub-modules, the external sub-module information that this third-party program library depends on and all internal sub-module information of this third-party program library.

[0017] Further, the method of constructing the internal submodule through the software platform includes:

[0018] Generate internal sub-modules based on the user function logic sub-modules of the software platform.

[0019] Further, the method for verifying the legitimacy of the third-party library includes:

[0020] The third-party program library is loaded into the software platform, and the software platform calls the initialization submodule of the third-party program library, and the software platform calls the capability acquisition submodule of the third-party program library, and obtains the version number of the software platform corresponding to the third-party program library, the list of user callback submodules, the address information and function parameter information of all internal submodules of the third-party program library, and the external submodule information on which the third-party program library depends;

[0021] The software platform provides the third-party library with the submodule pointers it depends on;

[0022] If the external submodule that the third-party library depends on does not exist, the software platform provides a null pointer to the third-party library;

[0023] During the calling process of the third-party program library, judging whether there are other third-party program libraries that the third-party program library depends on according to whether the pointer is null;

[0024] If it is a null pointer, the internal submodules of other third-party libraries that the third-party library depends on will not take effect, but the functions of other internal submodules in the third-party library will still take effect;

[0025] The software platform compares the version number of the software platform corresponding to the obtained third-party library with its own version number. If the version number of the third-party library is greater than its own version number, the software platform stops calling the third-party library, otherwise it continues to call the third-party library.

[0026] Further, the method for the plurality of third-party program libraries to call each other includes:

[0027] After the software platform continues to call the third-party program library, the software platform is adapted to call the third-party program library according to the list of user callback submodules and the list of internal submodules obtained in the third-party program library;

[0028] If the current third-party library needs to call the internal submodule of other third-party libraries during operation, the software platform passes the submodule pointer that the current third-party library depends on in the capability acquisition submodule, so that the current third-party library calls the internal submodule in other third-party libraries;

[0029] After the call is completed, the software platform releases the requested resources by calling the release submodule in the third-party program library.

[0030] In a second aspect, the present invention further provides a software platform for the above-mentioned software platform using a third-party program library function intermodulation method, comprising:

[0031] Software platform header files, software platform API list, software platform version number, list of user logic callback sub-modules, list of external sub-modules that third-party program libraries depend on, user function logic sub-modules, and C++ compiler.

[0032] In a third aspect, the present invention further provides a third-party library for the software platform using a third-party library function intermodulation method, comprising:

[0033] Initialization submodule, capability acquisition submodule, internal submodule and release submodule.

[0034] In a fourth aspect, the present invention further provides an intermodulation system using the above-mentioned software platform and the third-party program library function intermodulation method, comprising:

[0035] Build modules and multiple third-party libraries;

[0036] Verification module to verify the legitimacy of third-party libraries; and

[0037] Calling module, multiple third-party program libraries call each other.

[0038] The beneficial effect of the present invention is that the present invention realizes a general calling framework through a software platform by constructing multiple third-party program libraries; verifying the legality of the third-party program libraries; and multiple third-party program libraries calling each other, so that the functions registered by the third-party program libraries in the software platform can be shared among all loaded third-party program libraries, so that when the current third-party program library needs to call other third-party program libraries, there is no need to load other third-party program libraries. Only by using the function table containing other third-party program libraries shared by the software platform to the current third-party program library, access to other third-party program libraries can be achieved. When other third-party program libraries are not loaded, the software platform and the current third-party program library can both be aware of this situation, which enables the current third-party program library to be successfully loaded and provide some functions.

[0039] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description and the drawings.

[0040] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0042] Figure 1 It is a flow chart of a method for intermodulating functions of a third-party program library with a software platform involved in the present invention;

[0043] Figure 2 is a flow chart of building multiple third-party program libraries involved in the present invention;

[0044] Figure 3 It is a flow chart of multiple third-party program libraries involved in the present invention calling each other;

[0045] Figure 4 It is a principle block diagram of the intermodulation system designed by the present invention. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0047] Example 1

[0048] Figure 1 The present invention is a flowchart of a method for intermodulating functions of a software platform with a third-party program library.

[0049] like Figure 1 As shown, this embodiment 1 provides a method for inter-deploying functions of a software platform with a third-party library, including: building multiple third-party libraries; verifying the legitimacy of the third-party libraries; and calling each other by multiple third-party libraries, so that a common calling framework is implemented through the software platform, so that the functions registered by the third-party library in the software platform can be shared among all loaded third-party libraries, so that when the current third-party library needs to call other third-party libraries, there is no need to load other third-party libraries. Only the function table containing other third-party libraries shared by the software platform to the current third-party library can be used to access other third-party libraries. When other third-party libraries are not loaded, the software platform and the current third-party library can both be aware of this situation, so that the current third-party library can be smoothly loaded and provide some functions.

[0050] Figure 2 It is a flowchart of building multiple third-party program libraries involved in the present invention.

[0051] like Figure 2 As shown, in this embodiment, the method for constructing multiple third-party program libraries includes: building a third-party program library by calling a C++ compiler through a software platform, building each third-party program library through the software platform, that is, building an initialization submodule (containing an initialization function and corresponding functions), a capability acquisition submodule (containing a capability acquisition function and corresponding functions) and an internal submodule (containing internal functions and corresponding functions) in each third-party program library through the software platform, and building a release submodule (containing a release function and corresponding functions) in the third-party program library; the release submodule is suitable for automatically releasing the resources applied for by the third-party program library when the third-party program library is uninstalled; the initialization submodule, the capability acquisition submodule and the release submodule are public submodules, and the functions in the submodules can be automatically loaded and called by an external program, and the functions in the internal submodules are not visible to the outside.

[0052] In this embodiment, the method of constructing an initialization sub-module through a software platform includes: generating an initialization sub-module through a software platform header file and a software platform API list in the software platform, so that after the initialization sub-module is called, the third-party program library obtains the address information of each API in the API list provided by the software platform, and can perform its normal function.

[0053] In this embodiment, the method of constructing a capability acquisition sub-module through a software platform includes: the software platform loads the software platform version number, the corresponding list of user logic callback sub-modules and the corresponding third-party program library dependency external sub-module list to automatically generate a capability acquisition sub-module, and when an external program calls the capability acquisition sub-module, obtains the version information of the software platform corresponding to the third-party program library, the list information of the user logic callback sub-module, the external sub-module information that this third-party program library depends on and all internal sub-module information of this third-party program library.

[0054] In this embodiment, the method of constructing internal sub-modules through a software platform includes: generating internal sub-modules according to user function logic sub-modules of the software platform, and the internal sub-modules do not open interfaces to the outside world and can only be obtained by external programs (third-party program libraries) by calling capability acquisition functions.

[0055] Figure 3 It is a flow chart of the mutual calling of multiple third-party program libraries involved in the present invention.

[0056] like Figure 3As shown, in this embodiment, the method for verifying the legitimacy of the third-party program library includes: the third-party program library calling process is completed by the software platform and the third-party program library in cooperation; the third-party program library is loaded into its own software platform by loading the dynamic link library software platform, the software platform calls the initialization submodule of the third-party program library, and the software platform calls the capability acquisition submodule of the third-party program library to obtain the version number of the software platform corresponding to the third-party program library, the list of user callback submodules, the address information and function parameter information of all internal submodules of the third-party program library, and the external submodule information on which the third-party program library depends; in the capability acquisition function calling process, the software platform simultaneously provides the third-party program library with the submodule pointer on which it depends (provides other submodules on which the third-party program library depends) function pointer of internal function in third-party library); if the external sub-module that the third-party library depends on does not exist, the software platform provides a null pointer to the third-party library; during the calling process of the third-party library, it is determined whether there are other third-party libraries that the third-party library depends on based on whether it is a null pointer; if it is a null pointer, the internal sub-modules of other third-party libraries that the third-party library depends on are not effective, but the functions of other internal sub-modules in the third-party library are still effective; the software platform compares the version number of the software platform corresponding to the obtained third-party library with its own version number. If the version number of the third-party library is greater than its own version number, the software platform stops calling the third-party library; otherwise, it determines that the third-party library is legal (meets the requirements) and continues to call the third-party library.

[0057] In this embodiment, the method for the plurality of third-party libraries to call each other includes: after the software platform continues to call the third-party library, the software platform is adapted to call the third-party library according to the list of user callback submodules and the list of internal submodules obtained in the third-party library; if the current third-party library needs to call the internal submodule of other third-party libraries during operation, the current third-party library calls the internal submodule of other third-party libraries through the submodule pointer on which the software platform depends in the capability acquisition submodule; after the call is completed, the software platform releases the requested resources by calling the release submodule in the third-party library; when the software platform calls the third-party library, not only can the internal functions of other third-party libraries on which the third-party library depends be known, but also the function pointers on which they depend can be provided to the third-party library through the software platform itself, so that when there is mutual dependence between the third-party libraries, the dependence can be provided through the software platform without manually modifying the third-party library; and various function dependencies are provided to the third-party program through the software platform, so that the method can avoid frequent modification of the third-party library to realize the dependence on other third-party libraries, improve the development efficiency of the third-party function library, and reduce the possibility of errors.

[0058] In this embodiment, third-party library A and third-party library B are constructed through the software platform. When the software platform calls third-party library A, third-party library A needs to rely on some internal functions of third-party library B. Then the software platform sends the function pointer of the internal function that it relies on to third-party library A, so as to call the corresponding internal function from third-party library B.

[0059] In this embodiment, the software platform includes: a software platform header file, a software platform API list containing API symbol information, a software platform version number, user logic generated by the user through the software platform (embodied in the form of callback functions), the user's own logic designed by the software platform (embodied in ordinary functions), and a list of other third-party library functions that the user logic depends on (embodied in function-related symbol information); in the process of the software platform building an interoperable third-party library, it is first necessary to generate an initialization function of the third-party library, the source code of which is generated based on the software platform header file and the software platform API list containing API symbol information; secondly, it is necessary to generate a capability acquisition function, the source code of which is composed of the software platform's own version number, the symbol information of the user logic callback function, and the symbol information of the third-party library function that the user logic depends on; thirdly, it is also necessary to generate a release function, which is responsible for releasing the applied resources before the third-party library is uninstalled; finally, it is necessary to generate a series of internal functions, which are free logic designed by the user through the software platform; when all the required functions are generated, the software platform calls the C / C++ compiler to compile the generated functions into a third-party library executable file.

[0060] In this embodiment, the software platform also includes: a dynamic link library loading function, a function calling function, a dependent function management function, a version number comparison function, a running function and a stopping function;

[0061] In the process of the software platform calling an interoperable third-party library, it is first necessary to load the third-party library through the dynamic link library loading function. After successful loading, the initialization function of the third-party library is called through the function call function, and then the capability acquisition function of the third-party library is called through the function call function. The software platform version number, user logic callback function and third-party function symbol information on which the user logic depends compiled into the capability acquisition function are read out and input into the software platform. The software platform will know the relationship between the build version number of the third-party library and the version number of the software platform. Only when the version numbers are the same, or the version number of the software platform is greater than the build version number of the third-party library, can the software platform continue to call the third-party library, otherwise the calling process is terminated; at the same time, the dependent function management function of the software platform also needs to detect the dependent function of the third-party library. Whether it exists in the software platform, if it does, the first address of the dependent function needs to be given to the third-party program library, if it does not exist, a null pointer needs to be given to the third-party program library; after the version number comparison function and the dependent function management function are executed and the flag that can continue to be called is returned, the software platform executes the run program function. During the running process, the internal functions of the third-party program library will be freely called by the software platform to provide various functions to the software platform; when the third-party program library needs to call the function it depends on, first determine whether the dependent function is a null pointer. If it is not a null pointer, continue to call, otherwise it is considered that the library it depends on does not exist, the relevant function is invalid, and the current calling process returns failure; when the third-party program library is not needed, the software platform executes the stop program function, which calls the release function of the third-party program library. After releasing the resources applied for by the third-party program library, the calling process ends.

[0062] Specifically, in this embodiment, the following two third-party program libraries are used as examples to illustrate the intermodulation method: a third-party program library of a general CRC16 algorithm; a third-party program library used for a calibration system, which relies on a general CRC16 algorithm to unlock the target controller; these two third-party program libraries are loaded successively by the software platform, and the software platform uniformly provides the user with a verification function of the CRC16 algorithm and a calibration function of the calibration system. The traditional third-party program library of a general CRC16 algorithm needs to export the API functions that the external program depends on during compilation; the third-party program library used in the traditional calibration system needs to import the dependent functions in the third-party program library of the general CRC16 algorithm because it relies on the third-party program library of the general CRC16 algorithm, and first loads the third-party program library of the general CRC16 algorithm during the loading process. If the third-party library of the universal CRC16 algorithm does not exist, the third-party library used by the calibration system will fail to load and cannot provide any functions to the software platform users; if the function in the third-party library of the universal CRC16 algorithm changes, for example, the parameters of the CRC16 algorithm function increase from three to four, and the third-party function library used by the calibration system is not updated synchronously for some reason, in this case, both third-party libraries can be loaded normally, but the third-party library used by the calibration system will crash when calling the CRC16 library. Therefore, the traditional method of the software platform library to reference another library through static linking, coupled with the defect of lacking interface definition checking during operation, will lead to a decrease in the availability of the software platform, and problems will not be easy to troubleshoot. The software platform provided in this embodiment adopts a different method, and its working process is as follows: the CRC16 third-party library and the third-party library used for the calibration system use the APIs that the external program depends on as internal functions, and do not export any API functions; the software platform loads the CRC16 third-party library and the third-party library used for the calibration system in sequence; the software platform calls the capability acquisition functions of the two third-party libraries to obtain the internal function list of each library and the definition information of each function, including function address information, parameter information, etc.; the software platform calls the capability acquisition functions of the two third-party libraries to obtain the function list of each library that depends on other libraries and the definition information of each function, including function address information, parameter information, etc.; the software platform analyzes the dependent functions of each third-party library, detects that the third-party library used for the calibration system depends on the CRC16 third-party library, and then assigns the dependent function address information in the third-party library used for the calibration system to the corresponding function address information of the CRC16 third-party library.The software platform analyzes the function definition information of each third-party library's dependent functions, including parameter information, etc. If it finds that the internal API function definition of the CRC16 third-party library is different from the corresponding dependent function definition of the third-party library used in the calibration system, a warning will be issued to the user, and the operation of the third-party library used in the calibration system will be prohibited. After the dependency relationship of the third-party library is verified, the software platform can call these two third-party libraries normally to provide services to users.

[0063] Example 2

[0064] Based on Example 1, this Example 2 also provides a software platform for the method of intercommunication between the software platform and the third-party program library function in Example 1, including: a software platform header file, a software platform API list, a software platform version number, a list of user logic callback sub-modules, a list of external sub-modules that the third-party program library depends on, a user function logic sub-module and a C++ compiler.

[0065] In this embodiment, the sub-modules and functions included in the software platform have been described in detail in Embodiment 1 and will not be repeated in this embodiment.

[0066] Example 3

[0067] Based on Example 1, this Example 3 also provides a third-party library for the software platform in Example 1 to use a third-party library function intercommunication method, including: an initialization submodule, a capability acquisition submodule, an internal submodule and a release submodule.

[0068] In this embodiment, the sub-modules and functions included in the third-party program library have been described in detail in Embodiment 1 and will not be repeated in this embodiment.

[0069] Example 4

[0070] Figure 4 It is a principle block diagram of the intermodulation system designed by the present invention.

[0071] On the basis of Example 1, this Example 4 also provides an intermodulation system that adopts the software platform in Example 1 to use the third-party program library function intermodulation method, including: a construction module to build multiple third-party program libraries; a verification module to verify the legitimacy of the third-party program libraries; and a calling module, multiple third-party program libraries call each other.

[0072] In this embodiment, the specific functions of each module have been described in detail in Embodiment 1 and will not be repeated in this embodiment.

[0073] Example 5

[0074] Based on the above embodiments, this embodiment 5 also provides a calling device, including: a software platform and several third-party program libraries; the software platform is suitable for building third-party program libraries and calling third-party program libraries; and the third-party program libraries can call each other through the software platform.

[0075] In this embodiment, the functions of the software platform and the third-party program library have been described in detail in the above embodiments and will not be repeated in this embodiment.

[0076] In summary, the present invention constructs multiple third-party program libraries; and multiple third-party program libraries call each other, thereby realizing a universal calling framework through a software platform, so that the functions registered by the third-party program libraries in the software platform can be shared among all loaded third-party program libraries, so that when the current third-party program library needs to call other third-party program libraries, there is no need to load other third-party program libraries. Only the function table containing other third-party program libraries shared to the current third-party program library by the software platform can be used to access other third-party program libraries. When other third-party program libraries are not loaded, the software platform and the current third-party program library can both be aware of this situation, which enables the current third-party program library to be successfully loaded and provide some functions.

[0077] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0078] In addition, the functional modules in the various embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0079] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0080] Based on the above ideal embodiments of the present invention, the relevant staff can make various changes and modifications without departing from the technical concept of the present invention through the above description. The technical scope of the present invention is not limited to the contents of the specification, and its technical scope must be determined according to the scope of the claims.

Claims

1. A method for intermodulating third-party library functions for a software platform, characterized in that: include: Build multiple third-party libraries; Verify the legitimacy of third-party libraries; as well as Multiple third-party libraries call each other; The method for building multiple third-party program libraries includes: Building each third-party program library through the software platform, that is, building an initialization submodule, a capability acquisition submodule and an internal submodule in each third-party program library through the software platform, and building a release submodule in the third-party program library; The release submodule is adapted to automatically release the resources applied for by the third-party library when the third-party library is uninstalled; Methods for constructing initialization submodules through software platforms include: Through the software platform header file and software platform API List generates initialization submodules so that after the initialization submodule is called, the third-party library obtains the software platform provided API Each in the list API address information; Methods for building capability acquisition submodules through software platforms include: The software platform loads the software platform version number, the corresponding user logic callback submodule list and the corresponding third-party program library dependent external submodule list to generate a capability acquisition submodule, and when the external program calls the capability acquisition submodule, obtains the software platform version information corresponding to the third-party program library, the user logic callback submodule list information, the third-party program library dependent external submodule information and all internal submodule information of the third-party program library; Methods for building internal submodules through software platforms include: Generate internal submodules according to the user function logic submodules of the software platform; Methods for verifying the legitimacy of third-party libraries include: The third-party program library is loaded into the software platform. The software platform calls the initialization submodule of the third-party program library, and the software platform calls the capability acquisition submodule of the third-party program library to obtain the version number of the software platform corresponding to the third-party program library, the list of user logic callback submodules, the address information and function parameter information of all internal submodules of the third-party program library, and the external submodule information on which the third-party program library depends; The software platform provides the third-party library with the submodule pointers it depends on; If the external submodule that the third-party library depends on does not exist, the software platform provides a null pointer to the third-party library; During the calling process of the third-party program library, judging whether there are other third-party program libraries that the third-party program library depends on according to whether the pointer is null; If it is a null pointer, the internal submodules of other third-party libraries that the third-party library depends on will not take effect, but the functions of other internal submodules in the third-party library will still take effect; The software platform compares the version number of the software platform corresponding to the obtained third-party program library with its own version number. If the version number of the third-party program library is greater than its own version number, the software platform stops calling the third-party program library. Otherwise, the software platform continues to call the third-party program library. The methods for multiple third-party libraries to call each other include: After the software platform continues to call the third-party program library, the software platform is adapted to call the third-party program library according to the list of user logic callback submodules and the list of internal submodules obtained in the third-party program library; If the current third-party library needs to call the internal submodule of other third-party libraries during operation, the software platform passes the submodule pointer that the current third-party library depends on in the capability acquisition submodule, so that the current third-party library calls the internal submodule in other third-party libraries; After the call is completed, the software platform releases the requested resources by calling the release submodule in the third-party program library.

2. A software platform for the third-party library function intermodulation method of the software platform as claimed in claim 1, characterized in that: include: Software platform header file, software platform API List, software platform version number, list of user logic callback sub-modules, list of external sub-modules that third-party program libraries depend on, and user function logic sub-modules.

3. A third-party library for a software platform function intermodulation method using a third-party library as claimed in claim 1, characterized in that: include: Initialization submodule, capability acquisition submodule, internal submodule and release submodule.

4. An intermodulation system using the software platform intermodulation method using a third-party library function as claimed in claim 1, characterized in that: include: Build modules and multiple third-party libraries; Verify the module to verify the legitimacy of third-party program libraries; As well as calling modules, multiple third-party program libraries call each other.

Images