A method, device, equipment and medium for generating a mobile application software application package

Abstract

The present application discloses a method, apparatus, device and medium for generating a mobile application software application package, which relates to the field of computer technology, including determining the types of local mobile application software plug-ins, adding mobile application development framework dependencies to the corresponding mobile application platform according to the types of mobile application software plug-ins; constructing various binary files, saving the various binary files and the corresponding mobile application development framework dependencies to various binary file storage repositories; performing a pruning operation on the platform side code to obtain various platform application packages, determining the dependency information corresponding to the platform application packages; and generating various target mobile application software application packages based on the platform application packages and the corresponding dependency information. The present application can increase the scope of application of mobile application software application package generation, improve the efficiency of mobile application software application package generation, reduce the size of mobile application software plug-in products on the server, and reduce developer download time and server resource usage.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and medium for generating a mobile application software application package. Background Art

[0002] In the prior art, for the Flutter (open source mobile application software development kit) packaging and building process, one mainly describes the building process of the Flutter App and focuses on the implementation of converting the Unity code into the corresponding platform language code of Android (Android operating system) or iOS (Apple operating system), which cannot reduce the compilation and building time. The six project types of Flutter include: Flutter Application (Flutter App application), Flutter Module (Flutter module), Flutter Plugin, Flutter Package (pure Dart / Flutter component package), Flutter Skeleton (Flutter App template application) and Flutter FFI Plugin (Flutter external function interface plug-in). The other is mainly aimed at hybrid application development. The corresponding Flutter project type is Flutter Module, which describes the generation of Flutter binary products, a binary product corresponding to the Flutter source code, which cannot reduce the package size and compilation time of the corresponding Flutter Plugin (mobile application software file), but can only improve the building efficiency for hybrid mobile application development, and cannot be used for any Flutter project type that uses Flutter Plugin (such as Flutter App\Flutter Module\Flutter Plugin\Flutter Package).

[0003] As can be seen from the above, how to increase the scope of application of mobile application software application package generation, improve the efficiency of mobile application software application package generation, reduce the product size of mobile application software plug-ins on the server, reduce developer download time, and reduce server resource usage are problems to be solved in this field. Summary of the Invention

[0004] In view of this, the present invention aims to provide a method, apparatus, device, and medium for generating a mobile application software package, which can expand the scope of application of mobile application software package generation, improve the efficiency of mobile application software package generation, reduce the size of mobile application software plug-in products on the server, reduce developer download time, and reduce server resource usage. The specific solution is as follows:

[0005] In a first aspect, the present application discloses a method for generating a mobile application software application package, comprising:

[0006] Determine the local mobile application software plug-in types, and add mobile application development framework dependencies to the corresponding mobile application platform according to the mobile application software plug-in types;

[0007] Constructing binary files according to the types of the mobile application software plug-ins and the corresponding mobile application development framework dependencies, and saving the binary files and the corresponding mobile application development framework dependencies to binary file storage repositories;

[0008] Performing a removal operation on the local platform-side code to obtain each platform application package, and determining dependency information corresponding to the platform application package from the binary file storage repository;

[0009] Generate target mobile application software application packages based on the platform application package and the corresponding dependency information.

[0010] Optionally, determining the types of local mobile application software plug-ins includes:

[0011] Determine the mobile application software environment based on current project information and business needs;

[0012] The types of mobile application software plug-ins are determined from the mobile application software environment.

[0013] Optionally, constructing each binary file according to each mobile application software plug-in type and the corresponding mobile application development framework dependency includes:

[0014] Determining language architecture information of the mobile application platform;

[0015] Binary files are constructed based on the language architecture information, the mobile application software plug-in type, and the corresponding mobile application development framework dependencies.

[0016] Optionally, the step of saving the binary files and the corresponding mobile application development framework dependencies to binary file storage repositories includes:

[0017] Determining each of the binary file storage repositories corresponding to each of the mobile application software plug-in types;

[0018] According to the type of each mobile application software plug-in, each binary file and the corresponding mobile application development framework dependency are saved to the corresponding binary file storage warehouse.

[0019] Optionally, the local platform-side code is removed to obtain the application packages for each platform, including:

[0020] Utilize local mobile application software building blocks to remove local platform-side codes to obtain application packages for each platform;

[0021] Upload each of the platform application packages to each of the binary file storage repositories in the form of a mobile application software plug-in.

[0022] Optionally, generating each target mobile application software application package based on the platform application package and the corresponding dependency information includes:

[0023] Determine a target application package generation method from preset application package generation methods;

[0024] The target application package generation method utilizes a local platform-side integration module and generates target mobile application software application packages based on the platform application package and the corresponding dependency information.

[0025] Optionally, the target application package generation method utilizes a local platform-side integration module and generates each target mobile application software application package based on the platform application package and the corresponding dependency information, including:

[0026] Utilizing a local platform-side integration module by hooking the compilation process, and generating each target mobile application software application package based on the platform application package and the corresponding dependency information;

[0027] Alternatively, the local platform-side integration module is utilized by modifying the bytecode, and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information.

[0028] In a second aspect, the present application discloses a mobile application software application package generation device, comprising:

[0029] A dependency adding module is used to determine the local mobile application software plug-in type and add the mobile application development framework dependency to the corresponding mobile application platform according to the mobile application software plug-in type;

[0030] A binary file construction module, configured to construct each binary file according to each mobile application software plug-in type and the corresponding mobile application development framework dependency, and save each binary file and the corresponding mobile application development framework dependency to each binary file storage repository;

[0031] A code removal module is used to remove the local platform-side code to obtain each platform application package, and determine the dependency information corresponding to the platform application package from the binary file storage repository;

[0032] The application package generation module is used to generate each target mobile application software application package based on the platform application package and the corresponding dependency information.

[0033] In a third aspect, the present application discloses an electronic device, comprising:

[0034] Memory, used to store computer programs;

[0035] The processor is used to execute the computer program to implement the aforementioned method for generating a mobile application software application package.

[0036] In a fourth aspect, the present application discloses a computer storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the aforementioned disclosed method for generating a mobile application software application package are implemented.

[0037] It can be seen that the present application provides a method for generating a mobile application software application package, including determining the local mobile application software plug-in types, and adding mobile application development framework dependencies to the corresponding mobile application platform according to the mobile application software plug-in types; constructing each binary file according to the mobile application software plug-in type and the corresponding mobile application development framework dependency, and saving each binary file and the corresponding mobile application development framework dependency to each binary file storage repository; performing a removal operation on the local platform-side code to obtain each platform application package, and determining the dependency information corresponding to the platform application package from the binary file storage repository; and generating each target mobile application software application package based on the platform application package and the corresponding dependency information. This application adopts the principle of divide and conquer, distributing events that previously required centralized processing into various stages. Packaging and integration are completely independent, effectively solving the problem of build time. In addition, this application can reduce the compilation and build time of Flutter App or Flutter Module in scenarios where it depends on a large number of Flutter Plugins, improve development efficiency, avoid compilation errors of the main project caused by source code modifications of sub-modules, effectively reduce the size of the Flutter Plugin product on the pub server, reduce developer download time, and also reduce the resource usage of the pub server. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0039] Figure 1 This is a flow chart of a method for generating a mobile application software application package disclosed in this application;

[0040] Figure 2 A specific flow chart of a method for generating a mobile application software application package disclosed in this application;

[0041] Figure 3 This is a flow chart of a method for generating a mobile application software application package disclosed in this application;

[0042] Figure 4 A flowchart specifically constructs a method for generating a mobile application software application package disclosed in this application;

[0043] Figure 5 This is a flowchart of a Flutter Plugin processing method disclosed in this application;

[0044] Figure 6 This is a structural diagram of a mobile application software application package generation device disclosed in this application;

[0045] Figure 7 This is a structural diagram of an electronic device provided in this application. DETAILED DESCRIPTION

[0046] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only 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 making creative efforts are within the scope of protection of the present invention.

