Update Method, Device, Storage Medium and Electronic Device for Compiling Project Files

Abstract

An embodiment of the present invention provides a method, device, storage medium, and electronic device for updating a compiled project file. The method includes: determining a first version of a first compiled project file of a target client, and determining a second version of a second compiled project file on which the first compiled project file depends; determining a local version of the first compiled project file based on the first version and the second version; determining a server version of the first compiled project file stored in a target server, where the target server is connected to the target client; in the case where the local version is inconsistent with the server version, obtaining a server-side version file corresponding to the first compiled project file from the target server; and updating the first compiled project file based on the server-side version file. Through the present invention, the problem of low efficiency in updating compiled project files in the related art is solved, and the effect of improving the update efficiency of compiled project files is achieved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computers, and in particular, to a method, device, storage medium, and electronic device for updating a compiled project file. Background Art

[0002] With the expansion of business and the increase of functions, the client will continuously iterate and update versions. During the version update process, there are usually two methods to let users update the program. One is to provide a new complete program installation package for users to download and install. The other is to provide an incremental update solution, such as maintaining an md5 checksum of all files, obtaining this file from the server, comparing it with the local one, and downloading the files with inconsistent md5. However, in the first method, when only a few files are changed, a large program installation package still needs to be downloaded, wasting bandwidth. In the second method, there may be a considerable number of dynamic library files in the program, and their functions remain unchanged in adjacent program versions. By the strategy of judging whether files are the same through the file md5 checksum, these dynamic library files will be considered different and need to be updated.

[0003] It can be seen that there are problems with the efficiency of updating compiled project files in the related art.

[0004] In view of the above problems existing in the related art, no effective solution has been proposed yet. Summary of the Invention

[0005] The embodiments of the present invention provide a method, device, storage medium, and electronic device for updating a compiled project file, so as to at least solve the problem of the efficiency of updating compiled project files existing in the related art.

[0006] According to an embodiment of the present invention, a method for updating a compiled project file is provided, including: determining a first version of a first compiled project file of a target client, and determining a second version of a second compiled project file on which the first compiled project file depends, where the first version is the current version of the first compiled project file, and the second version is the current version of the second compiled project file; determining a local version of the first compiled project file based on the first version and the second version; determining a server version of the first compiled project file stored in a target server, where the target server is connected to the target client; in the case where the local version is inconsistent with the server version, obtaining a server-side version file corresponding to the first compiled project file from the target server; and updating the first compiled project file based on the server-side version file.

[0007] According to another embodiment of the present invention, there is provided an update device for compiling project files, including: a first determination module, configured to determine a first version of a first compiled project file of a target client, and determine a second version of a second compiled project file on which the first compiled project file depends, where the first version is the current version of the first compiled project file, and the second version is the current version of the second compiled project file; a second determination module, configured to determine a local version of the first compiled project file based on the first version and the second version; a third determination module, configured to determine a server version of the first compiled project file stored in a target server, where the target server is connected to the target client; an acquisition module, configured to, when the local version is inconsistent with the server version, acquire a server-side version file corresponding to the first compiled project file from the target server; and an update module, configured to update the first compiled project file based on the server-side version file.

[0008] According to still another embodiment of the present invention, there is also provided a computer-readable storage medium storing a computer program, where the computer program, when executed by a processor, implements the steps of the method described in any one of the above.

[0009] According to still another embodiment of the present invention, there is also provided an electronic device including a memory and a processor, where the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0010] Through the present invention, a first version of a first compiled project file of a target client is determined, and a second version of a second compiled project file on which the first compiled project file depends is determined. The local version of the first compiled project file is determined based on the first version and the second version. The server version of the first compiled project file existing in the target server is determined. When the local version is inconsistent with the server version, a server-side version file corresponding to the first compiled project file is acquired from the target server, and the first compiled project file is updated based on the server-side version file. Since when determining the first compiled project file, it can be determined according to the current version of the first compiled project file and the current version of the compiled project file on which the first compiled project file depends, that is, only when the first compiled project file or the second compiled project file on which it depends is updated, the first compiled project file is updated, and there is no need to update other files. Therefore, the problem of the efficiency of updating compiled project files in the related art can be solved, and the effect of improving the update efficiency of compiled project files can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1It is a hardware structure block diagram of a mobile terminal for an update method of a compiled project file according to an embodiment of the present invention;

[0012] Figure 2 It is a flowchart of a method for updating a compiled project file according to an embodiment of the present invention;

[0013] Figure 3 It is a schematic diagram of each compiled project file included in a target client according to an exemplary embodiment of the present invention;

