Development tool acquisition method and device, computer equipment and storage medium

Abstract

The invention discloses a development tool acquisition method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring an auxiliary tool plug-in; when the tool chain needs to be generated, a plurality of auxiliary tool plug-ins are selected and combined into a tool chain array; and the auxiliary tool plug-ins are loaded in sequence according to the sequence of the tool chain array until all the auxiliary tool plug-ins are loaded in sequence to generate the tool chain. According to the method and the device, the needed auxiliary tool plug-ins are acquired in advance, and the acquired auxiliary tool plug-ins are integrated into a unified plug-in, so that various development tools can be conveniently accessed, and confusion caused by a large number of plug-ins is prevented. Moreover, the user can combine various tool chains for use according to a user-defined use scene to form a south-north tool chain suitable for the user, so that the development efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of operating systems, and in particular to a method and device for acquiring development tools, a computer device and a storage medium. Background Art

[0002] OpenHarmony is an open source project. Its goal is to build a framework and platform for the operating system of intelligent terminal devices based on open source, facing the era of full scenarios, full connection and full intelligence, and promote the development of the Internet of Everything industry. In order to support developers to better use OpenHarmony, a series of auxiliary tools such as Api scanning tools, Gn conversion tools, Service generation tools, Ts generation tools, Napi generation tools, etc. have been developed to help developers better use the OpenHarmony platform and improve development efficiency.

[0003] However, the VS Code plug-ins of the above-mentioned auxiliary tools are all separate entrances. When users need to use certain plug-ins, they need to go to the plug-in market to find and download and install the plug-ins one by one. When there are a large number of plug-ins, it may cause confusion and inconvenience to users. In addition, because there are some dependencies between auxiliary tools, for example, the input file of the next auxiliary tool is the output file of the previous auxiliary tool. If the user needs to use the auxiliary tools as any tool chain, it is necessary to wait for the output results of the dependent auxiliary tools, and then manually configure the input files downstream of the auxiliary tools, which reduces user efficiency and even causes configuration errors.

[0004] Therefore, the prior art still needs to be improved and developed. Summary of the invention

[0005] In view of the above-mentioned deficiencies in the prior art, the purpose of the present invention is to provide a development tool acquisition method, apparatus, computer equipment and storage medium to solve the problems of confusion and inconvenience caused to users when using certain plug-ins, and low efficiency and possible configuration errors when auxiliary tools are combined into any tool chain for use.

[0006] The technical solution of the present invention is as follows:

[0007] In a first aspect, the present invention provides a method for acquiring a development tool, comprising:

[0008] Get auxiliary tool plug-ins for system development;

[0009] When a tool chain needs to be generated, select several auxiliary tool plug-ins and synthesize a tool chain array;

[0010] Load auxiliary tool plug-ins in sequence according to the toolchain array order until all auxiliary tool plug-ins are loaded in order to generate a toolchain;

[0011] Among them, when there is a dependency relationship between two auxiliary tool plug-ins in the previous and subsequent order, the next auxiliary tool plug-in receives the output file path of the previous auxiliary tool plug-in, and obtains the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool plug-in, and uses the output file of the previous auxiliary tool plug-in as the input file.

[0012] In a further configuration of the present invention, the step of obtaining the auxiliary tool plug-in includes:

[0013] Check whether the current environment has installed the required auxiliary tool plug-in. If the current environment has not installed the corresponding auxiliary tool plug-in, download and install the corresponding auxiliary tool plug-in.

[0014] In a further configuration of the present invention, the step of sequentially loading the auxiliary tool plug-ins according to the tool chain array sequence until all the auxiliary tool plug-ins are loaded in sequence to generate the tool chain specifically includes:

[0015] Load the first auxiliary tool plugin according to the order of the toolchain array;

[0016] The first auxiliary tool plug-in loads the next auxiliary tool plug-in in the toolchain array until all auxiliary tool plug-ins are loaded in order.