[0047] In the prior art, for the Flutter (open source mobile application software development kit) packaging and building process, one mainly describes the building process of the Flutter App and focuses on the implementation of converting the Unity code into the corresponding platform language code of Android (Android operating system) or iOS (Apple operating system), which cannot reduce the compilation and building time. The six project types of Flutter include: Flutter Application (Flutter App application), Flutter Module (Flutter module), Flutter Plugin, Flutter Package (pure Dart / Flutter component package), Flutter Skeleton (Flutter App template application) and Flutter FFI Plugin (Flutter external function interface plug-in). The other is mainly aimed at hybrid application development. The corresponding Flutter project type is Flutter Module, which describes the generation of Flutter binary products, a binary product corresponding to the Flutter source code, which cannot reduce the package size and compilation time of the corresponding Flutter Plugin (mobile application software file), but can only improve the building efficiency for hybrid mobile application development, and cannot be used for any Flutter project type that uses Flutter Plugin (such as Flutter App\Flutter Module\Flutter As can be seen from the above, how to expand the scope of application of mobile application software application package generation, improve the efficiency of mobile application software application package generation, reduce the size of mobile application software plug-in products on the server, reduce developer download time, and reduce server resource usage are issues to be solved in this field.

[0048] See also Figure 1 As shown, the embodiment of the present invention discloses a method for generating a mobile application software application package, which may specifically include:

[0049] Step S11: determining the local mobile application software plug-in types, and adding a mobile application development framework dependency to the corresponding mobile application platform according to the mobile application software plug-in types.

[0050] In this embodiment, the mobile application software environment is determined according to the current project information and business needs, and then the types of mobile application software plug-ins are determined from the mobile application software environment. According to the types of mobile application software plug-ins, the mobile application development framework dependency is added to the corresponding mobile application platform. This application will add the Flutter Framework dependency (i.e., add the mobile application development framework dependency) for each platform at each end of the Flutter Plugin (Android\iOS\Web\MacOS) based on the Flutter environment where the current project is located, to prevent the problem of missing Flutter Framework dependencies when the code on each end is built.

[0051] Step S12: constructing each binary file according to each mobile application software plug-in type and the corresponding mobile application development framework dependency, and saving each binary file and the corresponding mobile application development framework dependency to each binary file storage warehouse.

[0052] In this embodiment, the language architecture information of the mobile application platform is determined, and then the binary files are constructed according to the language architecture information, the mobile application software plug-in type and the corresponding mobile application development framework dependency, and then the binary files and the corresponding mobile application development framework dependency are saved to the binary file storage warehouse.

[0053] Step S13: performing a removal operation on the local platform-side code to obtain each platform application package, and determining dependency information corresponding to the platform application package from the binary file storage repository.

[0054] Step S14: generating target mobile application software application packages based on the platform application package and the corresponding dependency information.

[0055] In this embodiment, a target application package generation method is determined from a preset application package generation method; the target application package generation method is used to utilize a local platform-side integration module, and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information.

[0056] Specifically, the local platform-side integration module can be utilized by hooking the compilation process, and each target mobile application software application package can be generated based on the platform application package and the corresponding dependency information; or, the local platform-side integration module can be utilized by modifying the bytecode, and each target mobile application software application package can be generated based on the platform application package and the corresponding dependency information.

[0057] The specific process of this application is as follows Figure 2As shown, the specific steps are as follows: (1) According to the Flutter environment where the current project is located, determine the type of each mobile application software plug-in (i.e., Android\iOS\Web\MacOS), and add the Flutter Framework dependency to each mobile application platform corresponding to each mobile application software plug-in type to prevent the problem of missing Flutter Framework dependencies when each end code is built; (2) Execute the command to build the target platform product: build each binary file according to the type of each mobile application software plug-in and the mobile application development framework dependency; (3) All binary products are integrated: obtain a collection of all binary files and upload the binary files to the binary file storage warehouse; (4) The remaining compilation process: remove the local platform side code to obtain each platform application package, and determine the dependency information corresponding to the platform application package from the binary file storage warehouse; (5) Output the target platform product: generate each target mobile application software application package based on the platform application package and the corresponding dependency information by hooking the compilation process or modifying the bytecode.

[0058] In this embodiment, the local mobile application software plug-in type is determined, and the mobile application development framework dependency is added to the corresponding mobile application platform according to the mobile application software plug-in type; each binary file is constructed according to the mobile application software plug-in type and the corresponding mobile application development framework dependency, and each binary file and the corresponding mobile application development framework dependency are saved to each binary file storage warehouse; the local platform side code is removed to obtain each platform application package, and the dependency information corresponding to the platform application package is determined from the binary file storage warehouse; and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information. This application adopts the principle of divide and conquer, distributing events that previously required centralized processing into various stages, and packaging and integration are completely independent, effectively solving the problem of construction time. In addition, this application can reduce the compilation and construction time of Flutter App or Flutter Module in scenarios where it depends on a large number of Flutter Plugins, improve development efficiency, avoid compilation errors of the main project due to source code modifications of sub-modules, effectively reduce the size of the Flutter Plugin product on the pub server, reduce developer download time, and also reduce the resource usage of the pub server.

[0059] See also Figure 3 As shown, the embodiment of the present invention discloses a method for generating a mobile application software application package, which may specifically include:

[0060] Step S21: determining the local mobile application software plug-in types, and adding a mobile application development framework dependency to the corresponding mobile application platform according to the mobile application software plug-in types.

[0061] Step S22: construct each binary file according to each mobile application software plug-in type and the corresponding mobile application development framework dependency, determine each binary file storage warehouse corresponding to each mobile application software plug-in type, and then save each binary file and the corresponding mobile application development framework dependency to the corresponding binary file storage warehouse according to each mobile application software plug-in type.

[0062] Step S23: Use the local mobile application software construction module to remove the local platform side code to obtain each platform application package, and then upload each platform application package to each binary file storage warehouse in the form of a mobile application software plug-in, and determine the dependency information corresponding to the platform application package from the binary file storage warehouse.

[0063] Step S24: Generate target mobile application software application packages based on the platform application package and the corresponding dependency information.

[0064] This application includes two functional modules: Flutter Plugin construction module and platform-side integration module. The specific module workflow is as follows Figure 4 As shown in the figure, its corresponding functions are as follows: (1) Flutter Plugin construction module: mainly responsible for the construction of Dart code in Flutter Plugin and the code on each platform side (Android / iOS / MacOS / Web). Among them, each platform side will be separately built with the target binary product of each platform as the target (such as Andoir's AAR product, iOS's Framework product), and then published to the binary product hosting warehouse of each platform side (Maven on the Android side / Specs on the iOS side). Then, the current Flutter Plugin code is published in the form of flutter Plugin to the Dart / Flutter binary product hosting warehouse (that is, binary file storage warehouse) Pub. Before that, it is necessary to shield the code directory of each platform side in its code according to certain rules (that is, remove the local platform side code to obtain the application package of each platform). At this point, a standard Flutter Plugin publishes multiple binary files to the binary product hosting warehouse of each platform separately; (2) Platform side integration module: such as Figure 4As shown in the figure, although the final binary product of the Flutter Plugin published to Pub is still the original tar.gz compressed package, the native code on each platform side is removed during the custom compilation phase. As a result, the Flutter compilation tool believes that this Flutter Plugin is not adapted to the target platform. Compared with the process in the existing technology, all dependent plugins are not compiled and are relied upon in source code form. In addition, the corresponding compilation commands into binary products are not executed for all plugins that are relied upon in source code form (because they are no longer relied upon in source code), which saves a lot of time for binary compilation and search verification.

[0065] The specific Flutter Plugin processing method for this application is as follows Figure 5 As shown, it is mainly responsible for building the Dart code in the Flutter Plugin and the code on each platform side (Android / iOS / MacOS / Web). Each platform side will be built separately with the target binary product of each platform as the target (such as Andoir's AAR product and iOS's Framework product), and then published to the binary product hosting repository on each platform side (Maven on the Android side / Specs on the iOS side). Then, the current Flutter Plugin code is reduced and published to the Dart / Flutter binary product hosting repository Pub in the form of Flutter Plugin. Before that, the code directories on each platform side in its code need to be shielded according to certain rules. At this point, a standard Flutter Plugin publishes multiple binary files separately to the binary product hosting repository of each platform.

[0066] In this embodiment, the local mobile application software plug-in type is determined, and the mobile application development framework dependency is added to the corresponding mobile application platform according to the mobile application software plug-in type; each binary file is constructed according to the mobile application software plug-in type and the corresponding mobile application development framework dependency, and each binary file and the corresponding mobile application development framework dependency are saved to each binary file storage warehouse; the local platform side code is removed to obtain each platform application package, and the dependency information corresponding to the platform application package is determined from the binary file storage warehouse; and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information. This application adopts the principle of divide and conquer, distributing events that previously required centralized processing into various stages, and packaging and integration are completely independent, effectively solving the problem of construction time. In addition, this application can reduce the compilation and construction time of Flutter App or Flutter Module in scenarios where it depends on a large number of Flutter Plugins, improve development efficiency, avoid compilation errors of the main project due to source code modifications of sub-modules, effectively reduce the size of the Flutter Plugin product on the pub server, reduce developer download time, and also reduce the resource usage of the pub server.

[0067] See also Figure 6 As shown, the embodiment of the present invention discloses a mobile application software application package generation device, which may specifically include:

[0068] The dependency adding module 11 is used to determine the local mobile application software plug-in type and add the mobile application development framework dependency to the corresponding mobile application platform according to the mobile application software plug-in type;

[0069] A binary file construction module 12 is configured to construct binary files according to the types of the mobile application software plug-ins and the corresponding mobile application development framework dependencies, and save the binary files and the corresponding mobile application development framework dependencies to binary file storage repositories;

[0070] A code removal module 13 is configured to remove the local platform-side code to obtain each platform application package, and determine dependency information corresponding to the platform application package from the binary file storage repository;

[0071] The application package generation module 14 is configured to generate application packages of target mobile application software based on the platform application package and the corresponding dependency information.

[0072] In this embodiment, the local mobile application software plug-in type is determined, and the mobile application development framework dependency is added to the corresponding mobile application platform according to the mobile application software plug-in type; each binary file is constructed according to the mobile application software plug-in type and the corresponding mobile application development framework dependency, and each binary file and the corresponding mobile application development framework dependency are saved to each binary file storage warehouse; the local platform side code is removed to obtain each platform application package, and the dependency information corresponding to the platform application package is determined from the binary file storage warehouse; and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information. This application adopts the principle of divide and conquer, distributing events that previously required centralized processing into various stages, and packaging and integration are completely independent, effectively solving the problem of construction time. In addition, this application can reduce the compilation and construction time of Flutter App or Flutter Module in scenarios where it depends on a large number of Flutter Plugins, improve development efficiency, avoid compilation errors of the main project due to source code modifications of sub-modules, effectively reduce the size of the Flutter Plugin product on the pub server, reduce developer download time, and also reduce the resource usage of the pub server.

[0073] In some specific embodiments, the dependency adding module 11 may specifically include:

[0074] The environment determination module is used to determine the mobile application software environment based on current project information and business requirements;

[0075] The plug-in type determination module is used to determine the type of each mobile application software plug-in from the mobile application software environment.

[0076] In some specific embodiments, the binary file construction module 12 may specifically include:

[0077] A language architecture information determination module, configured to determine the language architecture information of the mobile application platform;

[0078] The binary file construction module is used to construct each binary file according to each of the language architecture information, each of the mobile application software plug-in types and the corresponding mobile application development framework dependencies.

[0079] In some specific embodiments, the binary file construction module 12 may specifically include:

[0080] A storage repository determining module, configured to determine each of the binary file storage repositories corresponding to each of the mobile application software plug-in types;

[0081] The dependency saving module is used to save each of the binary files and the corresponding mobile application development framework dependencies to the corresponding binary file storage warehouses according to the type of each mobile application software plug-in.

[0082] In some specific embodiments, the code removal module 13 may specifically include:

[0083] A code removal module is used to remove the local platform-side code using the local mobile application software construction module to obtain application packages for each platform;

[0084] The application package uploading module is used to upload each platform application package to each binary file storage warehouse in the form of a mobile application software plug-in.

[0085] In some specific embodiments, the application package generation module 14 may specifically include:

[0086] A target application package generation method determination module, configured to determine a target application package generation method from among preset application package generation methods;

[0087] The application package generation module is used to adopt the target application package generation method and utilize the local platform side integration module to generate each target mobile application software application package based on the platform application package and the corresponding dependency information.

[0088] In some specific embodiments, the application package generation module 14 may specifically include:

[0089] a first target application package generation method determination module, configured to utilize a local platform-side integration module by hooking a compilation process, and generate each target mobile application software application package based on the platform application package and the corresponding dependency information;

[0090] The second target application package generation method determination module is used to utilize the local platform side integration module by modifying the bytecode, and generate each target mobile application software application package based on the platform application package and the corresponding dependency information.

[0091] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps of the method for generating a mobile application software package performed by the electronic device as disclosed in any of the aforementioned embodiments.

[0092] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device. The communication protocol it follows is any communication protocol that can be applied to the technical solution of this application and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world. Its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0093] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or CD, etc. The resources stored thereon include an operating system 221, a computer program 222 and data 223, etc. The storage method can be temporary storage or permanent storage.