[0014] Figure 4 It is a schematic diagram of the dependency relationship of each compiled project file included in a target client according to an exemplary embodiment of the present invention;

[0015] Figure 5 It is a schematic diagram of the dependency relationship of each compiled project file with a version number according to an exemplary embodiment of the present invention;

[0016] Figure 6 It is a schematic diagram of the interaction between a target client and a target server according to an exemplary embodiment of the present invention;

[0017] Figure 7 It is a structure block diagram of an update device for a compiled project file according to an embodiment of the present invention. Detailed implementation manners

[0018] In the following, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in conjunction with the embodiments.

[0019] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence.

[0020] The method embodiments provided in the embodiments of the present application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 It is a hardware structure block diagram of a mobile terminal for an update method of a compiled project file according to an embodiment of the present invention. As Figure 1 shown, the mobile terminal may include one or more ( Figure 1 only one is shown in Figure 1 a processor 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. Among them, the above-mentioned mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those of ordinary skill in the art can understand that Figure 1more or fewer components shown, or having a configuration different from that Figure 1 shown.

[0021] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the update method of the compilation project file in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, the above-mentioned method is implemented. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely provided with respect to the processor 102, and these remote memories can be connected to the mobile terminal through a network. Examples of the above network include but are not limited to the Internet, intranet, local area network, mobile communication network, and combinations thereof.

[0022] The transmission device 106 is used to receive or send data via a network. Specific examples of the above network may include a wireless network provided by a communication provider of the mobile terminal. In one instance, the transmission device 106 includes a network adapter (abbreviated as NIC), which can be connected to other network devices through a base station and thus can communicate with the Internet. In one instance, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0023] In this embodiment, a method for updating a compilation project file is provided. Figure 2 is a flowchart of the method for updating a compilation project file according to the embodiment of the present invention, as Figure 2 shown, and the process includes the following steps:

[0024] Step S202, determining the first version of the first compilation project file of the target client, and determining the second version of the second compilation project file on which the first compilation project file depends, where the first version is the current version of the first compilation project file, and the second version is the current version of the second compilation project file;

[0025] Step S204, determining the local version of the first compilation project file based on the first version and the second version;

[0026] Step S206, determining the server version of the first compilation project file stored in the target server, where the target server is connected to the target client;

[0027] Step S208, in the case where the local version is inconsistent with the server version, obtain the server-side version file corresponding to the first compilation project file from the target server;

[0028] Step S210, update the first compilation project file based on the server-side version file.

[0029] In the above embodiment, the target client may be an application client, and the first compilation project file and the second compilation project file may be compilation product files of the project under the target client, such as dynamic libraries, executable files, etc.

[0030] In the above embodiment, the dependency relationships between the various compilation project files of the target client may be determined, the second compilation project file on which the first compilation project file depends may be determined according to the dependency relationships, and the first version and the second version of the first compilation project file and the second compilation project file may be determined, and the local version of the first compilation project file may be determined according to the first version and the second version. For example, the local version may be determined according to the size relationship between the first version and the second version, or the local version may be determined according to the sequence of the first version and the second version.

[0031] In the above embodiment, the server version of each compilation project file of the target client stored in the target table server may be requested from the target server, and it may be determined whether the local version of the first compilation project file needs to be updated based on the server version. When the server version is consistent with the local version, there is no need to update. When the server version is inconsistent with the local version, the server-side version file stored in the target server may be obtained, and the server-side version file may be parsed and installed locally.

[0032] In the above embodiment, when the first compilation project file and the second compilation project file are dynamic libraries, in a project hosted by a version control system (such as svn / git, etc.), it may be considered that the version number of the dynamic library in its product is the version number of the current project directory. However, from the perspective of actual development, since the dependency directories or files of each dynamic library are different, its version can be more refined. Without loss of generality, a schematic diagram of each compilation project file included in the target client can be seen in the appendix Figure 3 , such as Figure 3 As shown, this project has five project directories A, B, C, D, E and two dependency directories Include and Lib, and finally generates five dynamic libraries (taking the generation of dll for a windows program as an example). Assume that the dependency relationships of each dynamic library are as follows: A does not depend on other directories; B depends on Include; C depends on Include and Lib; D depends on C; E depends on C, Include and Lib. A schematic diagram of the dependency relationships of each compilation project file included in the target client can be seen in the appendix Figure 4 , such asFigure 4 As shown, if there are file code modifications only in Project A among the function modifications of a certain version, then the functions of the four dynamic libraries B, C, D, and E are the same as those of the previous version. Only Project A needs to be updated during incremental update; if there are file code modifications in Project B, then only Project B needs to be updated during incremental update; if there are file code modifications in Project C, then Projects C, D, and E need to be updated during incremental update; if there are file code modifications in Project D, then only Project D needs to be updated during incremental update; if there are file code modifications in Project E, then only Project E needs to be updated during incremental update; if there are file code modifications in the Include directory, then Projects B, C, D, and E need to be updated during incremental update; if there are file code modifications in the Lib directory, then Projects C, D, and E need to be updated during incremental update.

