CN111176625A - Method for efficiently compiling identity intelligent contract at browser end - Google Patents
Method for efficiently compiling identity intelligent contract at browser end Download PDFInfo
- Publication number
- CN111176625A CN111176625A CN201911424066.2A CN201911424066A CN111176625A CN 111176625 A CN111176625 A CN 111176625A CN 201911424066 A CN201911424066 A CN 201911424066A CN 111176625 A CN111176625 A CN 111176625A
- Authority
- CN
- China
- Prior art keywords
- compiler
- file
- browser
- compiling
- version
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- Y—GENERAL 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
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE 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/00—Energy 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)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method for efficiently compiling a Solidity intelligent contract at a browser end, which comprises the following steps: firstly, deploying all current consistency compilers on a domestic server or CDN node, and updating the latest compiler in time; secondly, a consistency source file is transmitted or input into a browser end, and a WASM format file of a consistency compiler is built in a browser script; directly compiling the intelligent contract file by using a Solidity compiler, and returning a compiling result in the Javascript main thread; or pulling a required consistency compiler from a domestic server or a CDN node by dynamically adding a script file, executing compilation operation on a Javascript sub-thread, and returning a compilation result to a main thread; when the intelligent contract file is compiled, a compiler needing to be pulled does not download the intelligent contract file completely, or the intelligent contract file is pulled unsuccessfully, the identity source code is compiled through the back-end service, and then the compiling result is returned to the front-end browser. The invention can avoid the blockage of the main thread and ensure the high-efficiency and stable consistency compiling environment.
Description
Technical Field
The invention relates to a Solidity intelligent contract compiling technology, in particular to a method for efficiently compiling a Solidity intelligent contract at a browser end.
Background
In the existing block chain application development mode, a developer often compiles a solid intelligent contract 1) by installing a binary file of a solid intelligent contract compiler in a local computer and compiling the intelligent contract in a command line mode to obtain a compiling result. 2) A solid intelligent contract compiler binary file is deployed and installed in a certain server, and a compiling result is obtained in a service calling mode. 3) And compiling a solid intelligent contract through a browser-side online tool Remix and acquiring the result. However, these several approaches have more or less problems: 1) local installation of binary files requires developers to be familiar with relevant knowledge and learn command lines, so that the learning cost is increased, and local computer resources are consumed; 2) when the remote server is provided with a compiling tool, under the condition that developers are increased and the compiling request amount is increased, the load of a server side is easily overlarge, so that the compiling process is abnormal or quit, and a special operation and maintenance worker needs to maintain the compiling service; 3) when the complexity file in the remix is compiled, because the remix is a mode of assigning a compiler on a foreign server through dynamic loading deployment, the network service is unstable, the loading speed is usually slow, the compiler can be downloaded after waiting for a long time, and sometimes the compiler cannot be loaded well even for a long time.
Disclosure of Invention
Aiming at the defects in the technical scheme of compiling the Solidity intelligent contract, the invention provides a method for efficiently compiling the Solidity intelligent contract at a browser end, and the method can provide convenient, stable and efficient Solidity online compiling service.
The purpose of the invention is realized by the following technical scheme: a method for efficiently compiling a identity smart contract at a browser side, the method comprising the steps of:
(1) deploying all current solid compilers on a domestic server or CDN node, comparing a version list with an official compiler warehouse of a foreign Ethernet workshop periodically, and updating the latest compiler in time;
(2) a consistency source file is transmitted or input at a browser end, and a WASM format file of a latest and stable consistency compiler is built in a browser script;
(3) if the compiler version of the Solity source code statement is consistent with the built-in compiler version or the compiler version is not declared, directly compiling the intelligent contract file by using the Solity compiler of the built-in WASM version, and returning a compiling result in the Javascript main thread; if the compiler version is stated by the Solidiy source file and the version is not consistent with the Solidiy compiler of the built-in WASM file, the src attribute is appointed to be a path of a domestic server or a CDN node in a mode of dynamically adding a script tag to a Javascript code, so that a needed Solidiy compiler is pulled, meanwhile, the compiling operation of the intelligent contract file is executed on a Javascript sub-thread, and a compiling result is returned to a main thread;
(4) if the compiler needing to be pulled has not been downloaded or the pulling fails when the intelligent contract file is compiled in the step (3), sending the source code to node.js back-end service in a mode of request of a client server, compiling the identity source code through the back-end service, and then returning a compiling result to the front-end browser;
(5) and (4) when the same intelligent contract file requests compilation again, returning to the step (3).
Further, in the step (1), before deploying all the Solidity compilers on the domestic server or the CDN node or pulling the latest version compiler to the etherhouse official Solidity compiler repository, the compiler of the C + + version needs to be compiled into the asm.js version file supporting the front-end browser environment and the node.js environment through an emscript or other LLVM tool.
Further, in the step (2), before the latest and stable compiler is built in the browser, the C + + version compiler needs to be compiled into a WASM file in a binary byte code format supported by the browser through an script or other LLVM tools, and then the WASM file is packaged into front-end script code through a front-end packaging tool such as Webpack. Whether the built-in WASM file compiler is used is judged by the version number declared by the identity file in the browser. The compiler is used in case the versions match correctly or the identity file does not declare a version number.
Further, in the step (2), the WASM format file is a binary byte code file and can be directly run in the browser without interpretation and compilation by a browser script engine.
Further, in the step (3), when the consistency file in the browser end fails to match the WASM compiler file, the browser dynamically creates a script, loads the compiler version corresponding to the current consistency file in the domestic server or CDN node, and simultaneously creates a Web Worker sub-thread to compile the consistency file and returns the compilation result to the JavaScript main thread, thereby effectively preventing the JavaScript main thread from being blocked.
Further, in the step (4), all the Solidity compilers in the domestic server or the CDN nodes are synchronized in the back-end node. When a script is dynamically created in a browser to pull a compiler without completing or failing downloading, a client server request is temporarily sent to send a solicitation source file code to a node.js service, the compilation operation is executed in the node.js service, a compiled result is returned to the browser end, and the loaded compiler is used for executing the compilation operation after the compiler at the browser end is loaded.
The invention has the following beneficial effects:
firstly, a Solidy compiler of an original C + + version is compiled into a compiler in an asm.js format through compiling of Emscript or other specific LLVM tools, so that a Javascript language environment can be supported, the Solidy compiler can run in a browser end and a node.js, the running of the compiler in the browser end saves most of computer resources and learning cost of developers, and a Solidy intelligent contract can be compiled through simple visual operation. Meanwhile, a WASM format file is compiled through an Emscript or other specific LLVM tools, the file is a binary byte code file which runs at a browser end, and compared with a traditional Javascript file, the browser saves the process of interpretation and compilation during execution, so that the efficiency of the whole compiler execution process can be greatly improved. Secondly, different compiler scripts are dynamically loaded in the browser, so that on one hand, server pressure can be shared, on the other hand, the number of built-in web assembly version compilers can be reduced, the size of an initialized Javascript script file is kept small, and in addition, a sub-thread is created in the modern browser through WebWorker to execute a compiling process, so that the blockage of a main thread can be avoided. And finally, the support of the node.js compiler service prevents some abnormal conditions in the process of loading the compiler by the browser. All the steps ensure that the browser provides an efficient and stable consistency compiling environment.
Drawings
FIG. 1 is an architecture diagram of a method for efficiently compiling a Solidiy intelligent contract at a browser side in accordance with the present invention;
FIG. 2 is a flow chart of a method for efficiently compiling a Solidiy intelligent contract at a browser side of the present invention.
Detailed Description
The method for efficiently compiling the identity intelligent contract at the browser side of the invention is further explained in the following by combining the attached drawings.
As shown in fig. 1, a method for efficiently compiling a identity smart contract at a browser side includes the following steps:
(1) compiling the compiler of the C + + version into an asm.js version file supporting a front-end browser environment and a node.js environment through an Emscript or other LLVM tools, deploying all current Solidity compilers on a domestic server or a CDN node, comparing a version list with an official compiler warehouse of an overseas ether house regularly, and updating the latest compiler in time;
(2) a consistency source file is transmitted or input at a browser end, and a WASM format file of a latest and stable consistency compiler is built in a browser script; the method specifically comprises the following steps: compiling the C + + version compiler into a WASM file in a binary byte code format supported by the browser through an Emscript or other LLVM tools, and then packaging the WASM file into a front-end script code through a front-end packaging tool such as Webpack, wherein the WASM file can directly run in the browser without the interpretation and compilation of a browser script engine. Whether the built-in WASM file compiler is used is judged by the version number declared by the identity file in the browser. The compiler is used in case the versions match correctly or the identity file does not declare a version number.
(3) Directly compiling the intelligent contract file by using a Solidity compiler with a built-in WASM version, and returning a compiling result in the Javascript main thread; or the src attribute is specified to be a path of a domestic server or a CDN node in a mode of dynamically adding a script tag to the Javascript code, so that a required Solity compiler is pulled, meanwhile, the compiling operation of the intelligent contract file is executed on a Javascript sub thread, and a compiling result is returned to a main thread; when the consistency file in the browser end fails to be matched with the WASM compiler file, the browser dynamically creates a script, loads a compiler version corresponding to the current consistency file in a domestic server or a CDN node, simultaneously creates a Web Worker sub-thread to compile the consistency file, and returns a compiling result to a JavaScript main thread, thereby effectively preventing the JavaScript main thread from being blocked.
(4) If the compiler needing to be pulled has not been downloaded or the pulling fails when the intelligent contract file is compiled in the step (3), sending the source code to node.js back-end service in a mode of request of a client server, compiling the identity source code through the back-end service, and then returning a compiling result to the front-end browser; the method specifically comprises the following steps: js, synchronizing all the identity compilers in the domestic server or the CDN node, and periodically pulling the latest identity compiler in the server by comparing the version lists of the compilers. When a script is dynamically created in a browser to pull a compiler without completing or failing downloading, a client server request is temporarily sent to send a solicitation source file code to a node.js service, the compilation operation is executed in the node.js service, a compiled result is returned to the browser end, and the loaded compiler is used for executing the compilation operation after the compiler at the browser end is loaded.
(5) And (4) when the same intelligent contract file requests compilation again, returning to the step (3).
As shown in FIG. 2, the Solidity intelligent contract compilation process is totally divided into the following steps:
(1) a consistency source file is transmitted or input at a browser end to mark a required compiler version, and if not, a default built-in compiler is used as a standard;
(2) starting compiling, and directly compiling by using the compiler version of the built-in WASM version when the compiler version of the Solity source code statement is consistent with the built-in compiler version or no compiler version is declared, and returning a compiling result;
(3) if the compiler version is declared by the consistency source file and the version is not consistent with the built-in consistency compiler of the WASM version, a script file is dynamically created to pull the compiler of the corresponding version from a domestic server or a CDN node, meanwhile, the compiling operation is executed on a Javascript sub thread, and the compiling result is returned to a main thread;
(4) and (4) when the compiler with the specified version is not found during the dynamic pulling in the step (3), inquiring whether the compiler with the version exists in a compiler warehouse of the official party, if so, updating the compiler in the server, and simultaneously giving an error prompt to the browser.
(5) If the pulling compiler in the step (3) is too slow or the pulling fails, sending the source code to node.js back-end service in a manner of request of a client server, compiling the identity source code through the back-end service, and then returning a compiling result to the front-end browser;
(6) if the step (5) finds that no corresponding compiler version exists in the node.js, the server in China is inquired whether a compiler with the version exists or not, if yes, the compiler in the node.js service is updated, and meanwhile, an error message is returned to the browser;
(7) and (4) when the same file is compiled again after the step (3), judging whether the local compiler script is loaded completely or not through the step (3), and otherwise, continuing the operations in the steps (4), (5) and (6).
The above-described embodiments are intended to illustrate rather than to limit the invention, and any modifications and variations of the present invention are within the spirit of the invention and the scope of the appended claims.
Claims (6)
1. A method for efficiently compiling a identity smart contract at a browser side, the method comprising the steps of:
(1) deploying all current solid compilers on a domestic server or CDN node, comparing a version list with an official compiler warehouse of a foreign Ethernet workshop periodically, and updating the latest compiler in time;
(2) a consistency source file is transmitted or input at a browser end, and a WASM format file of a latest and stable consistency compiler is built in a browser script;
(3) if the compiler version of the Solity source code statement is consistent with the built-in compiler version or the compiler version is not declared, directly compiling the intelligent contract file by using the Solity compiler of the built-in WASM version, and returning a compiling result in the Javascript main thread; if the compiler version is stated by the Solidiy source file and the version is not consistent with the Solidiy compiler of the built-in WASM file, the src attribute is appointed to be a path of a domestic server or a CDN node in a mode of dynamically adding a script tag to a Javascript code, so that a needed Solidiy compiler is pulled, meanwhile, the compiling operation of the intelligent contract file is executed on a Javascript sub-thread, and a compiling result is returned to a main thread;
(4) if the compiler needing to be pulled has not been downloaded or the pulling fails when the intelligent contract file is compiled in the step (3), sending the source code to node.js back-end service in a mode of request of a client server, compiling the identity source code through the back-end service, and then returning a compiling result to the front-end browser;
(5) and (4) when the same intelligent contract file requests compilation again, returning to the step (3).
2. The method for compiling the Solidity intelligent contract at the browser side efficiently according to claim 1, wherein in the step (1), all the Solidity compilers are deployed on a domestic server or a CDN node, or a compiler of the C + + version needs to be compiled into an asm.
3. The method for efficiently compiling the identity intelligent contract at the browser side according to claim 1, wherein in the step (2), before a latest and stable compiler is built in the browser, a C + + version compiler needs to be compiled into a WASM file in a binary byte code format supported by the browser through an emscript or other LLVM tools, and then the WASM file is packaged into front-end script code through a front-end packaging tool such as Webpack. Whether the built-in WASM file compiler is used is judged by the version number declared by the identity file in the browser. The compiler is used in case the versions match correctly or the identity file does not declare a version number.
4. The method for efficiently compiling a identity smart contract at a browser side according to claim 3, wherein in the step (2), the WASM format file is a binary byte code file and can be directly run in the browser without being interpreted and compiled by a browser script engine.
5. The method for efficiently compiling the identity intelligent contract at the browser end according to claim 1, wherein in the step (3), when the identity file in the browser end fails to match the WASM compiler file, the browser dynamically creates a script, loads a compiler version corresponding to the current identity file in a domestic server or a CDN node, and simultaneously creates a Web Worker sub thread to compile the identity file and returns a compiling result to the JavaScript main thread, thereby effectively preventing the JavaScript main thread from being blocked.
6. The method for efficiently compiling the identity intelligent contract at the browser side according to claim 1, wherein in the step (4), all identity compilers in a domestic server or a CDN node are synchronized in a back-end node.js, and meanwhile, the latest identity compiler in the server is periodically pulled by comparing a compiler version list. When a script is dynamically created in a browser to pull a compiler without completing or failing downloading, a client server request is temporarily sent to send a solicitation source file code to a node.js service, the compilation operation is executed in the node.js service, a compiled result is returned to the browser end, and the loaded compiler is used for executing the compilation operation after the compiler at the browser end is loaded.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911424066.2A CN111176625B (en) | 2019-12-31 | 2019-12-31 | Method for efficiently compiling intelligent contract of solubility at browser end |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911424066.2A CN111176625B (en) | 2019-12-31 | 2019-12-31 | Method for efficiently compiling intelligent contract of solubility at browser end |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111176625A true CN111176625A (en) | 2020-05-19 |
| CN111176625B CN111176625B (en) | 2023-07-28 |
Family
ID=70649150
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911424066.2A Active CN111176625B (en) | 2019-12-31 | 2019-12-31 | Method for efficiently compiling intelligent contract of solubility at browser end |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111176625B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111737621A (en) * | 2020-06-17 | 2020-10-02 | 友虹(北京)科技有限公司 | OFD rendering method, system and device based on WASM |
| CN111815310A (en) * | 2020-08-31 | 2020-10-23 | 支付宝(杭州)信息技术有限公司 | Method for executing intelligent contract, block chain node and storage medium |
| CN111984245A (en) * | 2020-08-31 | 2020-11-24 | 上海玳鸽信息技术有限公司 | Block chain intelligent contract online integrated development environment system and implementation method |
| CN112269602A (en) * | 2020-11-10 | 2021-01-26 | 深圳晶泰科技有限公司 | WebAssembly loading method and device and storage medium |
| CN116048532A (en) * | 2023-04-03 | 2023-05-02 | 深圳市启明智显科技有限公司 | Web-based embedded UI effect simulation preview method, device and system |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070055964A1 (en) * | 2005-09-06 | 2007-03-08 | Morfik Technology Pty. Ltd. | System and method for synthesizing object-oriented high-level code into browser-side javascript |
| US20070094649A1 (en) * | 2005-10-26 | 2007-04-26 | Soumitra Chatterjee | Method and apparatus for providing a compiler interface |
| CN101833449A (en) * | 2010-04-16 | 2010-09-15 | 中山大学 | Compile processing method and system based on cloud computing |
| CN102736943A (en) * | 2012-06-12 | 2012-10-17 | 电子科技大学 | Dynamic compiling and executing method of embedded browser engine |
| WO2012142892A1 (en) * | 2011-04-19 | 2012-10-26 | 腾讯科技（深圳）有限公司 | Script processing method and system for browsers |
| CN105468427A (en) * | 2015-11-19 | 2016-04-06 | 深圳创维数字技术有限公司 | Implementation method and system of automatic compilation and release |
| CN105893103A (en) * | 2014-11-26 | 2016-08-24 | 深圳他拍档电子商务有限公司 | Compilation method and compiler adopting same |
| CN109375899A (en) * | 2018-09-25 | 2019-02-22 | 杭州趣链科技有限公司 | A kind of method of formal verification Solidity intelligence contract |
| CN109683898A (en) * | 2017-09-01 | 2019-04-26 | 北京猿圈科技有限责任公司 | A kind of Compilation Method and cloud compiling system based on cloud compiling |
| CN109766099A (en) * | 2018-12-11 | 2019-05-17 | 浙江口碑网络技术有限公司 | Front end source code Compilation Method, device, storage medium and computer equipment |
-
2019
- 2019-12-31 CN CN201911424066.2A patent/CN111176625B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070055964A1 (en) * | 2005-09-06 | 2007-03-08 | Morfik Technology Pty. Ltd. | System and method for synthesizing object-oriented high-level code into browser-side javascript |
| US20070094649A1 (en) * | 2005-10-26 | 2007-04-26 | Soumitra Chatterjee | Method and apparatus for providing a compiler interface |
| CN101833449A (en) * | 2010-04-16 | 2010-09-15 | 中山大学 | Compile processing method and system based on cloud computing |
| WO2012142892A1 (en) * | 2011-04-19 | 2012-10-26 | 腾讯科技（深圳）有限公司 | Script processing method and system for browsers |
| CN102736943A (en) * | 2012-06-12 | 2012-10-17 | 电子科技大学 | Dynamic compiling and executing method of embedded browser engine |
| CN105893103A (en) * | 2014-11-26 | 2016-08-24 | 深圳他拍档电子商务有限公司 | Compilation method and compiler adopting same |
| CN105468427A (en) * | 2015-11-19 | 2016-04-06 | 深圳创维数字技术有限公司 | Implementation method and system of automatic compilation and release |
| CN109683898A (en) * | 2017-09-01 | 2019-04-26 | 北京猿圈科技有限责任公司 | A kind of Compilation Method and cloud compiling system based on cloud compiling |
| CN109375899A (en) * | 2018-09-25 | 2019-02-22 | 杭州趣链科技有限公司 | A kind of method of formal verification Solidity intelligence contract |
| CN109766099A (en) * | 2018-12-11 | 2019-05-17 | 浙江口碑网络技术有限公司 | Front end source code Compilation Method, device, storage medium and computer equipment |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111737621A (en) * | 2020-06-17 | 2020-10-02 | 友虹(北京)科技有限公司 | OFD rendering method, system and device based on WASM |
| CN111815310A (en) * | 2020-08-31 | 2020-10-23 | 支付宝(杭州)信息技术有限公司 | Method for executing intelligent contract, block chain node and storage medium |
| CN111984245A (en) * | 2020-08-31 | 2020-11-24 | 上海玳鸽信息技术有限公司 | Block chain intelligent contract online integrated development environment system and implementation method |
| US11544044B2 (en) | 2020-08-31 | 2023-01-03 | Alipay (Hangzhou) Information Technology Co., Ltd. | Methods, blockchain nodes, and storage media for executing smart contract |
| CN112269602A (en) * | 2020-11-10 | 2021-01-26 | 深圳晶泰科技有限公司 | WebAssembly loading method and device and storage medium |
| CN112269602B (en) * | 2020-11-10 | 2023-12-29 | 深圳晶泰科技有限公司 | WebAssemble loading method, device and storage medium |
| CN116048532A (en) * | 2023-04-03 | 2023-05-02 | 深圳市启明智显科技有限公司 | Web-based embedded UI effect simulation preview method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111176625B (en) | 2023-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111176625A (en) | Method for efficiently compiling identity intelligent contract at browser end | |
| CN111399853B (en) | Templated deployment method for machine learning model and custom operator | |
| CN111736954B (en) | Multi-intelligent contract virtual machine implementation method, multi-intelligent contract virtual machine and system | |
| US8056062B2 (en) | Methods and systems for converting application code in turbine control systems | |
| CN105446712B (en) | Application program defect repairing method and device | |
| CN109766099B (en) | Front-end source code compiling method and device, storage medium and computer equipment | |
| CN112799677B (en) | Method, device, equipment and storage medium for hook of compiling period | |
| US11068243B2 (en) | Application stack builder based on node features | |
| CN101645009A (en) | Web service integrated development system and method | |
| CN105159732A (en) | Method for installing or updating application program in mobile terminal and mobile terminal | |
| US11474796B1 (en) | Build system for distributed applications | |
| CN110888652A (en) | Multi-version construction method based on jenkins plug-in and terminal | |
| CN105183657A (en) | System and method for testing WEB interface | |
| CN115421765A (en) | Big data management deployment method applied to domestic operating system | |
| CN107608672B (en) | UI module manager, UI module management method and system | |
| CN113934640A (en) | Method and system for automatically testing software | |
| CN108415737B (en) | Method for loading plug-in virtual machine and electronic terminal | |
| CN115658140A (en) | SDK packaging method, device, terminal and storage medium | |
| CN113204351B (en) | Embedded system package management method and using method thereof | |
| CN113360156B (en) | IOS compiling method and related equipment | |
| CN114860300A (en) | Dependency configuration method and device, electronic equipment and storage medium | |
| CN110874226B (en) | Android system function upgrading method | |
| US8898524B2 (en) | Computer-readable medium storing wrapper program and integrated circuit apparatus | |
| CN113741935B (en) | Project and product synchronous iteration upgrading method | |
| CN111078231A (en) | Visualization interface component heat deployment method, client and server |
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 |