[0017] In a further configuration of the present invention, the step of sequentially loading auxiliary tool plug-ins according to the tool chain array sequence comprises:

[0018] When the previous auxiliary tool plug-in automatically loads the next auxiliary tool plug-in in the tool chain array, the tool chain array is synchronously passed to the newly loaded auxiliary tool plug-in.

[0019] According to a further configuration of the present invention, the step of the next auxiliary tool plug-in receiving the output file path of the previous auxiliary tool plug-in and obtaining the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool comprises:

[0020] When the previous auxiliary tool plug-in completes processing, the next auxiliary tool plug-in captures and reads the output file path of the previous auxiliary tool plug-in;

[0021] The output file path of the previous auxiliary tool plug-in is set as the input parameter of the next auxiliary tool plug-in, and the next auxiliary tool plug-in uses the input parameter as an input file for subsequent processing.

[0022] According to a further configuration of the present invention, when the previous auxiliary tool plug-in completes processing and outputs an event or signal, the next auxiliary tool plug-in responds to the event or signal output by the previous auxiliary tool plug-in and captures and reads the output file path of the previous auxiliary tool plug-in.

[0023] In a second aspect, the present invention provides a development tool acquisition device, comprising:

[0024] An acquisition unit, used to acquire an auxiliary tool plug-in;

[0025] A tool chain array synthesis unit is used to select several auxiliary tool plug-ins to synthesize a tool chain array when a tool chain needs to be generated;

[0026] A tool chain generation unit is used to load auxiliary tool plug-ins in sequence according to the tool chain array order until all auxiliary tool plug-ins are loaded in sequence to generate a tool chain; wherein, when there is a dependency relationship between two auxiliary tool plug-ins in the previous and subsequent order, the next auxiliary tool plug-in receives the output file path of the previous auxiliary tool plug-in, obtains the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool plug-in, and uses the output file of the previous auxiliary tool plug-in as the input file.

[0027] In a third aspect, the present invention provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is used to implement the steps in the development tool acquisition method as described above when executing the computer program.

[0028] In a fourth aspect, the present invention provides a storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, is used to implement the steps in the development tool acquisition method as described above.

[0029] The present invention provides a method, device, computer equipment and storage medium for acquiring development tools, and a method for acquiring development tools, which includes: acquiring an auxiliary tool plug-in for system development; when a tool chain needs to be generated, selecting several auxiliary tool plug-ins and synthesizing a tool chain array; loading the auxiliary tool plug-ins in sequence according to the tool chain array order until all auxiliary tool plug-ins are loaded in sequence to generate a tool chain; wherein, when there is a dependency relationship between two auxiliary tool plug-ins in the previous and subsequent order, the next auxiliary tool plug-in receives the output file path of the previous auxiliary tool plug-in, and obtains the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool plug-in, and uses the output file of the previous auxiliary tool plug-in as the input file. The present invention obtains the required auxiliary tool plug-in in advance, integrates the obtained auxiliary tool plug-in into a unified plug-in, can facilitate access to various development tools, and prevents confusion caused by a large number of plug-ins. In addition, users can combine various tools according to customized usage scenarios to form a north-south tool chain suitable for themselves, so that they can select a suitable tool combination according to their own needs and habits, reduce unnecessary operations and switching, and avoid configuration errors, thereby improving development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary personnel in this field, other drawings can be obtained based on the structures shown in these drawings without paying any creative work.

[0031] Figure 1 It is a flow chart of the method for acquiring development tools in the present invention.

[0032] Figure 2 It is a flowchart of a method for acquiring development tools in one embodiment of the present invention.

[0033] Figure 3 This is a diagram of the operation interface when the tool chain is not enabled in one embodiment of the present invention.

[0034] Figure 4 This is a diagram of the operation interface of an API scanning tool in one embodiment of the present invention.