[0033] Optionally, the execution subject of the above steps may be the target client, or other devices with similar processing capabilities, or a machine integrated with at least a data processing device. Among them, the data processing device may include terminals such as computers and mobile phones, but is not limited thereto.

[0034] Through the present invention, the first version of the first compilation project file of the target client is determined, and the second version of the second compilation project file on which the first compilation project file depends is determined. The local version of the first compilation project file is determined according to the first version and the second version, and the server version of the first compilation project file existing in the target server is determined. In the case where the local version is inconsistent with the server version, the server-side version file corresponding to the first compilation project file is obtained from the target server, and the first compilation project file is updated according to the server-side version file. Since when determining the first compilation project file, it can be determined according to the current version of the first compilation project file and the current version of the compilation project file on which the first compilation project file depends, that is, only when the first compilation project file or the second compilation project file on which it depends is updated, the first compilation project file is updated, and there is no need to update other files. Therefore, the problem of the update efficiency of the compilation project file existing in the related art can be solved, and the effect of improving the update efficiency of the compilation project file can be achieved.

[0035] In an exemplary embodiment, determining the first version of the first compilation project file of the target client includes: determining the first version number of the first compilation project file of the target client, and determining the first version number as the first version; determining the second version of the second compilation project file on which the first compilation project file depends includes: determining the second version number of the second compilation project file, and determining the second version number as the second version. In this embodiment, when determining the first version and the second version, the first version number of the first compilation project file can be determined as the first version, and the second version number of the second compilation file can be determined as the second version.

[0036] In an exemplary embodiment, determining the local version of the first compilation project file based on the first version and the second version includes: comparing the first version and the second version to obtain a comparison result; and determining the local version based on the comparison result. In this embodiment, the size relationship or the sequence relationship between the first version and the second version can be compared, and the local version is determined according to the comparison result.

[0037] In the above embodiment, for a project hosted by svn, the local version can be determined according to the size relationship of the version numbers of the compilation project files. For a project hosted by git, the time of the commit record can be obtained, and the size of the timestamp is used as the basis for version comparison.

[0038] In an exemplary embodiment, determining the local version based on the comparison result includes: when the comparison result indicates that the first version is greater than or equal to the second version, determining the first version as the local version; and when the comparison result indicates that the first version is less than the second version, determining the second version as the local version. In this embodiment, in a project hosted by svn, each folder and each file has a commit version number. Before project compilation, for each project, the version numbers of the directories it depends on and its own directory are respectively obtained, and the largest one is taken as the version number of the current project product. If there is a new commit record in the directory it depends on or its own directory, then the version number of this project product is larger than before. Otherwise, the version number of this project product is the same as before. Before project compilation, the version number of the project directory itself and the version numbers of the dependent directories or files are sequentially obtained, and the maximum value is taken as the version number of the current project product. This version number can be saved to a file, and when packaging the project, this file is also packaged together. For incremental updates, first obtain the version file on the server side, compare it with the local version file, find the files with inconsistent versions, and incrementally download and update them from the server side.

[0039] In an exemplary embodiment, before determining the first version of the first compilation project file of the target client and determining the second version of the second compilation project file on which the first compilation project file depends, the method further includes: determining the first compilation data and the first version number corresponding to the first compilation project file, and determining the second compilation data and the second version number corresponding to the second compilation project file; packing the first compilation data and the first version number into a first data packet, and packing the second compilation data and the second version number into a second data packet; determining the first data packet as the first compilation file, and determining the second data packet as the second compilation file. In this embodiment, before project compilation, the version number of the project directory itself and the version numbers of the dependent directories or files are sequentially obtained, and the maximum value is taken as the version number of the current project product. This version number can be saved to a file, and when the project is packaged, this file is also packaged together. Among them, a schematic diagram of the dependency relationship of each compilation project file with a version number can be seen in Appendix Figure 5 。

[0040] In an exemplary embodiment, the first compilation project file includes one of the following: a dynamic library file, an executable file, the second compilation project file includes one of the following: a dynamic library file, an executable file, and the first compilation project file and the second compilation project file are of the same type. In this embodiment, the compilation project files included in the target client can be updated based on the version number increment. Among them, the compilation project files can be compilation product files, such as dynamic libraries and executable files, etc.

