CN109739548B - Program packaging method, program packaging device, and computer-readable storage medium - Google Patents

Abstract

A program packaging method, a program packaging device, and a computer-readable storage medium, wherein the program packaging method includes: acquiring subpackage configuration information, wherein the configuration information includes a designation of a module included in this package; according to the subpackage The configuration information of the package generates the module calling method of the package, wherein the module calling method is used to specify the loading mode of each module called by the package; the packaging operation is performed based on the configuration information of the subpackage and the module calling method , to obtain a subcontracting file, wherein the subcontracting file contains the module calling method of this package. The solution provided by this application enables the subcontracted documents to be run on various platforms.

Description

Program packaging method, program packaging device, and computer-readable storage medium

technical field

The present application relates to the field of communication technologies, and in particular, to a program packaging method, a program packaging device, and a computer-readable storage medium.

Background technique

With the development of science and technology, various intelligent terminals have become an indispensable part of people's life and work. Smart terminals can realize various functions by carrying various application programs to meet the different needs of users.

"Quick App" is a new type of application ecosystem jointly launched by several mobile phone manufacturers based on the hardware platform. Users do not need to download and install, just click and use, and can enjoy the performance experience of native applications. "Quick application" uses front-end technology stack development and native rendering, which combines the dual advantages of H5 pages and native applications.

At present, the typical case of "quick application" is the WeChat applet. In some cases, the developer needs to divide the applet into different sub-packages, and package them into different sub-packages during construction. load. In the prior art, the subpackage packaged by the packaging tool needs to rely on the engine of WeChat to be started, and cannot be run under other platforms (such as browsers).

SUMMARY OF THE INVENTION

The present application provides a program packaging method, a program packaging device, and a computer-readable storage medium, so that the subpackaged files can be run on various platforms.

A first aspect of the present application provides a program packaging method, including:

Obtain the configuration information of subcontracting, wherein, the configuration information includes the designation of the module included in this package and the designation of the module called by this package;

The module calling method of this package is generated according to the configuration information of the subpackage, wherein the module calling method is used to specify the loading mode of each module called by this package;

The packaging operation is performed based on the configuration information of the subpackage and the module invocation method to obtain a subpackage file, wherein the subpackage file includes the module invocation method of the package.

A second aspect of the present application provides a program packaging device, comprising:

an acquisition unit for acquiring the configuration information of the subcontracting, wherein the configuration information includes a specification of a module included in this package and a specification of a module called by this package;

a generating unit, configured to generate a module calling method of the package according to the configuration information of the subpackage, wherein the module calling method is used to specify the loading mode of each module called by the package;

A packaging unit, configured to perform a packaging operation based on the configuration information of the subpackage and the module invocation method to obtain a subpackage file, wherein the subpackage file includes the module invocation method of the package.

A third aspect of the present application provides another program packaging device, the program packaging device comprising:

A memory, a processor, and a computer program stored in the memory and running on the processor, when the processor executes the computer program, implements the steps in the program packaging method provided in the first aspect of the embodiment of the present application.

A fourth aspect of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, each step of the program packaging method provided in the first aspect of the embodiment of the present application is implemented.

As can be seen from the above, the solution of the present application generates the module calling method of the package according to the configuration information of the package, and performs the packaging operation based on the configuration information of the package and the module calling method, so that the package file contains the module calling method of the package. Since the module calling method specifies the loading method of each module called by this package, the subpackage file generated by the case division packaging of the present application can be run according to the module calling method in the subpackage file under various platforms, while There is no need to rely on the loading method specified by the engine in a specific platform to run.

Description of drawings

1 is a schematic flowchart of an embodiment of a program packaging method provided by the present application;

2 is a schematic diagram of the overall package packaging process provided by the application;

3 is a schematic structural diagram of an embodiment of a program packaging device provided by the present application;

FIG. 4 is a schematic structural diagram of another embodiment of the program packaging apparatus provided by the present application.

Detailed ways

In order to make the purpose, features and advantages of the invention of the present application more obvious and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. The embodiments described above are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of this application.

An embodiment of the present application provides a program packaging method. The program packaging method is applied to a program packaging device. The program packaging device may be integrated in a terminal such as a smart phone, a tablet computer, or a personal computer, or may also be an independent electronic device. Here Not limited.

Referring to FIG. 1, the program packaging method in this embodiment mainly includes the following steps:

Step 101, obtain the configuration information of subcontracting;

In the embodiment of the present application, the above configuration information includes the specification of the modules contained in this package (for example, a .js file, a .js file may be called a module). Files such as resources and codes for packaging operations, and sub-packages refer to resources and code blocks that are packaged together according to configuration information. From the above definition, it can be known that the relationship between this package and subcontracting is who is currently operating.