[0035] Figure 5 It is a diagram of the operation interface of the Gn conversion tool in one embodiment of the present invention.

[0036] Figure 6 This is a diagram of the operation interface of a Service generation tool in one embodiment of the present invention.

[0037] Figure 7It is a diagram of the operation interface of the Ts generation tool in one embodiment of the present invention.

[0038] Figure 8 It is a diagram of the operation interface of the Napi generation tool in one embodiment of the present invention.

[0039] Fig. 9 This is a diagram of an operation interface for enabling a tool chain in one embodiment of the present invention.

[0040] Fig.10 It is a diagram of the operation interface after the Ts generation tool is configured in one embodiment of the present invention.

[0041] Fig.11 This is a diagram of the operation interface after the Napi generation tool is configured in one embodiment of the present invention.

[0042] Fig.12 It is a principle block diagram of the development tool acquisition device in the present invention. DETAILED DESCRIPTION

[0043] The present invention provides a development tool acquisition method, device, computer equipment and storage medium. In order to make the purpose, technical solution and effect of the present invention clearer and more specific, the present invention is further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0044] In the embodiments and the scope of the patent application, unless the text specifically defines the article, "a", "an", "the" and "the" may also include plural forms. If there are descriptions involving "first", "second", etc. in the embodiments of the present invention, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" or "second" may explicitly or implicitly include at least one of the features.

[0045] It should be further understood that the term "comprising" used in the specification of the present invention refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when an element is said to be "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or there can also be intermediate elements. In addition, the "connection" or "coupling" used herein can include wireless connection or wireless coupling. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0046] It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as generally understood by those skilled in the art in the art to which the present invention belongs. It should also be understood that terms such as those defined in general dictionaries should be understood to have meanings consistent with the meanings in the context of the prior art, and will not be interpreted with idealized or overly formal meanings unless specifically defined as herein.

[0047] In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on the fact that ordinary technicians in the field can implement it. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0048] OpenHarmony provides a series of auxiliary development tools, including Api scanning tools, Gn conversion tools, Service generation tools, Ts generation tools and Napi generation tools, to help developers better use the OpenHarmony platform and improve development efficiency.

[0049] Among them, the Api scanning tool can scan the interfaces in the third-party library that are not included in the OpenHarmony source code, such as the Android system-specific interface, and output the scanning results to the result.xlsx document. The Api scanning tool helps developers quickly understand the interface status of the third-party library and facilitates the evaluation of the subsequent third-party library migration efficiency; the Gn conversion tool is another important auxiliary development tool, which can compile and convert the CMakeLists.txt file of the third-party library to generate the BUILD.gn script file. This can reduce the difficulty of porting the third-party library to OpenHarmony and improve development efficiency; the Service generation tool is a tool that automatically generates the Service framework code, which can automatically generate the entire Service according to a .h header file that defines a remote method. The code required by the framework includes Ability registration, proxy / stub class implementation, MessageParcel data packet construction, Service subsystem compilation and boot-up related configuration files. The Service generation tool simplifies the development process of the Service framework and reduces the workload of manually writing repetitive code; the Ts generation tool can generate TS interface files in the type-script language according to the interface defined in the C++ header file, which is convenient for developers to use in front-end development. The Napi generation tool can generate NAPI framework code, business code framework, GN file, etc. according to the ts (typescript) interface file in the user-specified path. The Ts generation tool and the Napi generation tool further improve the development efficiency and simplify the development process.

[0050] The Service generation tool supports two entry points: executable files and VS Code plug-ins. Users can choose the appropriate entry method according to their preferences and usage environment. Similarly, the Gn conversion tool also supports two entry points: executable files and VS Code plug-ins, which is convenient for users to use in different development environments. The Api scanning tool, Napi generation tool, and Ts generation tool are more flexible. In addition to executable files and VS Code plug-ins, they also support IntelliJ plug-ins as entry points. In this way, users can choose the most suitable way to develop according to their development habits and tool preferences.