[0041] In the above embodiment, for non-compilation product files such as pictures, text files, and configuration files included in the target client, the md5 checksum method can be combined to achieve incremental update. When updating the target client, these two methods can be combined to achieve a better incremental update effect.

[0042] In an exemplary embodiment, determining the server version of the first compilation project file stored in the target server includes: sending version request information to the target server; receiving the version file sent by the target server based on the version request information; determining the server version based on the version file. In this embodiment, the target client can send version request information for requesting a version file to the target server. The target server returns a version file according to the version request information. The target client can determine the files that need to be updated according to the version file, and send a request for an incremental update file to the target server. The target server returns an incremental update file, that is, a server-side version file. The target client can parse and install the server-side version file to implement the update of the compilation project file. Among them, a schematic diagram of the interaction between the target client and the target server can be seen in Appendix Figure 6 。

[0043] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions for causing a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present invention.

[0044] In this embodiment, an update device for a compilation project file is further provided. This device is used to implement the above embodiments and preferred implementation manners, and those that have been described will not be repeated. As used hereinafter, the term "module" can be a combination of software and / or hardware that can achieve a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0045] Figure 7 is a structural block diagram of an update device for a compilation project file according to an embodiment of the present invention. As Figure 7 shown, the device includes:

[0046] A first determination module 702, configured to determine a first version of a first compilation project file of a target client, and determine a second version of a second compilation project file on which the first compilation project file depends, where the first version is the current version of the first compilation project file, and the second version is the current version of the second compilation project file;

[0047] A second determination module 704, configured to determine a local version of the first compilation project file based on the first version and the second version;

[0048] A third determination module 706, configured to determine a server version of the first compilation project file stored in a target server, where the target server is connected to the target client;

[0049] An acquisition module 708, configured to, when the local version is inconsistent with the server version, acquire a server-side version file corresponding to the first compilation project file from the target server;

[0050] An update module 710, configured to update the first compilation project file based on the server-side version file.

[0051] In an exemplary embodiment, the first determination module 702 may determine the first version of the first compilation project file of the target client in the following manner: determine the first version number of the first compilation project file of the target client, and determine the first version number as the first version; the first determination module 702 may determine the second version of the second compilation project file on which the first compilation project file depends in the following manner: determine the second version number of the second compilation project file, and determine the second version number as the second version.

[0052] In an exemplary embodiment, the second determination module 704 may determine the local version of the first compilation project file based on the first version and the second version in the following manner: compare the first version and the second version to obtain a comparison result; determine the local version based on the comparison result.

[0053] In an exemplary embodiment, the second determination module 704 may determine the local version based on the comparison result in the following manner: when the comparison result indicates that the first version is greater than or equal to the second version, determine the first version as the local version; when the comparison result indicates that the first version is less than the second version, determine the second version as the local version.

[0054] In an exemplary embodiment, the device may also be used to determine the first compilation data and the first version number corresponding to the first compilation project file, and determine the second compilation data and the second version number corresponding to the second compilation project file before determining the first version of the first compilation project file of the target client and determining the second version of the second compilation project file on which the first compilation project file depends; package the first compilation data and the first version number into a first data packet, and package the second compilation data and the second version number into a second data packet; determine the first data packet as the first compilation file, and determine the second data packet as the second compilation file.

[0055] In an exemplary embodiment, the first compilation project file includes one of the following: a dynamic library file, an executable file, the second compilation project file includes one of the following: a dynamic library file, an executable file, and the first compilation project file and the second compilation project file are of the same type.

[0056] In an exemplary embodiment, the third determination module 706 may determine the server version of the first compiled project file stored in the target server in the following manner: sending version request information to the target server; receiving a version file sent by the target server based on the version request information; and determining the server version based on the version file.

[0057] It should be noted that the above-mentioned modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: all the above-mentioned modules are located in the same processor; or, the above-mentioned modules are respectively located in different processors in any combination form.

[0058] An embodiment of the present invention also provides a computer-readable storage medium, in which a computer program is stored. Wherein, when the computer program is executed by a processor, the steps of the method described in any one of the above are implemented.

[0059] In an exemplary embodiment, the above-mentioned computer-readable storage medium may include, but is not limited to: USB flash drives, read-only memories (ROM for short), random access memories (RAM for short), mobile hard disks, magnetic disks, or optical disks and other various media that can store computer programs.

