WO2019001335A1

WO2019001335A1 - Application program packaging method and device and terminal device

Info

Publication number: WO2019001335A1
Application number: PCT/CN2018/092165
Authority: WO
Inventors: 黄银锋
Original assignee: 广州优视网络科技有限公司
Priority date: 2017-06-29
Filing date: 2018-06-21
Publication date: 2019-01-03
Also published as: CN107315593A

Abstract

An application program packaging method and device, and a terminal device. The application program packaging method comprising: acquiring a compressed file generated in the process of converting a Java file to a DEX file (S101); decompressing the compressed file to obtain a decompressed file, the decompressed file comprising a specified file (S102); selecting the specified file from the decompressed file (S103); converting the specified file to a second DEX file (S104); and compressing the second DEX file into an application file to obtain the application program (105). The provided application program packaging method and device and the terminal device package separately a module of a specific package name into a second DEX file and package a part of independent services into a second DEX file during the packaging process of an Android application program, so that the services are loaded when a user needs the services and the process of immediately loading the services upon start-up is avoided. Therefore, the problem of long start-up time is solved; a better service mode is provided; and basic packaging support is provided for a dynamic loading scheme.

Description

Application packaging method, device and terminal device

Cross reference

The present application claims the following priority: Application No.: 201710530952.8, entitled: "Application Package Method, Apparatus, and Terminal Equipment", the entire contents of which are hereby incorporated by reference.

Technical field

The present invention relates to the field of the Internet, and specifically provides an application package method, apparatus, and terminal device.

Background technique

At present, Android development tool AndrodStudio in the application packaging process, due to the Android virtual machine mechanism, the number of methods is defined in 65,535, if the number of functions exceeds 65,535, the virtual machine can not properly load the DEX file. Therefore, it will cause the Android application to report an error. In order to solve this problem, Google introduced a multidex solution when the application was packaged. The Multidex solution is to divide the DEX file of more than 65,535 methods into multiple DEX files, and then load and merge back when the application starts, bypassing the Android virtual machine can not load 65,535 programs, multidex introduction, Although the number of methods is more than 65,535, it does not meet the business expansion requirements, because multidex cannot be freely subcontracted according to the service package name. Therefore, the requirements for dividing a specific function code into a specific DEX file required by the Android componentized business cannot be satisfied.

Summary of the invention

In view of this, an object of the embodiments of the present invention is to provide an application package method, apparatus, and terminal device, which are intended to implement a solution in which an Android specific service code can be divided into specific DEX files when packaged.

In order to achieve the above objective, the technical solution adopted by the embodiment of the present invention is as follows:

In a first aspect, an embodiment of the present invention provides an application packaging method, where the method includes: acquiring a compressed file generated in a process of converting a Java file into a first DEX file, wherein the first DEX file is used to compress Entering an application file to obtain an application; decompressing the compressed file to obtain a decompressed file, the decompressed file including a specified file; selecting a specified file from the decompressed file; converting the specified file into a second DEX file; The second DEX file is pushed into the application file to obtain the application.

In a second aspect, an embodiment of the present invention provides an application package device, where the device includes an acquisition module, a decompression module, a selection module, and a packaging module. The obtaining module is configured to obtain a compressed file generated in a process of converting a Java file into a first DEX file, where the first DEX file is used to be pressed into an application file to obtain an application; and the decompression module is configured to decompress the compression. The file is decompressed, the decompressed file includes a specified file, a selection module is configured to select the specified file from the decompressed file, a conversion module is configured to convert the specified file into a second DEX file, and a packaging module is configured to: The second DEX file is pushed into the application file to get the application.

In a third aspect, an embodiment of the present invention provides a terminal device, including a processor, a memory, and an application packaging device. The application packaging device is installed in the memory and includes one or more software function modules executed by the processor, the application packaging device including an acquisition module, a decompression module, a selection module, and a packaging module. The obtaining module is configured to obtain a compressed file generated in a process of converting a Java file into a first DEX file, where the first DEX file is used to be pressed into an application file to obtain an application; and the decompression module is configured to decompress the compression. The file is decompressed, the decompressed file includes a specified file, a selection module is configured to select the specified file from the decompressed file, a conversion module is configured to convert the specified file into a second DEX file, and a packaging module is configured to: The second DEX file is pushed into the application file to get the application.