[0051] However, the VS Code plug-ins for these tools are currently separate entrances. When users need to use certain plug-ins, they need to go to the plug-in market to find and download and install the plug-ins one by one. When there are a large number of plug-ins, it may cause confusion and inconvenience to users. In addition, there are some dependencies between some tools. For example, the output file of the Ts tool can be used as the input file of the Napi tool. If the user needs to use the tools as any tool chain, he needs to wait for the output results of the dependent tools, and then manually configure the input files of the downstream tools of the auxiliary development tools. This will cause low efficiency for users, frequent configuration operations are cumbersome, and may even cause configuration errors, affecting the user's experience with the tool.

[0052] In response to the above technical problems, the present invention provides a development tool acquisition method, device, computer equipment and storage medium. By pre-acquiring the required auxiliary tool plug-ins, the acquired auxiliary tool plug-ins are integrated into a unified plug-in, and there is no need to download and configure each tool separately. It is convenient to access various development tools, prevent confusion caused by a large number of plug-ins, and improve development efficiency. In addition, users can combine various tools according to customized usage scenarios to form a north-south tool chain suitable for themselves, so that they can choose the appropriate tool combination according to their own needs and habits, reduce unnecessary operations and switching, and avoid configuration errors, further improving development efficiency.

[0053] Please also see Figures 1 to 11 , the present invention provides a preferred embodiment of a method for acquiring a development tool.

[0054] In some embodiments, Figure 1 and Figure 2 As shown, the present invention provides a method for obtaining a development tool, which comprises the steps of:

[0055] S100, obtain auxiliary tool plug-ins for system development;

[0056] In this embodiment, the auxiliary tool plug-in may be, but is not limited to, an Api scanning tool, a Gn conversion tool, a Service generation tool, a Ts generation tool, and a Napi generation tool.

[0057] When you need to select the corresponding auxiliary tool plug-in, it will detect whether the current environment has installed the auxiliary tool plug-in you need to use. If the current environment does not have the corresponding auxiliary tool plug-in installed, download and install the corresponding auxiliary tool plug-in. Figure 3 and Figure 4 As shown in the figure, taking the Api Scan tool as an example, on the operation interface, the user clicks the Api Scan icon and then clicks OK. The system will detect whether the Api Scan tool has been installed in the current environment. If the Api Scan tool has not been downloaded in the current environment, the system will download and install the Api Scan tool in the plug-in market, and then jump to the Api Scan tool homepage. The user can now directly use the Api Scan tool. Figures 5 to 8 As shown, these are the operation interfaces of the Gn conversion tool, Service generation tool, Ts generation tool, and Napi generation tool, respectively.

[0058] S200, when a tool chain needs to be generated, select several auxiliary tool plug-ins and synthesize a tool chain array;

[0059] In this embodiment, each auxiliary tool plug-in is provided with a parameter for controlling whether to enable the tool chain. For example, when the auxiliary tool plug-in is not enabled, the parameter value is false, and when the auxiliary tool plug-in is enabled, the parameter value is true. The user can select the required auxiliary tool plug-in from the five auxiliary tool plug-ins according to the needs and synthesize a tool chain array in a certain order.

[0060] S300, loading auxiliary tool plug-ins in sequence according to the tool chain array order until all auxiliary tool plug-ins are loaded in order to generate a tool chain. Wherein, when there is a dependency relationship between two auxiliary tool plug-ins in the previous and subsequent order, the next auxiliary tool plug-in receives the output file path of the previous auxiliary tool plug-in, obtains the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool plug-in, and uses the output file of the previous auxiliary tool plug-in as the input file.