[0060] An embodiment of the present invention also provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0061] In an exemplary embodiment, the above-mentioned electronic device may further include a transmission device and an input / output device. Wherein, the transmission device is connected to the above-mentioned processor, and the input / output device is connected to the above-mentioned processor.

[0062] The specific examples in this embodiment may refer to the examples described in the above embodiments and exemplary embodiments, and will not be repeated here.

[0063] Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present invention can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. They can be implemented by program codes executable by the computing device. Thus, they can be stored in a storage device and executed by the computing device. And in some cases, the steps shown or described can be executed in a sequence different from that here, or they can be separately fabricated into individual integrated circuit modules, or multiple modules or steps among them can be fabricated into a single integrated circuit module for implementation. In this way, the present invention is not limited to any specific combination of hardware and software.

[0064] The above are only the preferred embodiments of the present invention and are not used to limit the present invention. For those skilled in the art, the present invention can have various changes and modifications. Any modifications, equivalent replacements, improvements, etc. made within the principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A method for updating a compiled project file, characterized in that, it includes: Determine the first version of the first compiled project file of the target client, and determine the second version of the second compiled project file on which the first compiled project file depends, where the first version is the current version of the first compiled project file, and the second version is the current version of the second compiled project file; Determine the local version of the first compiled project file based on the first version and the second version; Determine the server version of the first compiled project file stored in the target server, where the target server is connected to the target client; In the case where the local version is inconsistent with the server version, obtain the server-side version file corresponding to the first compiled project file from the target server; Update the first compiled project file based on the server-side version file; Before determining the first version of the first compiled project file of the target client and determining the second version of the second compiled project file on which the first compiled project file depends, the method further includes: determining the first compiled data and the first version number corresponding to the first compiled project file, and determining the second compiled data and the second version number corresponding to the second compiled project file; packing the first compiled data and the first version number into a first data packet, and packing the second compiled data and the second version number into a second data packet; determining the first data packet as the first compiled file, and determining the second data packet as the second compiled file; Determining the server version of the first compiled project file stored in the target server includes: sending version request information to the target server; receiving the version file sent by the target server based on the version request information; determining the server version based on the version file.

2. The method according to claim 1, characterized in that, Determining the first version of the first compiled project file of the target client includes: determining the first version number of the first compiled project file of the target client, and determining the first version number as the first version; Determining the second version of the second compiled project file on which the first compiled project file depends includes: determining the second version number of the second compiled project file, and determining the second version number as the second version.

3. The method according to claim 1, characterized in that, Determining the local version of the first compiled project file based on the first version and the second version includes: Comparing the first version and the second version to obtain a comparison result; Determining the local version based on the comparison result.

4. The method according to claim 3, characterized in that, Determining the local version based on the comparison result includes: In the case where the comparison result indicates that the first version is greater than or equal to the second version, determining the first version as the local version; In the case where the comparison result indicates that the first version is less than the second version, determining the second version as the local version.

5. The method according to claim 1, wherein, the first compilation project file includes one of the following: a dynamic library file, an executable file, the second compilation project file includes one of the following: a dynamic library file, an executable file, and the first compilation project file and the second compilation project file are of the same type.

6. An updating device for a compilation project file, wherein, it includes: a first determination module, configured to determine a first version of a first compilation project file of a target client, and determine a second version of a second compilation project file on which the first compilation project file depends, wherein, the first version is the current version of the first compilation project file, and the second version is the current version of the second compilation project file; a second determination module, configured to determine a local version of the first compilation project file based on the first version and the second version; a third determination module, configured to determine a server version of the first compilation project file stored in a target server, wherein, the target server is connected to the target client; an acquisition module, configured to, when the local version is inconsistent with the server version, acquire a server-side version file corresponding to the first compilation project file from the target server; an updating module, configured to update the first compilation project file based on the server-side version file; before the device determines a first version of a first compilation project file of a target client, and determines a second version of a second compilation project file on which the first compilation project file depends: determine first compilation data and a first version number corresponding to the first compilation project file, and determine second compilation data and a second version number corresponding to the second compilation project file; pack the first compilation data and the first version number into a first data packet, and pack the second compilation data and the second version number into a second data packet; determine the first data packet as the first compilation file, and determine the second data packet as the second compilation file; the third determination module determines the server version of the first compilation project file stored in the target server in the following manner: send version request information to the target server; receive a version file sent by the target server based on the version request information; determine the server version based on the version file.

7. A computer-readable storage medium, wherein, a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

8. An electronic device, including a memory and a processor, wherein, a computer program is stored in the memory, and the processor is configured to run the computer program to execute the method according to any one of claims 1 to 5.

Images