[0094] The operating system 221 is used to manage and control the hardware devices and computer program 222 on the electronic device 20 to enable the processor 21 to calculate and process the data 223 in the memory 22. It can be Windows, Unix, Linux, etc. In addition to including a computer program capable of completing the mobile application software application package generation method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 may further include computer programs capable of completing other specific tasks. In addition to including data transmitted from an external device and received by the mobile application software application package generation device, the data 223 may also include data collected by its own input and output interface 25.

[0095] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0096] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium, in which a computer program is stored. When the computer program is loaded and executed by a processor, the steps of the mobile application software application package generation method disclosed in any of the aforementioned embodiments are implemented.

[0097] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0098] The above is a detailed introduction to the mobile application software application package generation method, device, equipment and storage medium provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, based on the ideas of the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A method for generating a mobile application software application package, characterized in that: include: Determine the local mobile application software plug-in types, and add mobile application development framework dependencies to the corresponding mobile application platform according to the mobile application software plug-in types; Constructing binary files according to the types of the mobile application software plug-ins and the corresponding mobile application development framework dependencies, and saving the binary files and the corresponding mobile application development framework dependencies to binary file storage repositories; Performing a removal operation on the local platform-side code to obtain each platform application package, and determining dependency information corresponding to the platform application package from the binary file storage repository; Generate target mobile application software application packages based on the platform application package and the corresponding dependency information; By hooking the compilation process, the local platform-side integration module is utilized, and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information; or, by modifying the bytecode, the local platform-side integration module is utilized, and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information.