[0061] In this embodiment, after the synthesis of the tool chain array is completed, the first auxiliary tool plug-in is loaded in accordance with the tool chain array sequence. After the use of the first (i.e., the first) auxiliary tool plug-in is completed, thereafter, the first auxiliary tool plug-in loads the next auxiliary tool plug-in in the tool chain array until all auxiliary tool plug-ins are loaded in sequence. For example, when the user completes the use of the first auxiliary plug-in, the next step is performed (e.g., click "next"), and the auxiliary tool plug-in will automatically load the next auxiliary tool plug-in in the tool chain array until all auxiliary tool plug-ins are loaded and used in sequence, and finally form a user-defined north-south tool chain. If the tool chain is not enabled, the currently selected auxiliary tool plug-in is directly used, and the next step is executed (i.e., click "ok"). When there is a dependency relationship between two consecutive auxiliary tool plug-ins in the tool chain array, that is, the next auxiliary tool plug-in needs the output file of the previous auxiliary tool plug-in as the input file. Then, when the previous auxiliary tool plug-in loads the next auxiliary tool plug-in, the previous auxiliary tool plug-in will not only pass the tool chain array, but also pass the output file path. The next auxiliary tool plug-in will receive the output file path of the previous auxiliary tool plug-in and the output file path of the previous auxiliary tool plug-in as the input file. In this way, it can be ensured that the necessary information can be effectively transmitted between auxiliary tool plug-ins, and the tool chain can be flexibly combined as needed.

[0062] In this way, the present invention can facilitate access to various development tools by pre-acquiring the required auxiliary tool plug-ins and integrating the acquired auxiliary tool plug-ins into a unified plug-in, thereby preventing confusion caused by a large number of plug-ins. In addition, users can combine various tools according to customized usage scenarios to form a north-south tool chain that suits them. These auxiliary tool plug-ins form any tool chain and establish automated dependencies between tool chains. When the output file of one tool is used as the input file of another tool, the system will automatically configure it without manual intervention by the user, so that the user can choose the appropriate tool combination according to their own needs and habits, reduce unnecessary operations and switching, and avoid configuration errors. Users can seamlessly perform coding, conversion, and construction tasks without manually intervening in each step to configure and manage file paths, thereby improving development efficiency.

[0063] In some embodiments, Figure 2 and Figure 3 As shown, the step of loading the auxiliary tool plug-ins in sequence according to the tool chain array sequence includes:

[0064] S310: When the previous auxiliary tool plug-in automatically loads the next auxiliary tool plug-in in the tool chain array, the tool chain array is synchronously transferred to the newly loaded auxiliary tool plug-in.

[0065] In this embodiment, when the previous auxiliary tool plug-in automatically loads the next auxiliary tool plug-in, it will pass the tool chain array to the newly loaded auxiliary tool plug-in to ensure a continuous workflow. For example, when the user finishes using the first auxiliary tool plug-in, the first auxiliary tool plug-in will automatically load the second auxiliary tool plug-in and pass the tool chain array to the second auxiliary tool chain plug-in at the same time, and load in this order until all the auxiliary tool plug-ins in the tool chain array are loaded and used in order.

[0066] In some embodiments, the step of the next auxiliary tool plug-in receiving the output file path of the previous auxiliary tool plug-in, and obtaining the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool includes:

[0067] S320: When the previous auxiliary tool plug-in completes processing, the next auxiliary tool plug-in captures and reads the output file path of the previous auxiliary tool plug-in;

[0068] S330: Set the output file path of the previous auxiliary tool plug-in as an input parameter of the next auxiliary tool plug-in, and the next auxiliary tool plug-in uses the input parameter as an input file for subsequent processing.

[0069] In this embodiment, when the previous auxiliary tool plug-in completes processing, the next auxiliary tool plug-in captures and reads the output file path of the previous auxiliary tool plug-in, and uses the input parameters as the input file for subsequent processing. Figures 9 to 11 As shown in the figure, taking the output file generated by the Ts generation tool as the input of the Napi generation tool as an example, when the Ts tool loads the Napi tool, it will not only pass the toolchain array, but also the path of the Ts tool output file. The Napi tool will receive the output file path of the Ts tool and process it as an input parameter.