Optionally, the modules included in this package can be specified by specifying a directory, and then all modules in the specified directory are modules included in this package. For example, for the subpackage stage1 with the directory "stage1" as the subpackage name, you can specify all modules under the directory stage1 as the modules included in the subpackage stage1 by the following code:

Of course, it can also be specified directly by specifying a module. Taking the above example as an example, the js1 module can be specified by the following code:

Further, the above configuration information may also include the following items: a subpackage root directory, a subpackage alias, a page path of the subpackage relative to the subpackage root directory, and a flag indicating whether the subpackage is an independent subpackage.

In practical applications, the configuration information of each sub-package can be input by the developer through a specific interface in advance, and other data except the sub-package can be regarded as the data of the main package, and these data are packaged into the main package to generate the main package file. . Usually, the main package file includes: the default startup page and the common resources called by the subpackage.

Step 102, generating the module calling method of this package according to the configuration information of the above-mentioned subcontracting;

The above module calling method is used to specify the loading method of each module called by this package.

The above module calling method can solve the following two problems:

1. Implement the loading of modules (such as asynchronous loading) to avoid no response when loading modules;

2. Manage dependencies between modules to facilitate code writing and maintenance.

Because the above configuration information contains the specification of the modules included in this package. As an embodiment of the present application, the module calling method for generating the package according to the configuration information of the subpackage may be: acquiring the modules included in the package and the dependencies between the modules according to the configuration information of the subpackage, and passing the modules between the modules. The dependencies of the module know the loading order of each module, and generate the module call method of this package.

Optionally, the above-mentioned module calling method is a require method (also referred to as a require() function), and step 102 is specifically represented as: generating a require method of this package according to the above-mentioned configuration information of the sub-package. Specifically, the writing format of the require method can be as follows: require([module],callback), as can be seen from this format, the require method contains two parameters, the first parameter [module] is an array, and the members in it are to be loaded Module, the second parameter callback is the callback function after the loading is successful.

Of course, the require method is only an implementation manner of the above-mentioned module invocation method. In other embodiments, the above-mentioned module invocation method may also be a define method or other methods, which is not limited here.

Step 103, carry out a packaging operation based on the configuration information of the above-mentioned subcontracting and the above-mentioned module calling method, and obtain a subcontracting file;

Among them, the above-mentioned subpackage file contains the module calling method of this package.

In step 103, the module called by this package is packaged based on the configuration information of the subpackage, and the module invocation method generated in step 102 is written in the packaging process to obtain the subpackage file.

Optionally, in order to reduce the size of the subcontracting file, for the modules called by the subcontracting file and the modules not included in the subcontracting file, these modules are referred to as outsourcing modules in the embodiments of the present application, and these modules may not be referred to as outsourcing modules. Packaged in the subpackage file (that is, excluding these modules), because usually the developer defines the path of the module as a relative path, that is, the path relative to the root directory of the subpackage, in order to enable the subpackage file to find the related files when calling the outsourced module. , in the embodiment of the present application, the relative path of the outsourced module called by this package and the absolute path of the outsourced module may be mapped, and the module mapping information obtained by the mapping may be written into this package. Specifically, the program packaging method in the embodiment of the present application further includes:

When the module called by the above-mentioned subcontracting includes an outsourced module, the above-mentioned subcontracted module mapping information is generated, wherein the above-mentioned module mapping information is used to map the relative path of the outsourced module called by this package and the absolute path of the above-mentioned outsourced module, wherein , the above-mentioned outsourced module refers to the module called in this package and not included in this package, the above-mentioned relative path refers to the path relative to the root directory of this package, and the absolute path of the outsourced module is a dictionary equivalent to the outsourced module. Step 103 may be represented as: based on the configuration information of the subpackage and the module calling method, a packaging operation is performed on the modules included in the subpackage and the module mapping information in the subpackage.

For the scenario where the module is a Js module, the packaging operation in step 103 can use Gulp to control the packaging process, including JS conversion, sourceMap generation, error handling, code compression and obfuscation, etc., and Browserify can be used to package the JS module.

Further, after each subcontracting file and the main package file are obtained, each obtained subcontracting file and the main package file can be packaged into a general package file. As shown in Figure 2, the sub-package files 1-N (in Figure 2 are shown as sub-package 1.rpk, sub-package 2.rpk...sub-package file N.rpk) and the main package file (in Figure 2) are obtained after packaging. 2), each sub-package file and the main package file can be packaged into a total package file (indicated by [project name].rpk in Figure 2), where "rpk" is the package file suffix.

It should be noted that the program packaging method in the embodiment of the present application is a solution for improving the packaging logic of modules. For other non-module resources (css, pictures, audio and video files, etc.) contained in the subpackaged file, you can refer to the existing Technology (such as copy operation) can be added to the subcontract file.