2. The method for generating a mobile application software package according to claim 1, wherein: The determining of the types of local mobile application software plug-ins includes: Determine the mobile application software environment based on current project information and business needs; The types of mobile application software plug-ins are determined from the mobile application software environment.

3. The method for generating a mobile application software package according to claim 1, wherein: The binary files are constructed according to the types of the mobile application software plug-ins and the corresponding mobile application development framework dependencies, including: Determining language architecture information of the mobile application platform; Binary files are constructed based on the language architecture information, the mobile application software plug-in type, and the corresponding mobile application development framework dependencies.

4. The method for generating a mobile application software package according to claim 1, wherein: Saving the binary files and the corresponding mobile application development framework dependencies to the binary file storage repositories includes: Determining each of the binary file storage repositories corresponding to each of the mobile application software plug-in types; According to the type of each mobile application software plug-in, each binary file and the corresponding mobile application development framework dependency are saved to the corresponding binary file storage warehouse.

5. The method for generating a mobile application software package according to claim 1, wherein: The local platform side code is removed to obtain the application packages of each platform, including: Utilize local mobile application software building blocks to remove local platform-side codes to obtain application packages for each platform; Upload each of the platform application packages to each of the binary file storage repositories in the form of a mobile application software plug-in.

6. The method for generating a mobile application software package according to any one of claims 1 to 5, wherein: The generating of each target mobile application software application package based on the platform application package and the corresponding dependency information includes: Determine a target application package generation method from preset application package generation methods; The target application package generation method utilizes a local platform-side integration module and generates target mobile application software application packages based on the platform application package and the corresponding dependency information.

7. A mobile application software application package generation device, characterized in that: include: A dependency adding module is used to determine the local mobile application software plug-in type and add the mobile application development framework dependency to the corresponding mobile application platform according to the mobile application software plug-in type; A binary file construction module, configured to construct each binary file according to each mobile application software plug-in type and the corresponding mobile application development framework dependency, and save each binary file and the corresponding mobile application development framework dependency to each binary file storage repository; A code removal module is used to remove the local platform-side code to obtain each platform application package, and determine the dependency information corresponding to the platform application package from the binary file storage repository; An application package generation module, configured to generate application packages of target mobile application software based on the platform application package and the corresponding dependency information; By hooking the compilation process, the local platform-side integration module is utilized, and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information; or, by modifying the bytecode, the local platform-side integration module is utilized, and each target mobile application software application package is generated based on the platform application package and the corresponding dependency information.

8. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the method for generating a mobile application software application package according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that Used to store a computer program; wherein, when the computer program is executed by a processor, the method for generating a mobile application software application package as described in any one of claims 1 to 6 is implemented.

Images