[0070] In some embodiments, when the previous auxiliary tool plug-in outputs an event or signal after completing processing, the next auxiliary tool plug-in responds to the event or signal output by the previous auxiliary tool plug-in, captures and reads the output file path of the previous auxiliary tool plug-in. After the next auxiliary tool plug-in receives the output file path, it automatically sets the path as an input parameter, wherein a corresponding input field is set in the configuration inside the next auxiliary tool plug-in. After the configuration of the next auxiliary tool plug-in is completed, it can be automatically started and use the set path as the input file for subsequent processing, such as Fig.10 and Fig.11 shown.

[0071] In some embodiments, Fig.12As shown, the present invention provides a development tool acquisition device, which includes: an acquisition unit, a tool chain array synthesis unit and a tool chain generation unit. The acquisition unit is used to acquire auxiliary tool plug-ins; the tool chain array synthesis unit is used to select several auxiliary tool plug-ins to synthesize a tool chain array when a tool chain needs to be generated; the tool chain generation unit is used to load auxiliary tool plug-ins in sequence according to the tool chain array until all auxiliary tool plug-ins are loaded in sequence to generate a tool chain; when there is a dependency relationship between two auxiliary tool plug-ins in the previous and subsequent order, the next auxiliary tool plug-in receives the output file path of the previous auxiliary tool plug-in, obtains the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool plug-in, and uses the output file of the previous auxiliary tool plug-in as the input file.

[0072] In some embodiments, the present invention provides a computer device, which may be a terminal. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal via a network connection. The memory stores a computer program, and the processor is used to implement the following steps when executing the computer program:

[0073] Obtain auxiliary tool plug-ins; wherein the auxiliary tool plug-ins include Api scanning tools, Gn conversion tools, Service generation tools, Ts generation tools, and Napi generation tools;

[0074] When a tool chain needs to be generated, select several auxiliary tool plug-ins and synthesize a tool chain array;

[0075] The auxiliary tool plug-ins are loaded in sequence according to the toolchain array order until all auxiliary tool plug-ins are loaded in order to generate a toolchain.

[0076] In some embodiments, the present invention provides a storage medium having a computer program stored thereon, wherein the computer program is used to implement the steps in the following method when executed by a processor:

[0077] Obtain auxiliary tool plug-ins; wherein the auxiliary tool plug-ins include Api scanning tools, Gn conversion tools, Service generation tools, Ts generation tools, and Napi generation tools;

[0078] When a tool chain needs to be generated, select several auxiliary tool plug-ins and synthesize a tool chain array;

[0079] The auxiliary tool plug-ins are loaded in sequence according to the toolchain array order until all auxiliary tool plug-ins are loaded in order to generate a toolchain.

[0080] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided by the present invention can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0081] In summary, the development tool acquisition method, device, computer equipment and storage medium provided by the present invention have the following beneficial effects:

[0082] By pre-acquiring the required auxiliary tool plug-ins, integrating the acquired auxiliary tool plug-ins into a unified plug-in, and integrating the downloaded auxiliary tool plug-ins into one plug-in, there is no need to download and configure each tool separately, which simplifies the plug-in management process, facilitates access to various development tools, prevents confusion caused by a large number of plug-ins, and improves development efficiency;

[0083] Users can combine various tools according to customized usage scenarios, use these auxiliary tool plug-ins to form any tool chain, establish automated dependencies between tool chains, and form a north-south tool chain that suits them. This allows users to choose the right tool combination based on their own needs and habits, reduce unnecessary operations and switching, and avoid configuration errors, further improving development efficiency.

[0084] It should be understood that the application of the present invention is not limited to the above examples. For ordinary technicians in this field, improvements or changes can be made based on the above description. All these improvements and changes should fall within the scope of protection of the claims attached to the present invention.

Claims

1. A method for obtaining a development tool, It is characterized in that include: Get auxiliary tool plug-ins for system development; When a tool chain needs to be generated, select several auxiliary tool plug-ins and synthesize a tool chain array; Load auxiliary tool plug-ins in sequence according to the toolchain array order until all auxiliary tool plug-ins are loaded in order to generate a toolchain; Among them, when there is a dependency relationship between two auxiliary tool plug-ins in the previous and subsequent order, the next auxiliary tool plug-in receives the output file path of the previous auxiliary tool plug-in, and obtains the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool plug-in, and uses the output file of the previous auxiliary tool plug-in as the input file.

2. The method for acquiring development tools according to claim 1, It is characterized in that The step of obtaining the auxiliary tool plug-in includes: Check whether the current environment has installed the required auxiliary tool plug-in. If the current environment has not installed the corresponding auxiliary tool plug-in, download and install the corresponding auxiliary tool plug-in.

3. The method for acquiring development tools according to claim 1, It is characterized in that The step of sequentially loading the auxiliary tool plug-ins according to the tool chain array sequence until all the auxiliary tool plug-ins are loaded in sequence to generate the tool chain specifically includes: Load the first auxiliary tool plugin according to the order of the toolchain array; The first auxiliary tool plug-in loads the next auxiliary tool plug-in in the toolchain array until all auxiliary tool plug-ins are loaded in order.

4. The method for acquiring development tools according to claim 1, It is characterized in that The step of sequentially loading auxiliary tool plug-ins according to the toolchain array sequence includes: When the previous auxiliary tool plug-in automatically loads the next auxiliary tool plug-in in the tool chain array, the tool chain array is synchronously passed to the newly loaded auxiliary tool plug-in.

5. The method for acquiring development tools according to claim 1, It is characterized in that The step of the next auxiliary tool plug-in receiving the output file path of the previous auxiliary tool plug-in and obtaining the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool includes: When the previous auxiliary tool plug-in completes processing, the next auxiliary tool plug-in captures and reads the output file path of the previous auxiliary tool plug-in; The output file path of the previous auxiliary tool plug-in is set as the input parameter of the next auxiliary tool plug-in, and the next auxiliary tool plug-in uses the input parameter as an input file for subsequent processing.

6. The method for acquiring development tools according to claim 5, It is characterized in that When the previous auxiliary tool plug-in completes processing and outputs an event or signal, the next auxiliary tool plug-in responds to the event or signal output by the previous auxiliary tool plug-in and captures and reads the output file path of the previous auxiliary tool plug-in.

7. The method for acquiring development tools according to claim 1, It is characterized in that The auxiliary tool plug-ins include Api scanning tool, Gn conversion tool, Service generation tool, Ts generation tool, and Napi generation tool.

8. A development tool acquisition device, It is characterized in that include: An acquisition unit, used to acquire an auxiliary tool plug-in; A tool chain array synthesis unit is used to select several auxiliary tool plug-ins to synthesize a tool chain array when a tool chain needs to be generated; A tool chain generation unit is used to load auxiliary tool plug-ins in sequence according to the tool chain array order until all auxiliary tool plug-ins are loaded in sequence to generate a tool chain; wherein, when there is a dependency relationship between two auxiliary tool plug-ins in the previous and subsequent order, the next auxiliary tool plug-in receives the output file path of the previous auxiliary tool plug-in, obtains the output file of the previous auxiliary tool plug-in according to the output file path of the previous auxiliary tool plug-in, and uses the output file of the previous auxiliary tool plug-in as the input file.

9. A computer device comprising a memory and a processor, It is characterized in that The memory stores a computer program, and the processor executes the computer program to implement the steps in the development tool acquisition method according to any one of claims 1 to 7.

10. A storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, it is used to implement the steps in the development tool acquisition method according to any one of claims 1 to 7.

Images