CN108399071B - Application program installation package size processing method, device, equipment and storage medium - Google Patents
Application program installation package size processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN108399071B CN108399071B CN201810055343.6A CN201810055343A CN108399071B CN 108399071 B CN108399071 B CN 108399071B CN 201810055343 A CN201810055343 A CN 201810055343A CN 108399071 B CN108399071 B CN 108399071B
- Authority
- CN
- China
- Prior art keywords
- file
- version
- size
- installation package
- executable
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The embodiment of the invention provides a processing method, a device, equipment and a storage medium for the size of an application program installation package, which are characterized in that the file size of each executable file of a first version of an APP installation package is obtained, the file sizes of the executable files and the executable files with the same file identification in a second version of the APP installation package are compared aiming at each executable file in the first version, the file identification of the executable files with the file size larger than that of the same file identification in the second version in the first version is obtained, early warning information is generated according to the file identification of the executable files with the file size larger than that of the same file identification in the second version in the first version, and the early warning information is output, so that the accuracy and the efficiency of processing the size of the APP installation package are improved.
Description
Technical Field
The present invention relates to computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing an Application (APP) installation package size.
Background
With the increase of services, the size of the APP installation package may also increase continuously, however, the size of the APP installation package may affect the amount of users downloading APPs, for example: if the iOS-based APP installation package is larger than 100M, the AppStore limits the downloading of the APP installation package in the 4G environment, and therefore, the optimization of the size of the APP installation package is particularly important.
In the prior art, developers manually search some obvious redundant files and delete or modify the redundant files so as to reduce the size of the APP installation package.
However, with the prior art method, the accuracy of processing the size of the APP installation package is not high.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a storage medium for processing the size of an application program installation package, which are used for improving the accuracy of processing the size of an APP installation package.
In a first aspect, an embodiment of the present invention provides a method for processing an application installation package size, where the method includes:
acquiring the file size of each executable file of the first version of the application program installation package;
for each executable file in the first version, comparing the file size of the executable file with the file size of the executable file identified by the same file in the second version of the application installation package;
acquiring a first file identifier, wherein the file size corresponding to the first file identifier in the first version is larger than the file size corresponding to the first file identifier in the second version;
and generating early warning information according to the first file identifier, and outputting the early warning information.
Optionally, before comparing, for each executable file in the first version, the file size of the executable file with that of an executable file identified by the same file in the second version of the application installation package, the method further includes:
and storing the identification of each executable file and the corresponding file size in a database according to the file identification and the corresponding file size of each executable file in the second version of the application program installation package.
Optionally, the method further comprises:
acquiring a second file identifier, wherein the file size corresponding to the second file identifier of the first version is smaller than the file size corresponding to the second file identifier of the second version;
and updating the file size corresponding to the second file identifier in the database according to the file size corresponding to the second file identifier of the first version.
Optionally, the executable file includes an executable file generated by source code compilation of the application installation package and an executable file in a static library called by the application installation package, and the static library includes an a library or a framework library.
Optionally, the outputting the warning information includes:
and outputting the early warning information through mails, short messages or instant messaging software.
Optionally, before outputting the warning information through an email, a short message, or an instant messaging software, the method further includes:
and storing the first file identification.
Optionally, the generating early warning information according to the first file identifier includes:
and generating early warning information according to the sequence of the file sizes corresponding to the first file identifications and the first N first file identifications with the largest file size, wherein N is an integer greater than or equal to 1.
In a second aspect, an embodiment of the present invention provides an apparatus for processing an application installation package size, including:
the first acquisition module is used for acquiring the file size of each executable file of the first version of the application program installation package;
a processing module, configured to compare, for each executable file in the first version, a file size of the executable file with a file size of an executable file identified by the same file in the second version of the application installation package;
a second obtaining module, configured to obtain a first file identifier, where a file size corresponding to the first file identifier in the first version is larger than a file size corresponding to the first file identifier in the second version;
the processing module is further used for generating early warning information according to the first file identifier;
and the sending module is used for outputting the early warning information.
In a third aspect, an embodiment of the present invention provides an electronic device, including:
a memory for storing program instructions;
and the processor is used for calling and executing the program instructions in the memory so as to realize the processing method of the size of the application program installation package in the first aspect.
In a fourth aspect, an embodiment of the present invention provides a readable storage medium, in which a computer program is stored, and when at least one processor of a processing apparatus of an application installation package size executes the computer program, the processing apparatus of the application installation package size executes the processing method of the application installation package size according to the first aspect.
According to the processing method, device, equipment and storage medium for the size of the application program installation package, the file size of each executable file of the first version of the APP installation package is obtained, the file sizes of the executable files in the first version and the executable files with the same file identification in the second version of the APP installation package are compared for each executable file in the first version, the file identification of the executable files in the first version with the size larger than that of the executable files in the second version with the same file identification is obtained, early warning information is generated according to the file identification of the executable files in the first version with the size larger than that of the executable files in the second version with the same file identification, and the early warning information is output, so that the accuracy and the efficiency of processing the size of the APP installation package are improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic flow chart of a processing method for processing an APP installation package size according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of another APP installation package size processing method according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of another method for processing the size of the APP installation package according to the embodiment of the present invention;
fig. 4 is a schematic structural diagram of an APP installation package size processing apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of another processing apparatus for processing an APP installation package size according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another processing apparatus for processing an APP installation package size according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The vocabulary explanation that the embodiment of the invention may relate to:
1. electronic devices, including but not limited to Mobile Stations (MS), Mobile terminals (Mobile Terminal), Mobile phones (Mobile Telephone), Mobile phones (handset), portable devices (portable equipment), etc., may communicate with one or more core networks via a Radio Access Network (RAN), for example, the electronic devices may be Mobile phones (or "cellular" phones), computers with wireless communication functions, etc., and the electronic devices may also be portable, pocket, hand-held, computer-embedded or vehicle-mounted Mobile devices or devices.
2. The APP is a third-party application program on the electronic device, and is also called a client, such as an online shopping APP, a local service APP, a financial APP, a search APP, and the like.
The APP installation package comprises source code and a static library, wherein the source code is compiled to generate an executable file (. O file), and the static library can be an a library or a framework library, and the a library and the framework library comprise a plurality of executable files (. O files).
The embodiment of the invention aims at the same APP, and determines which executable files have larger file sizes by comparing the sizes of the executable files of the APP installation packages of the front and the back versions to obtain the early warning information and output the early warning information, thereby improving the accuracy and efficiency of processing the size of the APP installation package.
The technical solution of the present invention will be described in detail below with specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.
Fig. 1 is a flowchart of a processing method for processing the size of an APP installation package according to an embodiment of the present invention, where the method may be applied to an optimization process before the APP installation package is online, and may be executed by any device having processing and communication functions, where the device may be a device in the same computer as a development environment of the APP installation package, or may be an independent device, and thus, the embodiment of the present invention is not limited. The method of this embodiment is shown in fig. 1:
s101: and obtaining the file size of each executable file of the first version of the APP installation package.
To the same APP, the APP installation package is often updated continuously due to the addition, optimization, deletion, or the like of the business function, and therefore, the same APP installation package may have different versions, for example: according to the development time, the APP installation package of an APP comprises an APPV1.0, an APPV2.0, … …, an APPVN.0 and the like. For convenience of description, in the embodiments of the present invention, an APP version to be currently optimized is referred to as a first version, and a previous version of the APP version or a preset standard version is referred to as a second version.
Wherein, the APP installation package includes source code and static storehouse, and executable file includes: the method comprises the steps of generating an executable file after source codes of an APP installation package are compiled, and generating an executable file contained in a static library called by the APP installation package, wherein the static library comprises an a library or a framework library.
One possible way to obtain the file size of each executable file of the first version of the APP installation package is as follows:
the compiling option "Write Link Map File" value is set to "YES" to start compiling the APP installation package, and a Link Map File is generated under the "Path to Link Map File" directory, for example: MyAPP-LinkMap-normal-arm64.txt, the LinkMap file is mainly composed of three Sections, namely Object files, Sections and Symbols. Object files list all class files and their numbers, Sections list code fragment and data fragment storage locations and sizes, and Symbols list detailed locations and sizes of properties and methods in each class.
The LinkMap file is analyzed mainly by combining the Object files segment and the Symbols segment in the LinkMap file. Specifically, a plurality of dic < keys, value > are generated, where the value of a key is determined by traversing the file number in the Object files segment, and the value is a custom model, which sets two attributes, for example: name (name) and size (size) of the file, model. The Object files segment determines that the number in < key, value > corresponds to the model. And determining the size value of the model corresponding to the number in the < key, value > through the Symbols section. Therefore, a plurality of dic < keys, values > are obtained, that is, the file number and the file name of the APP installation package and the file size of the corresponding executable file are obtained, and thus, the file size of each executable file of the first version of the APP installation package is obtained.
Optionally, the obtained several dic < key, value > may also be preprocessed, for example: removing dic < key, value > corresponding to an executable file with a file size smaller than a certain value (for example, 10KB) in the executable file generated by the source code from a plurality of dic < key, value >; and/or removing dic < key, value > corresponding to M executable files with minimum file sizes of the executable files in the a library or the framework library from a plurality of dic < key, value >, wherein M is an integer greater than or equal to 1.
S103: and for each executable file in the first version, comparing the file size of the executable file with the file size of the executable file identified by the same file in the second version of the APP installation package.
Wherein the second version is developed earlier than the first version.
The file identifier may be a file name, a file number, or other identifiers capable of identifying a file, which is not limited in this application.
One possible implementation manner of this step may be to create a database, create a table in the database, and set a plurality of fields in the table for recording the comparison result, as shown in table 1, the fields in table 1 include: obj _ name, belong _ lib, size _ add, is _ new, remarks and the like; wherein, the obj _ name is used for storing and compiling to obtain an executable file name; the belong _ lib is used for storing a static library (a library or a frame library) to which the executable file belongs; size is used to store the size of the executable file; the size _ add is used for storing the increment compared with the second version, the is _ new is used for storing whether the file is a new file, and remarks are used for supplementing the description.
TABLE 1
S105: and acquiring a first file identifier.
And the file size corresponding to the first file identifier in the first version is larger than the file size corresponding to the first file identifier in the second version.
For example: with reference to table 1, for the a library or the framework library, if the file size is larger than the file size of xx.a and xx.framework in the second version, the file size in xx.a and xx.framework in the first version is compared to the first R executable files, and the file identifier of the executable file whose file size is larger than the same file identifier in the second version in the first N executable files in the first version is obtained as the first file identifier. For the rest executable files, such as myapp.
The first file identification includes: exec, myapp; xx.a; xx.a (yy.o); xx (yy.o); o.
S107: and generating early warning information according to the first file identifier, and outputting the early warning information.
According to a possible implementation manner, the early warning information may be generated according to the sequence of the file sizes corresponding to the first file identifiers and the first N first file identifiers with the largest file size, where N is an integer greater than or equal to 1. In combination with table 1: exec file size of myapp 20000 KB; a file size of 2000 KB; xx.a (yy.o) has a file size of 8 KB; xx (yy.o) has a file size of 10 KB; the file size of yy.o is 15 KB. And assuming that N is 2, generating early warning information according to MyApp. And when the value of N is greater than the number of all the first file identifications, generating early warning information according to all the first file identifications.
Optionally, the warning information may be output by mail, short message, or instant messaging software.
Optionally, before outputting the first warning information, the first file identifier may be stored, for example: the first file identification is stored in a temporary file.
In this embodiment, by obtaining the file size of each executable file of the first version of the APP installation package, for each executable file in the first version, comparing the file size of the executable file with the same file identifier in the second version of the APP installation package, obtaining the file identifier of the executable file with the file size larger than the same file identifier in the second version in the first version, generating the early warning information according to the file identifier of the executable file with the file size larger than the same file identifier in the second version in the first version, and outputting the early warning information, thereby improving the processing efficiency on the size of the APP installation package.
Fig. 2 is a schematic flow diagram of another processing method for processing the size of an APP installation package according to an embodiment of the present invention, where fig. 2 is based on the embodiment shown in fig. 1, optionally before S103, further includes S102, as shown in fig. 2:
s101, obtaining the file size of each executable file of the first version of the APP installation package.
S102: and storing the identification of each executable file and the corresponding file size in the database according to the file identification and the corresponding file size of each executable file in the second version of the application program.
The file identification and the corresponding file size of each executable file in the second version are stored in the database, so that the file sizes of each executable file in the first version and the executable file with the same file identification in the second version are compared conveniently.
S103: and for each executable file in the first version, comparing the file size of the executable file with the file size of the executable file identified by the same file in the second version of the APP installation package.
S105: and acquiring a first file identifier.
S107: and generating early warning information according to the first file identifier, and outputting the early warning information.
The detailed descriptions of S101, S103, S105, and S107 refer to the detailed description in the embodiment shown in fig. 1, and are not repeated here.
In this embodiment, by obtaining the file size of each executable file in the first version of the APP installation package, storing the identifier of each executable file and the corresponding file size in the database according to the file identifier and the corresponding file size of each executable file in the second version of the application program, thereby facilitating the comparison of the file sizes of each executable file in the first version and the executable file with the same file identifier in the second version, for each executable file in the first version, comparing the file sizes of the executable file and the executable file with the same file identifier in the second version of the APP installation package, obtaining the file identifier of the executable file with the file size larger than the same file identifier in the second version in the first version, and generating the warning information according to the file identifiers of the executable files with the file sizes larger than the same file identifier in the second version in the first version, and outputting early warning information, thereby improving the processing efficiency of the APP installation package size.
Fig. 3 is a schematic flow diagram of another processing method for APP installation package size according to an embodiment of the present invention, where fig. 3 is based on the embodiment shown in fig. 2, and optionally, after S103, may further include: s108 and S109, wherein S108 and S109 are executed after S103, as shown in fig. 3:
s101, obtaining the file size of each executable file of the first version of the APP installation package.
S102: and storing the identification of each executable file and the corresponding file size in a database according to the file identification and the corresponding file size of each executable file in the second version of the application program.
S103: and for each executable file in the first version, comparing the file size of the executable file with the file size of the executable file identified by the same file in the second version of the APP installation package.
S105: and acquiring a first file identifier.
S107: and generating early warning information according to the first file identifier, and outputting the early warning information.
S108: and acquiring a second file identifier.
And the file size corresponding to the second file identifier of the first version is smaller than the file size corresponding to the second file identifier of the second version.
S109: and updating the file size corresponding to the second file identifier in the database according to the file size corresponding to the second file identifier of the first version.
The detailed descriptions of S101, S102, S103, and S105 refer to the detailed description in the embodiment shown in fig. 2, and are not repeated here.
In this embodiment, on the basis of the embodiment shown in fig. 2, the second file identifier is obtained, and the file size corresponding to the second file identifier in the database is updated, so that the smallest file size of each executable file is maintained in the database all the time, and thus, a developer makes reference when optimizing the size of the APP installation package.
Fig. 4 is a schematic structural diagram of an apparatus for processing an APP installation package size according to an embodiment of the present invention, where the apparatus includes a first obtaining module 401, a processing module 402, a second obtaining module 403, and a sending module 404, where the first obtaining module 401 is configured to obtain a file size of each executable file of a first version of the APP installation package; the processing module 402 is configured to compare, for each executable file in the first version, a file size of the executable file with an executable file identified by the same file in the second version of the APP installation package; the second obtaining module 403 is configured to obtain a first file identifier, where a file size corresponding to the first file identifier in the first version is larger than a file size corresponding to the first file identifier in the second version; the processing module 402 is further configured to generate early warning information according to the first file identifier; the sending module 404 is configured to output the warning information.
Optionally, the executable file includes an executable file generated by source code compilation of the APP installation package and an executable file in a static library called by the APP installation package, where the static library includes an a library or a framework library.
Optionally, the sending module 404 is specifically configured to output the warning information through an email, a short message, or an instant messaging software.
Optionally, the processing module 402 is specifically configured to generate the early warning information according to the first N first file identifiers with the largest file size according to the sequence of the file sizes corresponding to the first file identifiers, where N is an integer greater than or equal to 1.
The apparatus of this embodiment may be correspondingly used to implement the technical solution of the method embodiment shown in fig. 1, and the implementation principle thereof is not described herein again.
In this embodiment, the file size of each executable file of the first version of the APP installation package is obtained through the first obtaining module, the processing module compares the file size of the executable file with the same file identifier in the second version of the APP installation package for each executable file in the first version, the second obtaining module obtains the file identifier of the executable file with the file size larger than the same file identifier in the second version in the first version, the processing module generates the early warning information according to the file identifier of the executable file with the file size larger than the same file identifier in the second version in the first version, and outputs the early warning information, so that the accuracy and efficiency of processing the size of the APP installation package are improved.
Fig. 5 is a schematic structural diagram of another processing apparatus for processing an APP installation package size according to an embodiment of the present invention, and fig. 5 is a schematic structural diagram of the embodiment shown in fig. 4, further including a storage module 405, where before the processing module compares, for each executable file in the first version, the file sizes of the executable file and the executable file with the same file identifier in the second version of the APP installation package, the storage module is configured to store, in a database, the identifier of each executable file and the corresponding file size according to the file identifier and the corresponding file size of each executable file in the second version of the APP installation package.
The apparatus of this embodiment may be correspondingly used to implement the technical solution of the method embodiment shown in fig. 2, and the implementation principle thereof is similar, which is not described herein again.
In this embodiment, the file size of each executable file of the first version of the APP installation package is obtained through the first obtaining module, the storage module stores the identifier of each executable file and the corresponding file size in the database according to the file identifier and the corresponding file size of each executable file in the second version of the APP installation package, so as to compare the file sizes of each executable file in the first version and the executable file with the same file identifier in the second version, the processing module compares the file sizes of the executable file with the same file identifier in the second version of the APP installation package for each executable file in the first version, the second obtaining module obtains the file identifier of the executable file with the same file identifier in the first version and the file identifier of the executable file with the same file identifier in the second version, and the processing module obtains the file identifiers of the executable files with the same file identifier in the second version according to the file sizes of the first version and the executable files with the same file identifier in the second version And generating early warning information, and outputting the early warning information by a sending module, thereby improving the processing efficiency of the APP installation package size.
On the basis of the embodiment shown in fig. 5, the second obtaining module 403 is further configured to obtain a second file identifier, where a file size corresponding to the second file identifier of the first version is smaller than a file size corresponding to the second file identifier of the second version; the storage module 405 is further configured to update the file size corresponding to the second file identifier in the database according to the file size corresponding to the second file identifier of the first version.
The apparatus of this embodiment may be correspondingly used to implement the technical solution of the method embodiment shown in fig. 3, and the implementation principle thereof is similar, which is not described herein again.
In this embodiment, the second file identifier is acquired through the second acquisition module, and the storage module updates the file size corresponding to the second file identifier in the database, so that the smallest file size of each executable file is maintained in the database all the time, and thus, a developer can refer to the optimized size of the APP installation package.
In the embodiments of the apparatus of the present invention, the functional modules may be divided according to the processing apparatus whose APP installation package size is exemplified by the method described above, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that the division of the modules in the embodiments of the present invention is schematic, and is only a logical function division, and there may be another division manner in actual implementation.
Fig. 6 is a schematic structural diagram of another processing apparatus for processing an APP installation package size according to an embodiment of the present invention, including: a memory 61 and a processor 62, wherein the memory 61 is used for storing program instructions, and the memory may be a flash (flash memory). And the processor 62 is configured to call and execute the program instructions in the memory to implement the steps in the processing method for the APP installation package size shown in any one of fig. 1 to 3. Reference may be made in particular to the description relating to the preceding method embodiment.
Alternatively, the memory 61 may be separate, or the memory 61 may be integrated with the processor 62.
An embodiment of the present invention further provides an electronic device, where the electronic device is configured to execute each step in the processing method for the APP installation package size shown in any one of fig. 1 to fig. 3.
The present invention also provides a readable storage medium, in which a computer program is stored, and when at least one processor of an APP installation package size processing apparatus executes the computer program, the APP installation package size processing apparatus executes any one of the methods described in fig. 1 to 3.
The present invention also provides a program product comprising a computer program, the computer program being stored in a readable storage medium. The computer program may be readable from a readable storage medium by at least one processor of the APP installation package size processing apparatus, and execution of the computer program by the at least one processor causes the APP installation package size processing apparatus to implement the method described in any of fig. 1-3.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A processing method for application program installation package size is characterized by comprising the following steps:
acquiring the file size of each executable file of the first version of the application program installation package; the first version is a current version to be optimized;
for each executable file in the first version, comparing the file size of the executable file with the file size of the executable file identified by the same file in the second version of the application installation package; the second version is a previous version or a preset standard version of a current version to be optimized;
acquiring a first file identifier, wherein the file size corresponding to the first file identifier in the first version is larger than the file size corresponding to the first file identifier in the second version;
and generating early warning information according to the first file identifier, and outputting the early warning information.
2. The method of claim 1, wherein comparing, for each executable file in the first version, the file size of the executable file to an executable file identified by the same file in the second version of the application installation package further comprises:
and storing the identification of each executable file and the corresponding file size in a database according to the file identification and the corresponding file size of each executable file in the second version of the application program installation package.
3. The method of claim 2, further comprising:
acquiring a second file identifier, wherein the file size corresponding to the second file identifier of the first version is smaller than the file size corresponding to the second file identifier of the second version;
and updating the file size corresponding to the second file identifier in the database according to the file size corresponding to the second file identifier of the first version.
4. The method of any of claims 1-3, wherein the executable files include executable files generated by source code compilation of the application installation package and executable files in a static library called by the application installation package, the static library including an a library or a framework library.
5. The method of any one of claims 1-3, wherein the outputting the early warning information comprises:
and outputting the early warning information through mails, short messages or instant messaging software.
6. The method of claim 5, wherein before outputting the warning message via mail, text message or instant messaging software, the method further comprises:
and storing the first file identification.
7. The method according to any one of claims 1-3, wherein generating early warning information according to the first file identifier comprises:
and generating early warning information according to the sequence of the file sizes corresponding to the first file identifications and the first N first file identifications with the largest file size, wherein N is an integer greater than or equal to 1.
8. An apparatus for processing an application installation package size, comprising:
the first acquisition module is used for acquiring the file size of each executable file of the first version of the application program installation package; the first version is a current version to be optimized;
a processing module, configured to compare, for each executable file in the first version, a file size of the executable file with a file size of an executable file identified by the same file in the second version of the application installation package; the second version is a previous version or a preset standard version of a current version to be optimized;
a second obtaining module, configured to obtain a first file identifier, where a file size corresponding to the first file identifier in the first version is larger than a file size corresponding to the first file identifier in the second version;
the processing module is further used for generating early warning information according to the first file identifier;
and the sending module is used for outputting the early warning information.
9. An electronic device, comprising:
a memory for storing program instructions;
a processor for calling and executing the program instructions in the memory to implement the processing method of the application installation package size of any one of claims 1 to 7.
10. A readable storage medium in which a computer program is stored, wherein when at least one processor of an application installation package size processing apparatus executes the computer program, the application installation package size processing apparatus executes the application installation package size processing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810055343.6A CN108399071B (en) | 2018-01-19 | 2018-01-19 | Application program installation package size processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810055343.6A CN108399071B (en) | 2018-01-19 | 2018-01-19 | Application program installation package size processing method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108399071A CN108399071A (en) | 2018-08-14 |
| CN108399071B true CN108399071B (en) | 2021-07-20 |
Family
ID=63094072
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810055343.6A Active CN108399071B (en) | 2018-01-19 | 2018-01-19 | Application program installation package size processing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108399071B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110333874B (en) * | 2019-06-10 | 2022-09-23 | 腾讯科技(成都)有限公司 | iOS system installation packet data acquisition method, device, equipment and medium |
| CN110795114B (en) * | 2019-10-29 | 2023-08-01 | 北京五八信息技术有限公司 | Method and device for monitoring application program installation package capacity, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103853574A (en) * | 2012-12-06 | 2014-06-11 | 腾讯科技（深圳）有限公司 | Method and system for upgrading software |
| CN104239091A (en) * | 2014-08-25 | 2014-12-24 | 北京金山安全软件有限公司 | File cleaning method and device and terminal |
| CN104407905A (en) * | 2014-12-16 | 2015-03-11 | 北京奇虎科技有限公司 | Deep cleaning and updating method and device |
| CN106354647A (en) * | 2016-08-31 | 2017-01-25 | 腾讯科技（深圳）有限公司 | Application detection method and server |
| CN106484771A (en) * | 2016-09-09 | 2017-03-08 | 腾讯科技（深圳）有限公司 | Different information file generated and application process, device |
| CN106547597A (en) * | 2016-11-21 | 2017-03-29 | 北京小米移动软件有限公司 | The control method and device of application program update |
| CN106648712A (en) * | 2017-02-27 | 2017-05-10 | 百度在线网络技术（北京）有限公司 | Incremental updating packet generating method and device, and server |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170235558A1 (en) * | 2014-03-26 | 2017-08-17 | NetSuite Inc. | System and method for recapture and rebuild of application definition from installed instance |
-
2018
- 2018-01-19 CN CN201810055343.6A patent/CN108399071B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103853574A (en) * | 2012-12-06 | 2014-06-11 | 腾讯科技（深圳）有限公司 | Method and system for upgrading software |
| CN104239091A (en) * | 2014-08-25 | 2014-12-24 | 北京金山安全软件有限公司 | File cleaning method and device and terminal |
| CN104407905A (en) * | 2014-12-16 | 2015-03-11 | 北京奇虎科技有限公司 | Deep cleaning and updating method and device |
| CN106354647A (en) * | 2016-08-31 | 2017-01-25 | 腾讯科技（深圳）有限公司 | Application detection method and server |
| CN106484771A (en) * | 2016-09-09 | 2017-03-08 | 腾讯科技（深圳）有限公司 | Different information file generated and application process, device |
| CN106547597A (en) * | 2016-11-21 | 2017-03-29 | 北京小米移动软件有限公司 | The control method and device of application program update |
| CN106648712A (en) * | 2017-02-27 | 2017-05-10 | 百度在线网络技术（北京）有限公司 | Incremental updating packet generating method and device, and server |
Non-Patent Citations (1)
| Title |
|---|
| 冗余文件自动清理软件的设计与分析;邹洪;《中国数字电视》;20110331;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108399071A (en) | 2018-08-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108415708B (en) | Application program installation package size processing method, device, equipment and storage medium | |
| US9678723B2 (en) | Application programming interface (API) engine | |
| CN105302587B (en) | Data-updating method and device | |
| US8689204B2 (en) | Methods and tools for creation of read-only-memory software binary images and corresponding software patches | |
| EP3432141A1 (en) | Mobile terminal application update method and device | |
| CN106681749B (en) | Local code patch updating method and device based on android platform | |
| CN107729014B (en) | Page jump method and structure based on Android | |
| CN108958730B (en) | Application program component sharing method and device, terminal device and readable storage medium | |
| CN108399071B (en) | Application program installation package size processing method, device, equipment and storage medium | |
| CN111859470A (en) | Business data chaining method and device | |
| CN106055375B (en) | Application program installation method and device | |
| CN1886976B (en) | Method and apparatus for performing actions on a wireless device using action lists and versioning | |
| CN109408594B (en) | Cross-chain data retrieval system based on block chain | |
| CN106101358A (en) | A kind of method of contact person information updating and smart machine | |
| CN111045683A (en) | Applet code compiling method, device, equipment and medium | |
| CN105740298A (en) | File processing method and apparatus, and server-side equipment | |
| CN114153856A (en) | Host data double-writing method and device | |
| US20070011157A1 (en) | Systems and methods for application management and related devices | |
| CN108920246B (en) | Form draft component sharing method and device, terminal device and readable storage medium | |
| CN109587353B (en) | Method, device and storage medium for identifying short message number attribution information | |
| CN112101023B (en) | Text processing method and device and electronic equipment | |
| CN107451050B (en) | Function acquisition method and device and server | |
| CN112579129A (en) | Software updating method, device, equipment and storage medium based on server | |
| CN101651932B (en) | Multimedia message mass-sending method and multimedia message center | |
| CN113360178B (en) | Method, device and equipment for generating unique software identification code and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |