Nothing Special   »   [go: up one dir, main page]

CN111124420B - Compiling method, compiling device, electronic equipment and readable storage medium - Google Patents

Compiling method, compiling device, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN111124420B
CN111124420B CN201911319075.5A CN201911319075A CN111124420B CN 111124420 B CN111124420 B CN 111124420B CN 201911319075 A CN201911319075 A CN 201911319075A CN 111124420 B CN111124420 B CN 111124420B
Authority
CN
China
Prior art keywords
plug
program
compiling
resources
code
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
Application number
CN201911319075.5A
Other languages
Chinese (zh)
Other versions
CN111124420A (en
Inventor
高飞
张岱帅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Baidu Netcom Science and Technology Co Ltd
Original Assignee
Beijing Baidu Netcom Science and Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Baidu Netcom Science and Technology Co Ltd filed Critical Beijing Baidu Netcom Science and Technology Co Ltd
Priority to CN201911319075.5A priority Critical patent/CN111124420B/en
Publication of CN111124420A publication Critical patent/CN111124420A/en
Application granted granted Critical
Publication of CN111124420B publication Critical patent/CN111124420B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/40Transformation of program code
    • G06F8/41Compilation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The application discloses a compiling method, a compiling device, electronic equipment and a readable storage medium, and relates to the technical field of compiling in the field of computers. The specific implementation scheme is as follows: splitting and compiling the object to be compiled in the first compiling engineering according to the configuration information of the non-plug-in program and at least one plug-in program to obtain a resource compiling result of the non-plug-in program, a resource compiling result of each plug-in program, a code compiling result of the non-plug-in program and a code compiling result of each plug-in program, and outputting executable files of the non-plug-in program and the plug-in program respectively. The method has the advantages that the complexity of plug-in compiling of the application program with plug-in requirement is low, and the compiling error can be avoided.

Description

Compiling method, compiling device, electronic equipment and readable storage medium
Technical Field
Embodiments of the present disclosure relate to computer technology, and in particular, to a compiling method, device, electronic apparatus, and readable storage medium.
Background
The application may need to be compiled multiple times during development prior to release. At compile time, source code and related resources of the application program are input into a compiling tool, compiled by the compiling tool, and an application package of the application program is output. Taking android operating systems as an example, gradle is a compiling tool with wider application. For applications that need to run in the android operating system, the gradle can be used for compiling.
In the prior art, when the gradle compiles the application program, the codes and resources of the application program to be compiled are taken as a main program to be compiled uniformly, so that a uniform compiling result is obtained.
However, for an application program with a plug-in requirement, the existing compiling method may have the problems of high plug-in splitting complexity, difficulty in obtaining an expected plug-in compiling result and the like.
Disclosure of Invention
The embodiment of the application provides a compiling method, a compiling device, electronic equipment and a readable storage medium, which are used for solving the problems that in the prior art, plug-in splitting complexity is high and expected plug-in compiling results are difficult to obtain.
In a first aspect, an embodiment of the present application provides a compiling method, including:
acquiring an object to be compiled in a first compiling project, wherein the object to be compiled comprises codes and resources of an application program to be compiled, and the codes and the resources are respectively attributed to a non-plug-in program and at least one plug-in program of the application program;
processing the object to be compiled in a first compiling project according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain a resource compiling result of the non-plug-in program, a resource compiling result of each plug-in program, a code compiling result of the non-plug-in program and a code compiling result of each plug-in program;
And outputting the executable file of the non-plug-in program and the executable file of the plug-in program respectively.
As a possible implementation manner, the outputting the executable file of the non-plug-in program and the executable file of the plug-in program respectively includes:
outputting an executable file of the non-plug-in program through the first compiling engineering according to the resource compiling result of the non-plug-in program and the code compiling result of the non-plug-in program;
and outputting the executable file of the plug-in through a second compiling project according to the resource compiling result of the plug-in and the code compiling result of the plug-in.
As a possible implementation manner, the processing, in a first compiling engineering, the object to be compiled according to the configuration information of the non-plug-in program and the at least one plug-in program, to obtain a resource compiling result of the non-plug-in program, a resource compiling result of each plug-in program, a code compiling result of the non-plug-in program, and a code compiling result of each plug-in program, includes:
according to the configuration information of the non-plug-in program and the at least one plug-in program, carrying out resource splitting on the object to be compiled to obtain the resources of the non-plug-in program and the resources of each plug-in program;
Compiling the resources of the non-plug-in program and the resources of each plug-in program to obtain a compiling result of the resources of the non-plug-in program and a compiling result of the resources of each plug-in program;
splitting the compiled code compiling result according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program.
As a possible implementation manner, the compiling the non-plug-in program resource and the plug-in program resource to obtain the non-plug-in program resource compiling result and the plug-in program resource compiling result includes:
compiling and allocating identifiers for the resources of the non-plug-in program and the resources of each plug-in program to obtain a resource compiling result of the non-plug-in program and a resource compiling result of each plug-in program, wherein the identifiers of the resource compiling result of the non-plug-in program and the identifiers of the resource compiling result of each plug-in program are different from each other.
As a possible implementation manner, after splitting the compiled code compiling result to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program, the method further includes:
And simultaneously carrying out confusion processing on the code compiling result of the non-plug-in program and the code compiling result of each plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program after the confusion processing.
As one possible implementation manner, the outputting, by a second compiling engineering, the executable file of the plug-in program according to the resource compiling result of the plug-in program and the code compiling result of the plug-in program includes:
inputting the resource compiling result of the plug-in program and the code compiling result of the plug-in program into the second compiling project, so as to replace the resource compiling result of the plug-in program through the second compiling project, and outputting the executable file of the plug-in program according to the resource compiling result of the plug-in program and the code compiling result of the plug-in program after the replacing process.
As a possible implementation manner, the splitting the compiled code compiling result according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program includes:
Splitting the compiled code compiling result according to the target configuration file to obtain a code compiling result of the non-plug-in program and a code compiling result of each plug-in program;
the target configuration file is used for identifying the configuration information.
As a possible implementation manner, the splitting the resources of the object to be compiled according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain the resources of the non-plug-in program and the resources of each plug-in program includes:
according to the target configuration file, splitting the resources of the object to be compiled to obtain the resources of the non-plug-in program and the resources of each plug-in program;
the target configuration file is used for identifying the configuration information.
In a second aspect, an embodiment of the present application provides a compiling apparatus, including:
the system comprises an acquisition module, a compiling module and a compiling module, wherein the acquisition module is used for acquiring an object to be compiled in a first compiling project, the object to be compiled comprises codes and resources of an application program to be compiled, and the codes and the resources are respectively attributed to a non-plug-in program and at least one plug-in program of the application program;
The processing module is used for processing the object to be compiled in a first compiling project according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain a resource compiling result of the non-plug-in program, a resource compiling result of each plug-in program, a code compiling result of the non-plug-in program and a code compiling result of each plug-in program;
and the output module is used for respectively outputting the executable file of the non-plug-in program and the executable file of the plug-in program.
As a possible implementation manner, the output module is specifically configured to:
the executable file of the non-plug-in program is output through the first compiling engineering according to the resource compiling result of the non-plug-in program and the code compiling result of the non-plug-in program; the method comprises the steps of,
and outputting the executable file of the plug-in through a second compiling project according to the resource compiling result of the plug-in and the code compiling result of the plug-in.
As a possible implementation manner, the processing module is specifically configured to:
according to the configuration information of the non-plug-in program and the at least one plug-in program, carrying out resource splitting on the object to be compiled to obtain the resources of the non-plug-in program and the resources of each plug-in program; the method comprises the steps of,
Compiling the resources of the non-plug-in program and the resources of each plug-in program to obtain a compiling result of the resources of the non-plug-in program and a compiling result of the resources of each plug-in program; the method comprises the steps of,
splitting the compiled code compiling result according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program.
As a possible implementation manner, the processing module is specifically configured to:
compiling and allocating identifiers for the resources of the non-plug-in program and the resources of each plug-in program to obtain a resource compiling result of the non-plug-in program and a resource compiling result of each plug-in program, wherein the identifiers of the resource compiling result of the non-plug-in program and the identifiers of the resource compiling result of each plug-in program are different from each other.
As a possible implementation manner, the processing module is further configured to:
and simultaneously carrying out confusion processing on the code compiling result of the non-plug-in program and the code compiling result of each plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program after the confusion processing.
As a possible implementation manner, the output module is specifically configured to:
inputting the resource compiling result of the plug-in program and the code compiling result of the plug-in program into the second compiling project, so as to replace the resource compiling result of the plug-in program through the second compiling project, and outputting the executable file of the plug-in program according to the resource compiling result of the plug-in program and the code compiling result of the plug-in program after the replacing process.
As a possible implementation manner, the processing module is specifically configured to:
splitting the compiled code compiling result according to the target configuration file to obtain a code compiling result of the non-plug-in program and a code compiling result of each plug-in program;
the target configuration file is used for identifying the configuration information.
As a possible implementation manner, the processing module is specifically configured to:
according to the target configuration file, splitting the resources of the object to be compiled to obtain the resources of the non-plug-in program and the resources of each plug-in program;
the target configuration file is used for identifying the configuration information.
In a third aspect, an embodiment of the present application provides an electronic device, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first aspect described above.
In a fourth aspect, embodiments of the present application provide a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method of the first aspect.
One embodiment of the above application has the following advantages or benefits:
the plug-in codes and the non-plug-in codes of the application program are integrally compiled based on one-time unified construction in the first compiling engineering, so that errors that dependency information cannot be found can be avoided, resources and codes of all plug-ins are split in the integral compiling process of the first compiling engineering based on configuration information of the plug-in programs and the non-plug-in programs, and executable files of the non-plug-in programs and the plug-in programs are respectively output. In the process, the source program of the application program is not required to be modified, the corresponding module of the plug-in program is not required to be split by itself, and the executable files of the plug-in program and the non-plug-in program can be obtained only based on the configuration information, so that the complexity of compiling plug-in of the application program with plug-in requirements is low and the compiling error can be avoided.
Other effects of the above alternative will be described below in connection with specific embodiments.
Drawings
The drawings are for better understanding of the present solution and do not constitute a limitation of the present application. Wherein:
FIG. 1 is an example of dependencies of a source program of an application;
fig. 2 is a schematic flow chart of a compiling method according to an embodiment of the present application;
FIG. 3 is a flowchart of a compiling method according to an embodiment of the present disclosure;
FIG. 4 is a schematic illustration of the compilation process of gradle;
FIG. 5 is a block diagram of a compiling apparatus according to an embodiment of the present application;
fig. 6 is a block diagram of an electronic device of a compiling method according to an embodiment of the application.
Detailed Description
Exemplary embodiments of the present application are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In the prior art, when the gradle compiles the application program, the codes and resources of the application program to be compiled are taken as a main program to be compiled uniformly, so that a uniform compiling result is obtained. For some applications with complex functions, the development may be performed by multiple development teams, each team is responsible for developing modules of a part of the plugins, there may be many places between the modules that need to be associated with each other and dependent on each other, and at the same time, each team needs to compile the modules that each team is responsible for to obtain various plugins. Fig. 1 is an example of a dependency relationship of a source program of an application program, and as shown in fig. 1, the application program includes a base module and n service modules, where each service module depends on the base module. Meanwhile, a dependency relationship may exist between each service module. If the gradle compiling method is used, for each plugin, the corresponding module and the module with the dependency relationship are required to be split into plugin projects for compiling, and due to the complex dependency relationship among the modules, the splitting complexity is very high, and the problem that errors are reported in the compiling process because the dependent module cannot be found can occur, so that the expected plugin compiling result is difficult to obtain is caused.
Based on the above problems, the embodiment of the present application proposes a compiling method, which performs overall compiling on an application program based on one-time unified construction, and compiles plug-in codes and non-plug-in codes integrally, so that errors that dependency information cannot be found can be avoided, and further, resources and codes of each plug-in are split in the overall compiling process, so that different plug-ins are obtained, and therefore, the complexity of plug-in compiling of the application program with plug-in requirements is low and the compiling error is avoided.
It should be understood that, in the embodiments of the present application, an application to be compiled refers to a source program of an application that is not compiled.
Fig. 2 is a schematic flow chart of a compiling method according to an embodiment of the present application, where an execution body of the method is an electronic device capable of installing and running a compiling tool. As shown in fig. 2, the method includes:
s201, acquiring an object to be compiled in a first compiling project, wherein the object to be compiled comprises codes and resources of an application program to be compiled, and the codes and the resources are respectively attributed to non-plug-ins and at least one plug-in of the application program.
It should be noted that, the method of the embodiment of the present application may be applied to an existing gradle compiling tool, and the gradle is modified, where the processing procedure of the embodiment of the present application is added, and the following embodiments of the present application are also described by taking the modification on the gradle as an example. However, embodiments of the present application are not limited in this regard and may be applied to other compilation tools as well.
When the gradle is needed to be used for compiling, a compiling project needs to be established first, and a source program to be compiled is input into the compiling project and compiling is started. In this embodiment of the present application, the first compiling engineering may be referred to as a main engineering of a compiling application, where an input of the main engineering is a complete source program of the application to be compiled, and the complete source program includes resources and codes. The non-plug-ins and the plug-ins of the application correspond to a portion of the resources and code, respectively, therein.
Alternatively, the non-plug-in of the application may refer to the main program or the base program of the application.
It should be appreciated that, based on the foregoing associations and dependencies, a resource, function code, etc. in a source program may be concurrently attributed to multiple programs. For example, a function, i.e., code that is not a plug-in, is also plug-in code.
Alternatively, the resources mentioned above may refer to resources that need to be loaded when the application program runs, for example, pictures, interface elements, etc. that need to be loaded.
In the implementation process, the first compiling engineering is created in the gradle, and the complete source program of the application program to be compiled is input into the first compiling engineering, so that the object to be compiled can be obtained.
S202, processing the object to be compiled in a first compiling project according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain a resource compiling result of the non-plug-in program, a resource compiling result of each plug-in program, a code compiling result of the non-plug-in program and a code compiling result of each plug-in program.
Wherein, the above-mentioned processing includes: splitting and compiling. The configuration information is used for identifying the corresponding relation between the non-plug-in program and the code and the resource, and the corresponding relation between the plug-in program and the code and the resource.
Taking the above-mentioned dependency relationship of the source program shown in fig. 1 as an example, the source program of the application program includes a base module and a plurality of service modules, and each module includes resources and codes. In one example, the configuration information described above may be marked as: basic module+business module 1=non-plug-in, basic module+module 2+module 3=plug-in 1. From this example, it is known that plug-in 1 corresponds to basic module, business module 2 and business module 3, i.e., the codes and resources in these modules are assigned to plug-in 1, and thus, at compile time, the results of compiling the codes and resources of these modules are the compiling results of plug-in 1. Further, as is clear from the above examples, the basic module belongs to both the plug-in 1 and the non-plug-in, and therefore, the basic module needs to be used for compiling both the plug-in 1 and the non-plug-in.
The configuration information may be pre-recorded by a developer of the application program before compiling and stored in a preset directory. When the first compiling engineering is executed to the step, the configuration information is read from the preset catalog, and the object to be compiled is split and compiled based on the configuration information. The specific procedure will be described in detail in the following examples.
S203, outputting the executable file of the non-plug-in program and the executable file of the plug-in program respectively.
After the above-described resource compilation result of the non-plug-in, resource compilation result of each plug-in, code compilation result of the non-plug-in, and code compilation result of each plug-in are obtained, the executable file of the non-plug-in and the executable file of each plug-in may be output, respectively, based on these information.
The executable files can be executed on the terminal equipment to realize the functions of the respective programs.
In this embodiment, the plug-in code and the non-plug-in code of the application program are integrally compiled based on one unified construction in the first compiling engineering, so that an error that dependency information cannot be found can be avoided, resources and codes of each plug-in program are split in the integral compiling process of the first compiling engineering based on configuration information of the plug-in program and the non-plug-in program, and executable files of the non-plug-in program and the plug-in program are respectively output. In the process, the source program of the application program is not required to be modified, the corresponding module of the plug-in program is not required to be split by itself, and the executable files of the plug-in program and the non-plug-in program can be obtained only based on the configuration information, so that the complexity of compiling plug-in of the application program with plug-in requirements is low and the compiling error can be avoided.
As an alternative embodiment, when the executable file of the non-plug-in program and the executable file of the plug-in program are output in the step S203, the executable file of the non-plug-in program may be output through the first compiling process according to the resource compiling result of the non-plug-in program and the code compiling result of the non-plug-in program, and the executable file of the plug-in program may be output through the second compiling process according to the resource compiling result of the plug-in program and the code compiling of the plug-in program.
It should be noted that the execution sequence of the two executable files is not different.
After the processing in step S202, the code and the compiling result of the resources and the non-plug-in program are split, and on the basis of this, only the compiling result and the code compiling result of the resources and the non-plug-in program are subjected to subsequent compiling processing by the first compiling engineering, for example, the dex file obtained by the foregoing compiling is compiled into an apk file, so as to obtain the compiling result of the non-plug-in program.
Alternatively, the second compiling process may be a process different from the first compiling process. Each plug-in may correspond to one second compilation project, and thus, if there are a plurality of plug-ins, there may be a plurality of second compilation projects.
Optionally, after the code compiling result and the resource compiling result of the plug-in program are obtained in the step S202, the code compiling result and the resource compiling result of the plug-in program may be respectively saved to the directory corresponding to the plug-in program. Further, in this step, the second compiling project corresponding to the plug-in program may be automatically created, the code compiling result and the resource compiling result thereof may be read from the directory corresponding to the plug-in program, and the two results may be used as the input of the second compiling project and the subsequent compiling process may be performed, thereby obtaining the executable file of the plug-in program.
As described in the foregoing step S202, the processing performed on the object to be compiled includes splitting and compiling. An alternative procedure to this process is described below.
Fig. 3 is a flowchart of a compiling method according to an embodiment of the present application, and it should be understood that steps S301 to S303 described below may all be performed in the first compiling engineering. As shown in fig. 3, an alternative processing manner of the step S202 includes:
s301, splitting the resources of the object to be compiled according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain the resources of the non-plug-in program and the resources of each plug-in program.
The configuration information identifies the correspondence between the non-plug-in and the code and the resource, and the correspondence between the plug-in and the code and the resource, so that it is possible to know which code and resource belong to which plug-in or non-plug-in through the configuration information. Further, when resource splitting is performed based on the configuration information, specifically, resources belonging to one plug-in program may be packaged as one unit, and resources belonging to non-plug-in programs may be packaged as one unit.
As an alternative way, when compiling the resources of the non-plug-in program and the resources of each plug-in program, compiling and allocating the identifiers of the resources of the non-plug-in program and the resources of each plug-in program in the first compiling engineering to obtain the compiling result of the resources of the non-plug-in program and the compiling result of the resources of each plug-in program, wherein the identifiers of the compiling result of the resources of the non-plug-in program and the identifiers of the compiling result of the resources of each plug-in program are different from each other.
After the above-mentioned process of allocating the identifiers, each resource compiling result has a unique identifier to distinguish from other resource compiling results, so that it can be ensured that the identifiers of the resource compiling results do not have any conflict, and further, errors in the subsequent compiling process can be avoided.
S302, compiling non-plug-in program resources and each plug-in program resource to obtain non-plug-in program resource compiling results and each plug-in program resource compiling results.
After the non-plug-in and the resources of each plug-in are split into respective units, the resources may be compiled for each unit in the first compilation project, respectively.
After the above-mentioned resource compilation is completed, the resource compilation result of each plug-in program may be saved in the directory corresponding to each plug-in program, and only the resource compilation result of the non-plug-in program is reserved in the first compilation project.
S303, splitting the compiled code compiling result according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program.
The step is executed after the code compiling is carried out on the object to be compiled.
Optionally, code compiling is performed on the object to be compiled, that is, code compiling is performed on the complete code of the application program in a unified manner, and the problem that the dependent code cannot be found is avoided through unified compiling. Further, after complete code compiling is completed, the compiled code may be split according to the configuration information described above. Specifically, by the configuration information described above, it is possible to know which code belongs to which plug-in or non-plug-in, and therefore, it is possible to package the code compilation result belonging to one plug-in into one unit and the code compilation result belonging to the non-plug-in into one unit.
After the code compiling results of the non-plug-in program and the plug-in program are obtained, the code compiling results of the plug-in programs may be saved in the directories corresponding to the plug-in programs, and only the code compiling results of the non-plug-in program are reserved in the first compiling engineering.
As an alternative way, after splitting the compiled code compiling result, the obfuscating process may be performed on the code compiling result of the non-plug-in program and the code compiling result of each plug-in program at the same time, so as to obtain the obfuscated code compiling result of the non-plug-in program and the code compiling result of each plug-in program.
The simultaneous confusion process refers to that the code compiling result of the non-plug-in program and the code compiling result of each plug-in program are uniformly mixed. By simultaneously carrying out confusion processing, confusion conflict between non-plug-in programs and plug-in programs can be avoided, and further, the compiling result of the application program is ensured to be accurate.
The following is a compilation process based on gradle, and the improved application process of steps S301 to S303 in gradle is described.
Fig. 4 is a schematic illustration of the compilation process of gradle, as shown in fig. 4, comprising the following task steps: pre-build, ready to publish dependencies, merge publish resources, process publish displays, generate publish resources, java precompiled publications, compile publications Java (compileReleaseJavaWithJavac) with java, compile publish resources, publish conversion processes (transformative classanaldsresource with ProteProteForrelease).
The electronic device may monitor the tasks of the first compiling project, and when it is monitored that the first compiling project has executed the tasks described below, add the processing procedure of the embodiment of the present application on the basis of the gradle original processing. With continued reference to fig. 4, the details are as follows:
when it is monitored that the execution of the mergereleaseResources task has started, the process of step S301 is added above the gradle original process, namely, resource splitting is performed. Only the resource of the non-plug-in program is used as the resource of the first compiling engineering. In addition, uniform screening and preprocessing can be performed on certain resources in the step.
When it is monitored that the generaterelease task has started to be executed, the process of the step S302 is added on the basis of compiling the resources belonging to the first compiling engineering in the gradle original processing, and the operation of compiling the resources of each plug-in engineering is added. And after the compiling is completed, the resource compiling results of the plug-in projects are stored in a designated directory, and only the resource compiling results of the non-plug-in programs are reserved in the first compiling project.
When the fact that the execution of the compileReleaseJavaWithJavac task is started is monitored, the compileReleaseJavaWithJavac task compiles the complete code unification of the application program. Any modifications and movements may be made to the source code file prior to compilation in the present task to achieve more precise control and modification of the compilation process.
When it is monitored that the execution of the transformclassesAndResourceWithProguardForRelease task has started, the processing procedure of the step S301 is added above the original processing of the gradle, and the splitting of the code compiling result of each plug-in program is added.
Specifically, the compileReleaseJavaWithJavac task may compile a code into a plurality of jar files, split the jar files according to configuration information in the transformClassesAndResourceWithProguarForRelease task, and synthesize the jar of each plug-in into a jar file. In addition, after the splitting is completed, the resource compiling results of each plug-in project are stored in a designated directory, and only the resource compiling results of non-plug-in programs are reserved in the first compiling project.
After the above processing is added, only the resources and the code compiling results of the non-plug-in program are reserved in the first compiling engineering of the gradle, and the packageRelease task is continuously executed, so that the executable file of the non-plug-in program, such as an apk file, can be obtained.
And the resource compiling result and the code compiling result of the split plug-in program are stored in a designated catalog, and after the second compiling project is created, the result is input into the compiling project. Optionally, the execution of the second compiling engineering is performed according to the task steps shown in fig. 4.
As an alternative implementation, the electronic device may also perform task listening on the second compilation project. When the situation that any of the mergeReleaseResources is started to be executed is monitored, replacing the resource compiling result of the plug-in program, and outputting an executable file of the plug-in program according to the resource compiling result after the replacing and the code compiling result of the plug-in program. The replacing process may be to replace the original initial value in the second compiling process with the resource compiling result. Through the replacement operation, the second compiling engineering can acquire correct resource information in subsequent compiling processing, and further the accuracy of a compiling result is ensured.
As an alternative implementation, the configuration information of the foregoing embodiments may be represented in the form of a target configuration file.
Accordingly, in the step S303, the compiled code compiling result may be split according to the target configuration file, so as to obtain a code compiling result of the non-plug-in program and a code compiling result of each plug-in program.
Accordingly, in the step S301, the object to be compiled may be split into the resources of the non-plug-in program and the resources of each plug-in program according to the target configuration file.
The target configuration file may be an xml file, for example.
Fig. 5 is a block diagram of a compiling apparatus according to an embodiment of the present application, as shown in fig. 5, the apparatus includes:
the obtaining module 501 is configured to obtain an object to be compiled in a first compiling project, where the object to be compiled includes codes and resources of an application to be compiled, where the codes and resources respectively belong to a non-plug-in program and at least one plug-in program of the application.
The processing module 502 is configured to process, in a first compiling project, the object to be compiled according to the configuration information of the non-plug-in program and the at least one plug-in program, to obtain a resource compiling result of the non-plug-in program, a resource compiling result of each plug-in program, a code compiling result of the non-plug-in program, and a code compiling result of each plug-in program.
An output module 503, configured to output the executable file of the non-plug-in program and the executable file of the plug-in program respectively.
As an alternative embodiment, the output module 503 is specifically configured to:
outputting an executable file of the non-plug-in program through the first compiling engineering according to the resource compiling result of the non-plug-in program and the code compiling result of the non-plug-in program; and outputting the executable file of the plug-in program through a second compiling project according to the resource compiling result of the plug-in program and the code compiling result of the plug-in program.
As an alternative embodiment, the processing module 502 is specifically configured to:
according to the configuration information of the non-plug-in program and the at least one plug-in program, carrying out resource splitting on the object to be compiled to obtain the resources of the non-plug-in program and the resources of each plug-in program; compiling the non-plug-in program resources and the plug-in program resources to obtain non-plug-in program resource compiling results and plug-in program resource compiling results; splitting the compiled code compiling result according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program.
As an alternative embodiment, the processing module 502 is specifically configured to:
compiling and allocating identifiers for the resources of the non-plug-in program and the resources of each plug-in program to obtain a resource compiling result of the non-plug-in program and a resource compiling result of each plug-in program, wherein the identifiers of the resource compiling result of the non-plug-in program and the identifiers of the resource compiling result of each plug-in program are different from each other.
As an alternative embodiment, the processing module 502 is further configured to:
and simultaneously carrying out confusion processing on the code compiling result of the non-plug-in program and the code compiling result of each plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program after the confusion processing.
As an alternative embodiment, the output module 503 is specifically configured to:
inputting the resource compiling result of the plug-in program and the code compiling result of the plug-in program into the second compiling project, so as to replace the resource compiling result of the plug-in program through the second compiling project, and outputting the executable file of the plug-in program according to the resource compiling result of the plug-in program and the code compiling result of the plug-in program after the replacing process.
As an alternative embodiment, the processing module 502 is specifically configured to:
splitting the compiled code compiling result according to the target configuration file to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program.
The target configuration file is used for identifying the configuration information.
As an alternative embodiment, the processing module 502 is specifically configured to:
and according to the target configuration file, splitting the resources of the object to be compiled to obtain the resources of the non-plug-in program and the resources of each plug-in program.
The target configuration file is used for identifying the configuration information.
The compiling device provided in the embodiment of the present application may execute the method steps in the embodiment of the method, and its implementation principle and technical effects are similar, and are not described herein again.
It should be noted that, it should be understood that the division of the modules of the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. For example, the determining module may be a processing element that is set up separately, may be implemented in a chip of the above apparatus, or may be stored in a memory of the above apparatus in the form of program code, and may be called by a processing element of the above apparatus and execute the functions of the determining module. The implementation of the other modules is similar. In addition, all or part of the modules can be integrated together or can be independently implemented. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in a software form.
For example, the modules above may be one or more integrated circuits configured to implement the methods above, such as: one or more specific integrated circuits (application specific integrated circuit, ASIC), or one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA), or the like. For another example, when a module above is implemented in the form of a processing element scheduler code, the processing element may be a general purpose processor, such as a central processing unit (central processing unit, CPU) or other processor that may invoke the program code. For another example, the modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.
According to embodiments of the present application, an electronic device and a readable storage medium are also provided.
As shown in fig. 6, a block diagram of an electronic device according to a compiling method according to an embodiment of the application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the application described and/or claimed herein.
As shown in fig. 6, the electronic device includes: one or more processors 601, memory 602, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the electronic device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In other embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple electronic devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). One processor 601 is illustrated in fig. 6.
Memory 602 is a non-transitory computer-readable storage medium provided herein. Wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the compiling method provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to execute the compiling method provided in the present application.
The memory 602 is used as a non-transitory computer readable storage medium for storing non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules (e.g., the acquisition module 501, the processing module 502, and the output module 503 shown in fig. 5) corresponding to the compiling method in the embodiments of the present application. The processor 601 executes various functional applications of the server and data processing, i.e., implements the compiling method in the above-described method embodiments, by running non-transitory software programs, instructions, and modules stored in the memory 602.
The memory 602 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for a function; the storage data area may store data created according to the use of the electronic device of the compiling process, and the like. In addition, the memory 602 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 602 may optionally include memory located remotely from processor 601, which may be connected to the compiling processing electronic device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the compiling method may further include: an input device 603 and an output device 604. The processor 601, memory 602, input device 603 and output device 604 may be connected by a bus or otherwise, for example in fig. 6.
The input device 603 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device of the compilation process, such as a touch screen, keypad, mouse, trackpad, touchpad, pointer stick, one or more mouse buttons, trackball, joystick, etc. input devices. The output means 604 may include a display device, auxiliary lighting means (e.g., LEDs), tactile feedback means (e.g., vibration motors), and the like. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device may be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASIC (application specific integrated circuit), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computing programs (also referred to as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present application may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions disclosed in the present application can be achieved, and are not limited herein.
The above embodiments do not limit the scope of the application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims (10)

1. A compiling method, comprising:
acquiring an object to be compiled in a first compiling project, wherein the object to be compiled comprises codes and resources of an application program to be compiled, and the codes and the resources are respectively attributed to a non-plug-in program and at least one plug-in program of the application program;
according to the configuration information of the non-plug-in program and the at least one plug-in program, carrying out resource splitting on the object to be compiled to obtain the resources of the non-plug-in program and the resources of each plug-in program;
compiling the resources of the non-plug-in program and the resources of each plug-in program to obtain a compiling result of the resources of the non-plug-in program and a compiling result of the resources of each plug-in program;
splitting the compiled code compiling result according to the configuration information to obtain a code compiling result of the non-plug-in program and a code compiling result of each plug-in program;
And outputting the executable file of the non-plug-in program and the executable file of the plug-in program respectively.
2. The method of claim 1, wherein the outputting the non-plug-in executable and the plug-in executable, respectively, comprises:
outputting an executable file of the non-plug-in program through the first compiling engineering according to the resource compiling result of the non-plug-in program and the code compiling result of the non-plug-in program;
and outputting the executable file of the plug-in through a second compiling project according to the resource compiling result of the plug-in and the code compiling result of the plug-in.
3. The method according to claim 1, wherein compiling the non-plug-in resource and the plug-in resource to obtain the non-plug-in resource compiling result and the plug-in resource compiling result includes:
compiling and allocating identifiers for the resources of the non-plug-in program and the resources of each plug-in program to obtain a resource compiling result of the non-plug-in program and a resource compiling result of each plug-in program, wherein the identifiers of the resource compiling result of the non-plug-in program and the identifiers of the resource compiling result of each plug-in program are different from each other.
4. The method according to claim 1, wherein after splitting the compiled code compilation results to obtain the code compilation results of the non-plug-in program and the code compilation results of each plug-in program, the method further comprises:
and simultaneously carrying out confusion processing on the code compiling result of the non-plug-in program and the code compiling result of each plug-in program to obtain the code compiling result of the non-plug-in program and the code compiling result of each plug-in program after the confusion processing.
5. The method according to claim 2, wherein the outputting the executable file of the plug-in program through the second compiling engineering based on the resource compiling result of the plug-in program and the code compiling result of the plug-in program includes:
inputting the resource compiling result of the plug-in program and the code compiling result of the plug-in program into the second compiling project, so as to replace the resource compiling result of the plug-in program through the second compiling project, and outputting the executable file of the plug-in program according to the resource compiling result of the plug-in program and the code compiling result of the plug-in program after the replacing process.
6. The method according to any one of claims 3 to 5, wherein splitting the compiled code compilation results according to the configuration information to obtain the code compilation results of the non-plug-in program and the code compilation results of each plug-in program includes:
splitting the compiled code compiling result according to the target configuration file to obtain a code compiling result of the non-plug-in program and a code compiling result of each plug-in program;
the target configuration file is used for identifying the configuration information.
7. The method according to any one of claims 3-5, wherein said splitting the resources of the object to be compiled according to the configuration information of the non-plug-in and the at least one plug-in to obtain the resources of the non-plug-in and the resources of each plug-in includes:
according to the target configuration file, splitting the resources of the object to be compiled to obtain the resources of the non-plug-in program and the resources of each plug-in program;
the target configuration file is used for identifying the configuration information.
8. A compiling apparatus, comprising:
The system comprises an acquisition module, a compiling module and a compiling module, wherein the acquisition module is used for acquiring an object to be compiled in a first compiling project, the object to be compiled comprises codes and resources of an application program to be compiled, and the codes and the resources are respectively attributed to a non-plug-in program and at least one plug-in program of the application program;
the processing module is used for splitting the resources of the object to be compiled according to the configuration information of the non-plug-in program and the at least one plug-in program to obtain the resources of the non-plug-in program and the resources of each plug-in program;
compiling the resources of the non-plug-in program and the resources of each plug-in program to obtain a compiling result of the resources of the non-plug-in program and a compiling result of the resources of each plug-in program;
splitting the compiled code compiling result according to the configuration information to obtain a code compiling result of the non-plug-in program and a code compiling result of each plug-in program;
and the output module is used for respectively outputting the executable file of the non-plug-in program and the executable file of the plug-in program.
9. An electronic device, comprising:
at least one processor; and
A memory communicatively coupled to the at least one processor; wherein,,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
10. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-7.
CN201911319075.5A 2019-12-19 2019-12-19 Compiling method, compiling device, electronic equipment and readable storage medium Active CN111124420B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911319075.5A CN111124420B (en) 2019-12-19 2019-12-19 Compiling method, compiling device, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911319075.5A CN111124420B (en) 2019-12-19 2019-12-19 Compiling method, compiling device, electronic equipment and readable storage medium

Publications (2)

Publication Number Publication Date
CN111124420A CN111124420A (en) 2020-05-08
CN111124420B true CN111124420B (en) 2023-06-20

Family

ID=70500224

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911319075.5A Active CN111124420B (en) 2019-12-19 2019-12-19 Compiling method, compiling device, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN111124420B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111638884B (en) * 2020-05-19 2021-07-23 贝壳找房(北京)科技有限公司 Method, system, device and storage medium for plug-in engineering compilation
CN111796878B (en) * 2020-06-05 2024-04-12 北京沃东天骏信息技术有限公司 Resource splitting and loading method and device applied to single-page application
CN112148303B (en) * 2020-09-28 2024-05-28 Oppo(重庆)智能科技有限公司 File generation method, device, terminal and storage medium
CN113010180A (en) * 2021-03-12 2021-06-22 山东英信计算机技术有限公司 Firmware generation method, system, device and medium
CN115408047B (en) * 2022-08-11 2023-07-25 北京大氪信息科技有限公司 Version release method and device and electronic equipment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107817978A (en) * 2017-09-28 2018-03-20 聚好看科技股份有限公司 The generation method and device of a kind of executable file
CN109358841A (en) * 2018-08-15 2019-02-19 中国平安人寿保险股份有限公司 Web application develops Compilation Method, device and storage equipment, computer equipment
CN109857405A (en) * 2019-02-02 2019-06-07 Oppo广东移动通信有限公司 Compilation Method, device, storage medium and the terminal of application program installation kit

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104090785B (en) * 2014-06-19 2017-12-29 小米科技有限责任公司 Application program provides method, apparatus and system
CN106201481A (en) * 2016-06-30 2016-12-07 传线网络科技(上海)有限公司 Assembly management method and apparatus in application development system
CN106569869B (en) * 2016-11-14 2019-04-19 平安科技(深圳)有限公司 Plug-in unit packaging method and device
US10579575B2 (en) * 2017-02-24 2020-03-03 Dell Products L.P. Systems and methods of management console user interface pluggability
CN106980504B (en) * 2017-03-28 2022-07-01 腾讯科技(深圳)有限公司 Application program development method and tool and equipment thereof
CN108595221B (en) * 2018-04-26 2021-04-06 Oppo广东移动通信有限公司 Plug-in loading method, device, server and storage medium of PaaS platform
CN110308900B (en) * 2019-06-27 2023-08-08 广州方硅信息技术有限公司 Page routing document generation method and device, computer equipment and storage medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107817978A (en) * 2017-09-28 2018-03-20 聚好看科技股份有限公司 The generation method and device of a kind of executable file
CN109358841A (en) * 2018-08-15 2019-02-19 中国平安人寿保险股份有限公司 Web application develops Compilation Method, device and storage equipment, computer equipment
CN109857405A (en) * 2019-02-02 2019-06-07 Oppo广东移动通信有限公司 Compilation Method, device, storage medium and the terminal of application program installation kit

Also Published As

Publication number Publication date
CN111124420A (en) 2020-05-08

Similar Documents

Publication Publication Date Title
CN111124420B (en) Compiling method, compiling device, electronic equipment and readable storage medium
US11663110B2 (en) Analysis to check web API code usage and specification
CN111666206B (en) Method, device, equipment and storage medium for acquiring influence range of change code
CN111832736B (en) Method, apparatus and computer readable storage medium for processing machine learning model
US9852015B2 (en) Automatic discovery of a JavaScript API
US10089089B2 (en) Data type reassignment
US9262237B2 (en) Automating software availability management based on API versioning
CN111694564B (en) Method, device, equipment and medium for compiling Flutter mixed mode
US20150363195A1 (en) Software package management
CN111752572B (en) Compiling method, device, equipment and storage medium
CN111475164B (en) Component dependency relationship detection method and device and electronic equipment
US9569203B2 (en) Service-based integration of application patterns
CN117149459A (en) Micro front-end system, construction method and device of micro front-end system and electronic equipment
US11288044B1 (en) System and method for interprocedural analysis
US8365154B2 (en) Multi-language software development
CN112130888B (en) Method, device, equipment and computer storage medium for updating application program
CN111639116B (en) Data access connection session protection method and device
US8806434B2 (en) Dynamically configuring an integrated development environment
US9519566B2 (en) Modeling memory use of applications
US9172395B2 (en) Generating an ICONV module in real time
CN116974555A (en) Method, device, equipment and storage medium for assembling software development kit
CN111831317B (en) Method and device for acquiring dependency relationship between services, electronic equipment and storage medium
CN117149609A (en) Method and device for testing interface
US10776255B1 (en) Automatic verification of optimization of high level constructs using test vectors
CN112379885A (en) Applet compiling method, device and equipment 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