In a fourth aspect, an embodiment of the present invention provides a computer readable storage medium, where the one or more programs are stored, and the one or more programs are executed by a terminal device that includes multiple applications. When the terminal device is caused to perform the following operations:

Obtaining a compressed file generated in a process of converting a Java file into a first DEX file, wherein the first DEX file is used to be pressed into an application file to obtain an application;

Decompressing the compressed file to obtain a decompressed file, where the decompressed file includes a specified file;

Selecting the specified file from the decompressed file;

Converting the specified file into a second DEX file;

The second DEX file is pushed into an application file to obtain the application.

The application package method, apparatus, and terminal device provided by the embodiment of the present invention, the application package method includes: acquiring a compressed file generated in a process of converting a Java file into a first DEX file, wherein the first DEX file is used for Pressing into the application file to obtain an application; decompressing the compressed file to obtain a decompressed file, the decompressed file including a specified file; selecting the specified file from the decompressed file; converting the specified file into a second DEX file; The second DEX file is pushed into the application file to obtain the application. The application package method, device and terminal device provided by the invention package the module of the specific package name into the second DEX file in the package process of the Android application, and package the partial independent service into the second DEX file, which is used by the user. When you go to the service, you can load it again, you don't have to load it immediately when you start it, avoid the problem of long startup time, have better business model, and provide basic packaging support for dynamic loading scheme.

The aspects and advantages of the present invention will be set forth in part in the description which follows.

DRAWINGS

The above and/or additional aspects and advantages of the present invention will become apparent and readily understood from

FIG. 1 is a schematic block diagram of a terminal device according to an embodiment of the present invention.

FIG. 2 is a flowchart of an application packaging method according to an embodiment of the present invention.

FIG. 3 is a schematic diagram of splitting a DEX file in the prior art.

4 is a schematic diagram of splitting a DEX file according to an embodiment of the present invention.

FIG. 5 is a schematic structural diagram of a function module of an application packaging apparatus 110 according to an embodiment of the present invention.

Icon: 100-terminal device; 110-application packaging device; 111-acquisition module; 112-decompression module; 113-selection module; 114-conversion module; 115-packaging module; 116-registration module; 117-compression module; - memory; 130-processor.

Detailed ways

The embodiments of the present application are described in detail below, and the examples of the embodiments are illustrated in the drawings, wherein the same or similar reference numerals are used to refer to the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are intended to be illustrative only, and are not to be construed as limiting.

It should be noted that similar reference numerals and letters indicate similar items in the following figures. Therefore, once an item is defined in one figure, it is not necessary to further define and explain it in the subsequent figures.

The application package method and device provided by the embodiments of the present invention are applied to a terminal device. The terminal device may be, but not limited to, a personal computer (PC), a server.

Please refer to FIG. 1, which is a block diagram of the terminal device 100. The terminal device 100 includes an application packaging device 110, a memory 120, and a processor 130.

The memory 120 and the processor 130 are electrically connected directly or indirectly to each other to implement data transmission or interaction. For example, the components can be electrically connected to one another via one or more communication buses or signal lines. The application packaging device 110 includes at least one software function module that can be stored in the memory 120 or solidified in an operating system (OS) of the terminal device 100 in the form of software or firmware. The processor 130 is configured to execute executable modules stored in the memory 120, such as software function modules, computer programs, and the like included in the application package device 110.

The memory 120 can be, but not limited to, a random access memory (RAM), a read only memory (ROM), and a programmable read-only memory (PROM). Erasable Programmable Read-Only Memory (EPROM), Electric Erasable Programmable Read-Only Memory (EEPROM), and the like. The memory 120 is used to store a program, and the processor 130 executes the program after receiving the execution instruction. Access to the memory 120 by the processor 130 and other possible components can be performed under the control of the memory controller 140.