It should also be noted that the program packaging file in the embodiment of the present application is suitable for packaging each sub-package, and the packaging process of the main package may be implemented with reference to the prior art, which will not be repeated here.

As can be seen from the above, the solution of the present application generates the module calling method of the package according to the configuration information of the package, and performs the packaging operation based on the configuration information of the package and the module calling method, so that the package file contains the module calling method of the package. Since the module calling method specifies the loading method of each module called by this package, the sub-package file generated by the case-divided packaging of this application can be used on various platforms (such as the platform built in the V8 environment) according to the sub-package file. The modules in the call method run without relying on the loading method specified by the engine in the specific platform to run.

FIG. 3 provides a program packaging apparatus according to an embodiment of the present application. The program packaging device can be used to implement the program packaging method in the embodiment shown in FIG. 1 . As shown in Figure 3, the program packaging device mainly includes:

The obtaining unit 301 is used for obtaining the configuration information of subcontracting, wherein, the configuration information includes the designation of the modules included in this package;

A generating unit 302, configured to generate a module calling method of the package according to the configuration information of the subpackage, wherein the module calling method is used to specify the loading mode of each module called by the package;

The packaging unit 303 is configured to perform a packaging operation based on the configuration information of the subpackage and the module invocation method to obtain a subpackage file, wherein the subpackage file includes the module invocation method of the package.

Optionally, the above-mentioned program packaging device further includes:

The mapping unit is used to generate the module mapping information of the above-mentioned subcontracting when the module called by the above-mentioned subcontracting includes the outsourcing module, wherein, the above-mentioned module mapping information is used to the relative path of the outsourcing module called by this bag and the relative path of the outsourcing module. The absolute path is mapped, wherein the above-mentioned outsourced module refers to the module called in this package and not included in this package, and the above-mentioned relative path refers to the path relative to the root directory of this package;

The packaging unit 303 is specifically configured to: based on the configuration information of the subpackage and the module calling method, perform a packaging operation on the modules included in the subpackage and the module mapping information in the subpackage.

It should be noted that, in the above embodiment of the program packaging device illustrated in FIG. 3 , the division of each functional module is only an example, and in practical applications, it can be based on needs, such as the configuration requirements of corresponding hardware or the convenience of software implementation, and The above function allocation is completed by different function modules, that is, the internal structure of the program packaging device is divided into different function modules, so as to complete all or part of the functions described above. Moreover, in practical applications, the corresponding functional modules in this embodiment may be implemented by corresponding hardware, or may be implemented by corresponding hardware executing corresponding software. The above description principles can be applied to each of the embodiments provided in this specification, which will not be repeated below.

For the specific process of each functional module in the program packaging device provided in this embodiment implementing their respective functions, please refer to the specific content described in the foregoing method embodiment, which will not be repeated here.

As can be seen from the above, the program packaging device in the embodiment of the present application generates a module calling method of the package according to the configuration information of the package, and performs a packaging operation based on the configuration information of the package and the module calling method, so that the package file contains the package. The module calls the method. Since the module calling method specifies the loading method of each module called by this package, the subpackage file generated by the case division packaging of the present application can be run according to the module calling method in the subpackage file under various platforms, while There is no need to rely on the loading method specified by the engine in a specific platform to run.

FIG. 4 provides a program packaging apparatus according to an embodiment of the present application. The program packaging device can be used to implement the program packaging method in the embodiment shown in FIG. 1 . As shown in Figure 4, the program packaging device mainly includes:

A memory 401, a processor 402, and a computer program stored in the memory 401 and running on the processor 402, when the processor 402 executes the computer program, implements the program packaging method in the embodiment shown in FIG. 1 .

Further, the program packaging device also includes:

At least one input device 403 and at least one output device 404 .

The above-mentioned memory 401 , processor 402 , input device 403 and output device 404 are connected through a bus 405 .

The input device 403 may specifically be a camera, a touch panel, a physical button, a mouse, or the like. The output device 404 may specifically be a display screen.

The memory 401 may be a high-speed random access memory (RAM, Random Access Memory) memory, or may be a non-volatile memory (non-volatile memory), such as a disk memory. The memory 401 is used to store a set of executable program codes, and the processor 402 is coupled to the memory 401 .

As can be seen from the above, the program packaging device in the embodiment of the present application generates a module calling method of the package according to the configuration information of the package, and performs a packaging operation based on the configuration information of the package and the module calling method, so that the package file contains the package. The module calls the method. Since the module calling method specifies the loading method of each module called by this package, the subpackage file generated by the case division packaging of the present application can be run according to the module calling method in the subpackage file under various platforms, while There is no need to rely on the loading method specified by the engine in a specific platform to run.

Further, an embodiment of the present application further provides a computer-readable storage medium, and the computer-readable storage medium may be set in the program packaging apparatus in the above-mentioned embodiments, and the computer-readable storage medium may be the aforementioned FIG. 3 memory in the embodiment shown. A computer program is stored on the computer-readable storage medium, and when the program is executed by the processor, the program packaging method in the embodiment shown in FIG. 1 is implemented. Further, the computer-storable medium may also be a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a RAM, a magnetic disk, or an optical disk and other media that can store program codes.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the above modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components may be combined or Integration into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or modules, and may be in electrical, mechanical or other forms.

The modules described above as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, may be located in one place, or may be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically alone, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.

If the above-mentioned integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a readable storage The medium includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the above-mentioned methods of the various embodiments of the present application. The aforementioned readable storage medium includes: U disk, removable hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

It should be noted that, for the convenience of description, the foregoing method embodiments are described as a series of action combinations, but those skilled in the art should know that the present application is not limited by the described action sequence. Because in accordance with the present application, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily all necessary for the present application.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

The above is a description of the program packaging method, the program packaging device and the computer-readable storage medium provided by the present application. For those skilled in the art, according to the ideas of the embodiments of the present application, there will be changes in the specific implementation and application scope. In conclusion, the content of this specification should not be construed as a limitation on this application.

Claims (9)

1. a program packaging method, is characterized in that, comprises: Obtain the configuration information of the subcontracting, wherein the configuration information includes the designation of the modules included in this package; Obtain the modules contained in this package and the dependencies between the modules according to the configuration information of the subpackage; Knowing the loading order of the modules through the dependencies, and generating the module calling method of the package, wherein the module calling method is used to specify the loading mode of each module called by the package; The packaging operation is performed based on the configuration information of the subpackage and the module invocation method to obtain a subpackage file, wherein the subpackage file includes the module invocation method of the package. 2. The program packaging method according to claim 1, wherein the program packaging method further comprises: When the module called by the subcontract includes an outsourced module, generate the subcontracted module mapping information, wherein the module mapping information is used for the relative path of the outsourced module called by this package and the absolute path of the outsourced module Mapping is performed, wherein the outsourced module refers to a module called in this package and not included in this package, and the relative path refers to a path relative to the root directory of this package; The packaging operation based on the subpackaged configuration information and the module calling method is specifically: Based on the configuration information of the subpackage and the module calling method, a packaging operation is performed on the modules included in the subpackage and the module mapping information in the subpackage. 3. The program packaging method according to claim 1, wherein the program packaging method further comprises: According to the configuration information of each sub-package file, the sub-package files of the same sub-package folder are packaged into one sub-package, and the files other than the sub-package files are packaged into the main package as the main package file; According to the configuration information of the main package and sub-packages, the main package and several sub-packages are aggregated into a general package file, wherein the main package file includes: a default startup page and public resources called by the sub-package files. 4. program packaging method according to claim 1, is characterized in that, described module calling method is specifically require method; The module invoking method for generating this package according to the subpackage configuration information is specifically: a require method for generating this package according to the subpackage configuration information. 5. The program packaging method according to any one of claims 1 to 4, wherein the designation of the modules included in this package comprises: If the modules included in the package are specified by specifying a directory, then all modules in the specified directory are modules included in the package, and the configuration information also includes the subpackage root directory, subpackage alias, subpackage Any one or more of the page path relative to the subpackage root directory and the flags indicating whether the subpackage is an independent subpackage. 6. the program packaging method according to any one of claims 1 to 4, is characterized in that, described based on the configuration information of described subcontracting and described module calling method to carry out packaging operation, obtain subcontracting file, comprising: According to the modules contained in this package and the dependencies between the modules, use any one or several methods of JS conversion, sourceMap generation, error handling, code compression and obfuscation to generate the modules contained in this package. Subpackage file. 7. a program packaging device, is characterized in that, comprises: an obtaining unit, used for obtaining the configuration information of the subcontracting, wherein the configuration information includes the designation of the modules included in the package; A generating unit, configured to obtain the modules included in the package and the dependencies between the modules according to the configuration information of the subpackage; learn the loading order of the modules through the dependencies, and generate the module call of the package method, wherein the module calling method is used to specify the loading mode of each module called by this package; A packaging unit, configured to perform a packaging operation based on the configuration information of the subpackage and the module invocation method to obtain a subpackage file, wherein the subpackage file includes the module invocation method of the package. 8. A program packaging device, comprising: a memory, a processor and a computer program that is stored on the memory and can be run on the processor, wherein when the processor executes the computer program, it realizes A step in the method of any one of claims 1 to 6. 9 . A computer-readable storage medium on which a computer program is stored, wherein, when the computer program is executed by a processor, the steps in the method of any one of claims 1 to 6 are implemented. 10 .

Images