The processor 130 can be an integrated circuit chip with signal processing capabilities. The processor 130 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., and may also be a digital signal processor (DSP), an application specific integrated circuit ( ASICs, Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present invention. The general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

The application packaging method provided by the embodiment of the present invention is applied to the terminal device 100. Referring to FIG. 2, the application packaging method includes the following steps:

Step S101: Acquire a compressed file generated during conversion of a Java file into a DEX file.

The packager needs to convert the Java code file into the first DEX file when packaging the source file implemented in Java code into an application. Before the Java tool file is optimized to the first DEX file, the package tool needs to be a jar compression file. The jar compression file is a executable code collection file compiled by the Java code, and the jar compression file is generated and then packaged into the first DEX file. In the embodiment of the present invention, the packaging tool is a Gradle packaging tool. By writing a plug-in and using a command, the jar compression file that needs to be converted into the first DEX file is forcibly extracted, such as main.jar and proguard.jar, and the extraction command may be task.doFirst.

Step S102, decompressing the compressed file to obtain a decompressed file, where the decompressed file includes a specified file.

The decompressed file includes a plurality of function codes, each of which has its own specific function. In the componentized service, the function code that needs to be used is delivered through built-in or online, thereby reducing the package. In the embodiment of the present invention, the specified file is a function code that needs to be separately converted into the second DEX file.

Step S103, selecting a specified file from the decompressed file.

Step S104, converting the specified file into a second DEX file.

In this embodiment, the specified file is converted into the second DEX file by the Gradle tool, and the conversion is performed according to a predetermined package path during the conversion process, so that the specific service is selected later, and the package path is obtained by pre-registration. Specifically, the specified file is placed in a preset folder according to a predetermined package path, and then the specified file is recompressed, and the compressed file is converted into a second DEX file by the Gradle tool.

Step S105, pressing the second DEX file into an application file to obtain the application.

After the function codes that need to be separately packaged into the second DEX file are all converted into the second DEX file, the converted second DEX file is pushed into the application file to obtain an application. This application file is an application package generated by the Gradle tool.

In this embodiment, for a non-designated file (a file other than the specified file in the function code), it is recompressed, and the compressed file before decompression is replaced, and then the compressed file is packaged by the Gradle tool to generate an application file.

Step S106, performing signature verification on the application.

Through the above steps, the packaging process of the application is completed, and the packaged application includes a plurality of second DEX files, each of which has a separate function service, and when the user needs to use a certain service in the later stage, Loading the second DEX file corresponding to the service does not need to be loaded immediately at startup, thereby avoiding the problem of long startup time. In order to make the embodiment of the present invention easier to understand, please refer to FIG. 3, which is a schematic diagram of dividing a DEX file of more than 65535 methods into a plurality of DEX files (ie, a first DEX file) in the prior art. Among them, the function business in which the DEX file is split into DEX1, DEX2, DEX3...DEX files is disrupted, and may be merged into multiple DEXs that are split, for example, for functional service 1, merged in DEX1 and DEX2, Functional service 2 is integrated in DEX2 and DEX3. To implement functional service 1 and functional service 2, it is necessary to load DEX1, DEX2 and DEX3 in sequence, which will undoubtedly increase the startup time. The application packaged by the application package method provided by the embodiment of the present invention refers to FIG. 4, because each function service is separately packaged and converted into a DEX file (ie, a second DEX file) according to requirements during the packaging process, so each needs to be used. The function business is a separate DEX file (ie the second DEX file), wherein the DEX file is split into DEX1', DEX2', DEX3'... Function Service 1 is packaged in DEX1', and Function Service 2 is packaged in DEX2 'In the case, for example, when the user needs to use the function service 2, only need to load DEX2', no need to load DEX1' first, then load DEX2', and no need to load DEX3', saving startup time and meeting the needs of componentized business. , to achieve a dynamic loading scheme.

5 is a schematic diagram of a functional module architecture of an application packaging apparatus 110 according to an embodiment of the present invention. The application packaging apparatus 110 includes an obtaining module 111, a decompression module 112, a selection module 113, a conversion module 114, and a packaging module 115.

The obtaining module 111 is configured to obtain a compressed file generated during conversion of the Java file into the first DEX file, where the first DEX file is used to be pressed into the application file to obtain an application.

In this embodiment, the obtaining module 111 is configured to perform step S101. The packager needs to convert the Java code file into the first DEX file when packaging the source file implemented in Java code into an application. Before the Java tool file is optimized to the first DEX file, the package tool needs to be a jar compression file. The jar compression file is a executable code collection file compiled by the Java code, and the jar compression file is generated and then packaged into the first DEX file. In the embodiment of the present invention, the packaging tool is a Gradle packaging tool. By writing a plug-in and using a command, the jar compression file that needs to be converted into the first DEX file is forcibly extracted, such as main.jar and proguard.jar, and the extraction command may be task.doFirst.

The decompression module 112 is configured to decompress the compressed file to obtain a decompressed file.

In this embodiment, the decompression module 112 can be used to perform step S102. The decompressed file includes a plurality of function codes, each of which has its own specific function. In the componentized service, the function code that needs to be used is delivered through built-in or online, thereby reducing the package. In the embodiment of the present invention, the specified file is a function code that needs to be separately converted into the second DEX file.

The selection module 113 is configured to select the specified file from the decompressed file.

In this embodiment, the selection module 113 can be used to perform step S103.

The conversion module 114 is configured to convert the specified file into a second DEX file.

In this embodiment, the conversion module 114 can be used to perform step S104. In this embodiment, the specified file is converted into the second DEX file by the Gradle tool, and the conversion is performed according to a predetermined package path during the conversion process, so that the specific service is selected later, and the package path is obtained by pre-registration. Specifically, the specified file is placed in a preset folder according to a predetermined package path, and then the specified file is recompressed, and the compressed file is converted into a second DEX file by the Gradle tool. The application package device 110 provided by the embodiment of the present invention further includes a registration module 116 for registering a package path.

The packaging module 115 is configured to push the second DEX file into an application file to obtain the application.

In this embodiment, the packaging module 115 can be used to perform step S105. After the function codes that need to be separately packaged as the second DEX file are all converted into the second DEX file, the converted second DEX file is pushed into the application file to obtain an application. This application file is an application package generated by the Gradle tool.

Further, the application packaging device 110 further includes a compression module 117, for non-designated files (files other than the specified file in the function code), will be recompressed, replaced in the compressed file before decompression, and then passed through the Gradle tool. Package the compressed file to generate an application file. The compression module 117 is configured to compress the non-specified file and replace the compressed file.

The application packaging device 110 can also include a signature module for performing signature verification on the application.

In summary, the embodiment of the present invention provides an application package method, device, and terminal device. The application packaging method includes: obtaining a compressed file generated during conversion of the Java file into the first DEX file; decompressing the compressed file to obtain a decompressed file, the decompressed file including the specified file; and selecting the specified file from the decompressed file; Converting the specified file into a second DEX file; pushing the second DEX file into an application file to obtain the application. The application package method, device and terminal device provided by the invention package the module of the specific package name into the second DEX file in the package process of the Android application, and package the partial independent service into the second DEX file, which is used by the user. When you go to the service, you can load it again, you don't have to load it immediately when you start it, avoid the problem of long startup time, have better business model, and provide basic packaging support for dynamic loading scheme.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may also be implemented in other manners. The apparatus embodiments described above are merely illustrative, for example, the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and functionality of possible implementations of apparatus, methods, and computer program products according to various embodiments of the invention. operating. In this regard, each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the DEX instruction. It should also be noted that, in some alternative implementations, the functions noted in the blocks may also occur in a different order than those illustrated in the drawings. For example, two consecutive blocks may be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts, can be implemented in a dedicated hardware-based system that performs the specified function or function. Or it can be implemented by a combination of dedicated hardware and computer instructions.

In addition, each functional module in each embodiment of the present invention may be integrated to form a separate part, or each module may exist separately, or two or more modules may be integrated to form a separate part.

The functions, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. . It should be noted that, in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities or operations. There is any such actual relationship or order between them. Furthermore, the term "comprises" or "comprises" or "comprises" or any other variations thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements includes not only those elements but also Other elements, or elements that are inherent to such a process, method, item, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention. It should be noted that similar reference numerals and letters indicate similar items in the following figures. Therefore, once an item is defined in one figure, it is not necessary to further define and explain it in the subsequent figures.

Claims

An application packaging method, the method comprising:

Obtaining a compressed file generated in a process of converting a Java file into a first DEX file, wherein the first DEX file is used to be pressed into an application file to obtain an application;

Decompressing the compressed file to obtain a decompressed file, where the decompressed file includes a specified file;

Selecting the specified file from the decompressed file;

Converting the specified file into a second DEX file;

The second DEX file is pushed into an application file to obtain the application.
The application packaging method according to claim 1, wherein the specified file is a function code that needs to be separately converted into a second DEX file;

The second DEX file has a separate functional service.
The application packaging method according to claim 1, wherein the converting the specified file into the second DEX file comprises:

Converting the specified file into a second DEX file in a predetermined package path.
The application packaging method according to claim 3, wherein the step of generating the second DEX file by the specified file according to a predetermined package path comprises:

Putting the specified file into a preset folder according to a predetermined package path;

Compressing the specified file;

Converting the compressed specified file into a second DEX file.
The application packaging method according to claim 3, wherein the method further comprises:

Register the package path.
The application packaging method according to any one of claims 1 to 5, wherein the decompressing file includes a non-designated file, the method further comprising:

Compress the non-specified file and replace the compressed file.
The application packaging method according to claim 6, wherein the step of compressing the non-designated file back into the compressed file further comprises the steps of:

The compressed file continues to be packaged by the Gradle tool to generate the application file.
The application packaging method according to claim 1, wherein the method further comprises:

Perform signature verification on the application.
An application packaging device, characterized in that the device comprises:

An obtaining module, configured to obtain a compressed file generated in a process of converting a Java file into a first DEX file, where the first DEX file is used to be pressed into an application file to obtain an application;

a decompression module, configured to decompress the compressed file to obtain a decompressed file, where the decompressed file includes a specified file;

a selection module, configured to select a specified file from the decompressed file;

a conversion module, configured to convert the specified file into a second DEX file;

a packaging module, configured to push the second DEX file into an application file to obtain the application.
The application packaging device according to claim 9, wherein the specified file is a function code that needs to be separately converted into a second DEX file;

The second DEX file has a separate functional service.
The application packaging apparatus according to claim 9, wherein said conversion module is configured to convert said specified file into a second DEX file in a predetermined package path.
The application package device according to claim 11, wherein the conversion module is configured to put the specified file into a preset folder according to a predetermined package path, compress the specified file, and compress the file. The specified file is converted into a second DEX file.
The application packaging apparatus according to claim 11, wherein said apparatus further comprises a registration module for registering said packet path.
The application packaging apparatus according to any one of claims 9-13, wherein said decompressing file comprises a non-designated file, said apparatus further comprising a compression module for compressing the non-specified file and replacing said compression file.
The application packaging apparatus according to claim 14, wherein the packaging module is further configured to continue to package the compressed file to generate the application file by using a Gradle tool.
The application packaging apparatus according to claim 9, wherein said apparatus further comprises a signature module for performing signature verification on said application.
A terminal device, comprising:

processor;

Memory;

An application packaging device, the application packaging device being installed in the memory and comprising one or more software function modules executed by the processor, the application packaging device comprising:

An obtaining module, configured to obtain a compressed file generated in a process of converting a Java file into a first DEX file, where the first DEX file is used to be pressed into an application file to obtain an application;

a decompression module, configured to decompress the compressed file to obtain a decompressed file, where the decompressed file includes a specified file;

a selection module, configured to select a specified file from the decompressed file;

a conversion module, configured to convert the specified file into a second DEX file;

a packaging module, configured to push the second DEX file into an application file to obtain the application.
A computer readable storage medium storing one or more programs, the one or more programs, when executed by a terminal device including a plurality of applications, causing the terminal device to perform the following operations :

Obtaining a compressed file generated in a process of converting a Java file into a first DEX file, wherein the first DEX file is used to be pressed into an application file to obtain an application;

Decompressing the compressed file to obtain a decompressed file, where the decompressed file includes a specified file;

Selecting the specified file from the decompressed file;

Converting the specified file into a second DEX file;

The second DEX file is pushed into an application file to obtain the application.