Compiled file generation method, device and system and storage medium

Abstract

The invention discloses a compiling file generation method, device and system and a storage medium. The method comprises the steps of pulling target compiling metadata from a conversion platform according to a target compiling event identifier; by executing a compiling configuration script, converting the target compiling metadata into a compiling event script, and adding the compiling event script into a compiling file corresponding to the target compiling event identifier; wherein preset compiling metadata corresponding to at least one preset compiling event identifier is stored in the conversion platform, and at least one event attribute parameter data corresponding to the target compiling event identifier is defined in the target compiling metadata; compiling configuration data corresponding to the event attribute parameter data are recorded in the compiling configuration script. According to the embodiment of the invention, the problem that the compiled file needs to be compiled manually is solved, and the generation efficiency of the compiled file is improved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of computer technology, and in particular, to a method, device, system, and storage medium for generating a compilation file. Background Art

[0002] Currently, when generating a compilation file, it is necessary to rely on developers to manually write the compilation file according to the compilation requirements, resulting in low efficiency in generating the compilation file and a relatively high error rate of the compilation file. Summary of the Invention

[0003] The present invention provides a method, device, system, and storage medium for generating a compilation file to solve the problem that the compilation file needs to be manually written, improve the efficiency of generating the compilation file, and reduce the error rate of the compilation file.

[0004] In a first aspect, an embodiment of the present invention provides a method for generating a compilation file, the method comprising:

[0005] Pulling target compilation metadata from a conversion platform according to a target compilation event identifier;

[0006] Converting the target compilation metadata into a compilation event script by executing a compilation configuration script, and adding the compilation event script to a compilation file corresponding to the target compilation event identifier;

[0007] Wherein, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, the target compilation metadata defines at least one event attribute parameter data corresponding to the target compilation event identifier, and the compilation configuration script records compilation configuration data corresponding to the event attribute parameter data.

[0008] In a second aspect, an embodiment of the present invention further provides a device for generating a compilation file, the device comprising:

[0009] A target compilation metadata pulling module, configured to pull target compilation metadata from a conversion platform according to a target compilation event identifier;

[0010] A compilation file determining module, configured to convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to a compilation file corresponding to the target compilation event identifier;

[0011] Wherein, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, the target compilation metadata defines at least one event attribute parameter data corresponding to the target compilation event identifier, and the compilation configuration script records compilation configuration data corresponding to the event attribute parameter data.

[0012] In a third aspect, an embodiment of the present invention further provides a system for generating a compilation file, which includes: a compilation server and a conversion platform that are communicatively connected;

[0013] Among them, the compilation server is used to pull target compilation metadata from the conversion platform according to the target compilation event identifier, and convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier;

[0014] Among them, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier. At least one event attribute parameter data corresponding to the target compilation event identifier is defined in the target compilation metadata, and compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script.

[0015] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium storing computer instructions for causing a processor to implement the method for generating a compilation file according to any embodiment of the present invention when executed.

[0016] The technical solution of the embodiment of the present invention solves the problem that compilation files need to be written manually by pulling target compilation metadata from the conversion platform according to the target compilation event identifier, converting the target compilation metadata into a compilation event script by executing a compilation configuration script, and adding the compilation event script to the compilation file corresponding to the target compilation event identifier. Among them, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier. At least one event attribute parameter data corresponding to the target compilation event identifier is defined in the target compilation metadata, and compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script, improving the generation efficiency of compilation files and reducing the error rate of compilation files. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In combination with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages and aspects of the embodiments of the present invention will become more apparent. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the original elements and elements are not necessarily drawn to scale.

[0018] Figure 1 It is a flowchart of a method for generating a compilation file provided by an embodiment of the present invention;

[0019] Figure 2A data architecture diagram of compilation identification data provided by an embodiment of the present invention;

[0020] Figure 3 A script structure diagram of a compilation configuration script provided by an embodiment of the present invention;

[0021] Figure 4 A script structure diagram of a compilation event script provided by an embodiment of the present invention;

[0022] Figure 5 A flowchart of another method for generating a compilation file provided by an embodiment of the present invention;

[0023] Figure 6 A schematic structural diagram of a device for generating a compilation file provided by an embodiment of the present invention;

[0024] Figure 7 A schematic structural diagram of a system for generating a compilation file provided by an embodiment of the present invention;

[0025] Figure 8 A schematic structural diagram of a compilation server provided by an embodiment of the present invention. Detailed implementation manners

[0026] Embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Instead, these embodiments are provided to more thoroughly and completely understand the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not used to limit the protection scope of the present invention.

[0027] It should be understood that the steps recited in the method embodiments of the present invention can be executed in a different order and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this regard.

[0028] The term "including" and its variations used herein are open-ended, i.e., "including but not limited to". The term "based on" is "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0029] It should be noted that the concepts such as "first" and "second" mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependent relationships.

[0030] It should be noted that the modifications of "one" and "multiple" mentioned in the present invention are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly specified in the context, it should be understood as "one or more".

[0031] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only for illustrative purposes and are not used to limit the scope of these messages or information.

[0032] It can be understood that before using the technical solutions disclosed in the embodiments of the present invention, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present invention should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0033] For example, when responding to receiving an active request from the user, a prompt message is sent to the user to clearly prompt the user that the operation requested by the user will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, an application program, a server, or a storage medium that executes the technical solution of the present invention according to the prompt message.

[0034] As an optional but non-limiting implementation manner, the manner of sending a prompt message to the user in response to receiving an active request from the user can be, for example, in the form of a pop-up window, and the prompt message can be presented in text in the pop-up window. In addition, the pop-up window can also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0035] It can be understood that the above process of notifying and obtaining the user's authorization is only illustrative and does not limit the implementation manner of the present invention, and other manners that meet relevant laws and regulations can also be applied to the implementation manner of the present invention.

[0036] Figure 1 The flowchart of a method for generating a compilation file provided for an embodiment of the present invention. This embodiment is applicable to the situation where a compilation server automatically generates a compilation file. This method can be executed by a device for generating a compilation file, and the device for generating a compilation file can be implemented in the form of hardware and / or software, and the device for generating a compilation file can be configured in a compilation server. As Figure 1 shown, the method includes:

[0037] S110. Pull the target compilation metadata from the conversion platform according to the target compilation event identifier.

[0038] Specifically, the target compilation event identifier is used to uniquely identify the compilation requirement event. Exemplarily, the target compilation event identifier may be composed of at least one of letters, numbers, uppercase letters, lowercase letters, and special characters. The composition method of the target compilation event identifier is not limited here, and it can be specifically customized according to actual needs.

[0039] In an alternative embodiment, the compilation requirement event is used to represent pulling the target event data during the operation of the target program. Exemplarily, the compilation requirement event may be pulling the response data of the target program. For example, the response data may be the time-consuming of timeline zooming and frame extraction. The compilation requirement event is not limited here, and it can be specifically customized according to actual needs.

[0040] In this embodiment, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, and at least one event attribute parameter data corresponding to the target compilation event identifier is defined in the target compilation metadata.

[0041] Specifically, the event attribute parameter data includes the attribute parameter data of the event attribute parameters related to the compilation requirement event. For example, assuming that the compilation requirement event is to pull the time-consuming of timeline zooming and frame extraction of the target program, the event attribute parameters related to the time-consuming of timeline zooming and frame extraction include, but are not limited to, the rendering time-consuming of the audio waveform diagram, the rendering time-consuming of the first frame of the player, the total zooming time-consuming, the rendering time-consuming of the video thumbnail, the zooming operation, and the zooming method, etc. Exemplarily, the attribute parameter data includes, but is not limited to, the attribute parameter identifier, the pulling time period, the attribute parameter type, etc. Among them, the attribute parameter identifier is used to uniquely identify the event attribute parameter, the pulling time period is used to represent the time period for pulling the target event data, and the attribute parameter type is used to represent the data type corresponding to the event attribute parameter.

[0042] Exemplarily, the attribute parameter identifier may be composed of at least one of letters, numbers, uppercase letters, lowercase letters, and special characters. The attribute parameter type corresponding to the rendering time-consuming of the audio waveform diagram is integer type, and the attribute parameter type corresponding to the zooming operation is string type. The attribute parameter identifier and the attribute parameter type are not limited here, and they can be specifically customized according to actual needs.

[0043] In an alternative embodiment, at least one preset compilation event identifier and corresponding preset compilation metadata are stored in the conversion platform. Correspondingly, pulling the target compilation metadata from the conversion platform according to the target compilation event identifier includes: sending a metadata pull request to the conversion platform according to the preset compilation event identifier, and receiving the target compilation metadata sent by the conversion platform according to the metadata pull request.

[0044] In another alternative embodiment, pulling the target compilation metadata from the conversion platform according to the target compilation event identifier includes: querying a target platform conversion identifier corresponding to the target compilation event identifier from a conversion mapping list; sending a metadata pull request to the conversion platform according to the target platform conversion identifier, and receiving the target compilation metadata sent by the conversion platform according to the metadata pull request.

[0045] In this embodiment, at least one preset compilation event identifier and corresponding preset platform conversion identifiers are stored in the conversion mapping list, and at least one preset platform conversion identifier and corresponding preset compilation metadata are stored in the conversion platform.

[0046] Specifically, the preset platform conversion identifier is used to uniquely identify the preset compilation metadata. Exemplarily, the preset platform conversion identifier can be composed of at least one of letters, numbers, capital letters, lowercase letters, and special characters. The composition method of the preset platform conversion identifier is not limited herein, and can be specifically customized according to actual needs.

[0047] Specifically, the metadata pull request includes at least the target platform conversion identifier. The conversion platform obtains the target platform conversion identifier in the received metadata pull request, searches for the target compilation metadata corresponding to the target platform conversion identifier from the local storage space, and sends the target compilation metadata to the compilation server.

[0048] Based on the above embodiments, optionally, before pulling the target compilation metadata from the conversion platform according to the target compilation event identifier, the method further includes: obtaining compilation list data corresponding to the preset compilation event identifier; sending the compilation list data to the conversion platform, so that the conversion platform converts the received compilation list data into JSON format compilation identifier data; wherein, the compilation identifier data includes a preset platform conversion identifier and preset compilation metadata; in response to receiving the preset platform conversion identifier sent by the conversion platform, storing the preset compilation event identifier and the preset platform conversion identifier in the conversion mapping list correspondingly.

[0049] Specifically, the compiled list data includes at least one event attribute parameter data in the list data format.

[0050] Figure 2 FIG. is a data architecture diagram of the compiled identification data provided by an embodiment of the present invention. Specifically, the preset platform conversion identifier in the compiled identification data includes the identifier values "200" and "SUCCESS" corresponding to "status" and "message" respectively. The preset compilation metadata in the compiled identification data includes Figure 2 the data content in "{}" corresponding to "data" in. Among them, the data content in the two "{}" corresponding to the array params represents the event attribute parameter data, and the data content outside the array params represents the event parameter data related to the compilation requirement event.

[0051] Specifically, Figure 2 The shown event attribute parameter data includes the attribute parameter identifier and the attribute parameter type of the time attribute parameter. Figure 2 "audio_waveform_time" in represents the attribute parameter identifier corresponding to the rendering time of the audio waveform diagram, "player_first_frame_time" represents the attribute parameter identifier corresponding to the rendering time of the first frame of the player, and "zoom_track_time" represents the time-consuming of frame extraction for timeline zooming.

[0052] The advantage of such a setting is that on the one hand, the definition of the compilation requirement event is realized through the compiled list data, reducing the difficulty of defining the compilation requirement event. On the other hand, the conversion platform is adopted to implement data conversion, which not only improves the conversion efficiency of the compilation metadata but also reduces the occupation of the local storage space of the compilation server by the compilation metadata.

[0053] S120. By executing the compilation configuration script, convert the target compilation metadata into a compilation event script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier.

[0054] In this embodiment, the compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script. Specifically, the compilation configuration script is used to convert the target compilation metadata of the preset data type into a compilation event script of the target event data type, where the preset data type is different from the target event data type, and the target event data type can support the compilation call of the compilation client. The combination form of the preset data type and the target event data type can be custom-set according to actual needs.

[0055] In an alternative embodiment, the preset data type is the JSON format, and the target event data type is the C++ data format.

[0056] In an alternative embodiment, the compilation configuration data includes constructor configuration data and assignment configuration data; wherein, the constructor configuration data is used to define adding a constructor in the compilation event script according to the attribute parameter identifier in the event attribute parameter data, and the assignment configuration data is used to define adding an assignment compilation statement in the compilation event script according to the attribute parameter identifier.

[0057] In this embodiment, the compilation file is used to pull target event data corresponding to each of the event attribute parameter data during the running of the target program. Specifically, the constructor is used to define the initialization state when an object of a class is created, and the assignment compilation statement is used to assign the event attribute parameter value corresponding to each attribute parameter identifier in the pulled target event data to the parameter array corresponding to the attribute parameter identifier.

[0058] In an alternative embodiment, the assignment configuration data includes duplicate assignment check configuration data, and the duplicate assignment check configuration data is used to define adding a duplicate assignment check compilation statement in the assignment compilation statement. Specifically, the duplicate assignment check compilation statement is used to check whether there is a duplicate assignment in the parameter array corresponding to the attribute parameter identifier.

[0059] Figure 3 This is a script structure diagram of a compilation configuration script provided by an embodiment of the present invention. Figure 3 Taking Figure 2 the preset compilation metadata therein, and taking the target data type corresponding to the compilation event script as the C++ data format as an example. Specifically, the compilation configuration script includes constructor compilation data and assignment compilation data, and the assignment compilation data includes duplicate assignment check compilation data.

[0060] Figure 4 This is a script structure diagram of a compilation event script provided by an embodiment of the present invention. Figure 4 Taking Figure 3 the compilation configuration script therein as an example. Specifically, the compilation configuration script includes a constructor and two assignment compilation statements, and the assignment compilation statement includes a duplicate assignment check compilation statement.

[0061] It should be noted that the Figure 2 , Figure 3 , Figure 4 shown in the embodiments of the present invention are only used for exemplary explanation of the compilation identification data, the compilation configuration script, and the compilation event script, and do not limit the specific statement compilation content in the compilation identification data, the compilation configuration script, and the compilation event script. It can be understood that any compilation identification data, compilation configuration script, and compilation event script that can achieve the above functions and effects are within the protection scope of the present application.

[0062] In the technical solution of this embodiment, by pulling target compilation metadata from the conversion platform according to the target compilation event identifier, and by executing a compilation configuration script, converting the target compilation metadata into a compilation event script, and adding the compilation event script to the compilation file corresponding to the target compilation event identifier, wherein the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, the target compilation metadata defines at least one event attribute parameter data corresponding to the target compilation event identifier, and the compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script, the problem that compilation files need to be written manually is solved, the generation efficiency of compilation files is improved, and the error rate of compilation files is reduced.

[0063] Figure 5 As shown in the flowchart of another method for generating a compilation file provided by an embodiment of the present invention, this embodiment further refines the method for generating a compilation file in the above embodiment. As Figure 5 shown, the method includes:

[0064] S210. Pull target compilation metadata from the conversion platform according to the target compilation event identifier.

[0065] S220. By executing a compilation configuration script, convert the target compilation metadata into a compilation event script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier.

[0066] S210 - S220 in this embodiment corresponds to S110 - S120 shown in the above embodiment Figure 1 and is the same or similar, and this embodiment will not be elaborated here.

[0067] On the basis of the above embodiment, optionally, before adding the compilation event script to the compilation file corresponding to the target compilation event identifier, the method further includes: if there is a compilation event script corresponding to the target compilation event identifier in the compilation file corresponding to the target compilation event identifier, then delete the compilation event script from the compilation file.

[0068] Specifically, the compilation file stores compilation event scripts respectively corresponding to at least one preset compilation event identifier.

[0069] The advantage of such a setting is that, on the one hand, it enables the compilation event script to support repeated request generation, and on the other hand, it avoids the problem of excessive number of compilation files caused by storing the compilation event script in a single file, thereby reducing the calling difficulty of the compilation file.

[0070] S230. Obtain the compilation file identifier and the call compilation event identifier in the compilation file call request corresponding to the target program.

[0071] Specifically, the compilation file call request is generated by the terminal device running the target program. Exemplarily, the terminal device can be a compilation server or a service front-end device.

[0072] Specifically, a call compilation statement for calling a compilation file is added to the program compilation statement of the target program. During the running process of the target program, when the call compilation statement is executed, a compilation file call request is generated according to the compilation file identifier and the target compilation event identifier in the call compilation statement.

[0073] Specifically, the compilation file identifier is used to uniquely identify the compilation file. Exemplarily, the compilation file identifier can be composed of at least one of letters, numbers, capital letters, lowercase letters, and special characters. There is no limitation on the composition method of the compilation file identifier here, and it can be customized according to actual needs.

[0074] S240. Obtain the target compilation file corresponding to the compilation file identifier, and execute the compilation event script corresponding to the target compilation event identifier in the target compilation file.

[0075] Specifically, the compilation server stores at least one compilation file identifier and the preset compilation files respectively corresponding to each compilation file identifier, and the target compilation file records the compilation event scripts respectively corresponding to at least one preset compilation event identifier.

[0076] S250. Generate an execution error message according to the execution error data of the compilation event script, and output and display the execution error message.

[0077] In this embodiment, the execution error data includes duplicate assignment error data and / or pull attribute parameter error data, and the pull attribute parameter error data is determined according to the pull attribute parameters corresponding to the pulled target event data.

[0078] In an optional embodiment, the duplicate assignment error data is generated when the event attribute parameter value in the target event data is repeatedly assigned to the parameter array corresponding to the attribute parameter identifier during the execution of the compilation event script.

[0079] In an optional embodiment, the pull attribute parameters include at least one of the number of pull identifiers, the pull parameter identifiers corresponding to each event attribute parameter data, and the pull parameter types.

[0080] Specifically, the pull identifier quantity can be used to characterize the identifier quantity of the pull parameter identifiers corresponding to the event attribute parameter values in the target event data, and the compilation identifier quantity can be used to characterize the identifier quantity of the attribute parameter identifiers defined in the compilation event script. In one embodiment, if there are at least one parameter arrays corresponding to the attribute parameter identifiers defined in the compilation event script that are not assigned values, it indicates that the pull identifier quantity corresponding to the target event data is less than the compilation identifier quantity corresponding to the compilation event script, and the compilation event script automatically outputs pull attribute parameter error data during operation.

[0081] Specifically, the event attribute parameter values include pull parameter identifiers and pull parameter types. In one embodiment, if the pull parameter identifier in the target event data is different from the attribute parameter identifier defined correspondingly in the compilation event script, the compilation event script automatically outputs pull attribute parameter error data during operation; if the pull parameter type in the target event data is different from the attribute parameter type defined correspondingly in the compilation event script, the compilation event script automatically outputs pull attribute parameter error data during operation.

[0082] Taking Figure 4 the compilation event script in Figure 4 as an example, the attribute parameter type is defined as "int64" in the assignment compilation statement corresponding to "audio_waveform_time". Assuming that the pull parameter type corresponding to "audio_waveform_time" in the target event data is of the hash type, the compilation event script automatically outputs pull attribute parameter error data during operation.

[0083] Exemplarily, the output display forms of the above execution error messages include but are not limited to text display, sound playback, indicator light output, etc. The embodiments of the present invention do not limit the output display forms of the execution error messages, and can be specifically customized according to actual requirements.

[0084] For example, the text display can be "The xx attribute parameter has been reassigned" or "The assignment result of the xx attribute parameter is missing", etc. The sound playback can be voice playback or beep playback. For example, the voice playback content can be the content of the above text display, and the beep playback can output a beep according to a preset volume and / or preset pitch. Exemplarily, the preset volume can be 5dB. Since the pitch is determined by the vibration frequency of the sound, the preset pitch can be the sound pitch when the vibration frequency reaches 100Hz. For example, a specific indicator light color and / or a specific indicator light flashing frequency can also be used for error prompting.

[0085] The technical solution of this embodiment is to obtain the compilation file identifier and the call compilation event identifier in the compilation file call request corresponding to the target program, obtain the target compilation file corresponding to the compilation file identifier, and execute the compilation event script corresponding to the target compilation event identifier in the target compilation file. According to the execution error data of the compilation event script, an execution error message is generated and the execution error message is output and displayed. Among them, the execution error data includes duplicate assignment error data and / or pull attribute parameter error data, and the pull attribute parameter error data is determined according to the pull attribute parameter corresponding to the pulled target event data. This solves the problem that traditional compilation files cannot complete their own running checks, further guarantees the quality of the generated compilation files, avoids bringing the incorrect target event data generated by the compilation file to the compilation analysis platform, and ensures the data quality of the target event data.

[0086] The following is an embodiment of the device for generating a compilation file provided by an embodiment of the present invention. This device and the method for generating a compilation file in the above embodiment belong to the same inventive concept. For the details not described in detail in the embodiment of the device for generating a compilation file, reference may be made to the content of the method for generating a compilation file in the above embodiment.

[0087] Figure 6 The following is a schematic structural diagram of a device for generating a compilation file provided by an embodiment of the present invention. As Figure 6 shown, the device includes: a target compilation metadata pulling module 310 and a compilation file determining module 320.

[0088] Among them, the target compilation metadata pulling module 310 is used to pull the target compilation metadata from the conversion platform according to the target compilation event identifier;

[0089] The compilation file determining module 320 is used to convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier;

[0090] Among them, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, at least one event attribute parameter data corresponding to the target compilation event identifier is defined in the target compilation metadata, and compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script.

[0091] In the technical solution of this embodiment, by pulling target compilation metadata from a conversion platform according to a target compilation event identifier, and through executing a compilation configuration script, converting the target compilation metadata into a compilation event script, and adding the compilation event script to a compilation file corresponding to the target compilation event identifier. Among them, preset compilation metadata corresponding to at least one preset compilation event identifier is stored in the conversion platform, at least one event attribute parameter data corresponding to the target compilation event identifier is defined in the target compilation metadata, and compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script. This solves the problem that compilation files need to be written manually, improves the generation efficiency of compilation files, and reduces the error rate of compilation files.

[0092] In an alternative embodiment, the compilation configuration data includes constructor configuration data and assignment configuration data; wherein, the constructor configuration data is used to define adding a constructor in the compilation event script according to an attribute parameter identifier in the event attribute parameter data, and the assignment configuration data is used to define adding an assignment compilation statement in the compilation event script according to the attribute parameter identifier.

[0093] Among them, the compilation file is used to pull target event data corresponding to each of the event attribute parameter data during the running of the target program.

[0094] In an alternative embodiment, the assignment configuration data includes duplicate assignment check configuration data, and the duplicate assignment check configuration data is used to define adding a duplicate assignment check compilation statement in the assignment compilation statement.

[0095] In an alternative embodiment, the device further includes:

[0096] An execution error message output module, configured to obtain a compilation file identifier and a called compilation event identifier in a compilation file call request corresponding to a target program;

[0097] Obtain a target compilation file corresponding to the compilation file identifier, and execute the compilation event script corresponding to the target compilation event identifier in the target compilation file;

[0098] Generate an execution error message according to the execution error data of the compilation event script, and output and display the execution error message;

[0099] Among them, the execution error data includes duplicate assignment error data and / or pulled attribute parameter error data, and the pulled attribute parameter error data is determined according to the pulled attribute parameter corresponding to the pulled target event data.

[0100] In an alternative embodiment, the pull attribute parameter includes at least one of the number of pull identifiers, the pull parameter identifier corresponding to each event attribute parameter data, and the pull parameter type.

[0101] In an alternative embodiment, the target compilation metadata pull module 310 is specifically configured to:

[0102] Query the target platform conversion identifier corresponding to the target compilation event identifier from the conversion mapping list;

[0103] According to the target platform conversion identifier, send a metadata pull request to the conversion platform, and receive the target compilation metadata sent by the conversion platform according to the metadata pull request;

[0104] Wherein, at least one preset compilation event identifier and the corresponding preset platform conversion identifier of each preset compilation event identifier are stored in the conversion mapping list, and at least one preset platform conversion identifier and the corresponding preset compilation metadata of each preset platform conversion identifier are stored in the conversion platform.

[0105] In an alternative embodiment, the apparatus further includes:

[0106] A conversion mapping list determination module, configured to obtain the compilation list data corresponding to the preset compilation event identifier before pulling the target compilation metadata from the conversion platform according to the target compilation event identifier;

[0107] Send the compilation list data to the conversion platform, so that the conversion platform converts the received compilation list data into compilation identifier data in JSON format; wherein, the compilation identifier data includes a preset platform conversion identifier and preset compilation metadata;

[0108] In response to receiving the preset platform conversion identifier sent by the conversion platform, store the corresponding preset compilation event identifier and the preset platform conversion identifier in the conversion mapping list.

[0109] In an alternative embodiment, the apparatus further includes:

[0110] A compilation event script deletion module, configured to delete the compilation event script from the compilation file if there is a compilation event script corresponding to the target compilation event identifier in the compilation file before adding the compilation event script to the compilation file corresponding to the target compilation event identifier.

[0111] The compilation file generation apparatus provided by the embodiments of the present invention can execute the compilation file generation method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0112] Figure 7 The following is a schematic structural diagram of a compilation file generation system provided by an embodiment of the present invention. As Figure 7 shown, the compilation file generation system 400 includes: a compilation server 410 and a conversion platform 420 that are communicatively connected;

[0113] Among them, the compilation server 410 is used to pull target compilation metadata from the conversion platform 420 according to the target compilation event identifier, and convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier;

[0114] Among them, the conversion platform 420 stores preset compilation metadata corresponding to at least one preset compilation event identifier respectively. At least one event attribute parameter data corresponding to the target compilation event identifier is defined in the target compilation metadata, and compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script.

[0115] In an alternative embodiment, the compilation server 410 is specifically configured to: query a target platform conversion identifier corresponding to the target compilation event identifier from a conversion mapping list, and send a metadata pull request to the conversion platform 420 according to the target platform conversion identifier, and receive the target compilation metadata sent by the conversion platform 420 according to the metadata pull request; the conversion platform 420 is used to send the target compilation metadata corresponding to the target platform conversion identifier in the received metadata pull request to the compilation server 410; among them, at least one preset compilation event identifier and preset platform conversion identifiers corresponding to the respective preset compilation event identifiers are stored in the conversion mapping list, and at least one preset platform conversion identifier and preset compilation metadata corresponding to the respective preset platform conversion identifiers are stored in the conversion platform 420.

[0116] In an alternative embodiment, the compilation server 410 is further configured to: send compilation list data corresponding to a preset compilation event identifier to the conversion platform 420, and store the preset compilation event identifier and the preset platform conversion identifier sent by the received conversion platform 420 in the conversion mapping list correspondingly; the conversion platform 420 is used to convert the received compilation list data into compilation identifier data in JSON format, and send the preset platform conversion identifier in the compilation identifier data to the compilation server 410.

[0117] Next, refer to Figure 8, which shows a schematic structural diagram of the compilation server 410 suitable for implementing the embodiments of the present invention.

[0118] The device types of the compilation server 410 in the embodiments of the present invention may include but are not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Computers), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The shown compilation server 410 is merely an example and should not impose any limitations on the functions and usage scope of the embodiments of the present invention.

[0119] As Figure 8 shown, the compilation server 410 may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 411, which may perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 412 or the program loaded from the storage device 415 into the random access memory (RAM) 413. In the RAM 413, various programs and data required for the operation of the compilation server 410 are also stored. The processing device 411, the ROM 412, and the RAM 413 are connected to each other through a bus 414. The input / output (I / O) interface 415 is also connected to the bus 414.

[0120] Generally, the following devices may be connected to the I / O interface 415: an input device 416 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 417 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 418 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 419. The communication device 419 may allow the compilation server 410 to communicate with other devices wirelessly or wiredly to exchange data. Although Figure 8 the shown compilation server 410 has various devices, it should be understood that it is not required to implement or have all the shown devices. More or fewer devices may be alternatively implemented or had.

[0121] Specifically, according to the embodiments of the present invention, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, the embodiments of the present invention include a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from the network through the communication device 419, or installed from the storage device 418, or installed from the ROM 412. When the computer program is executed by the processing device 411, the above-mentioned functions defined in the methods of the embodiments of the present invention are executed.

[0122] It should be noted that the above-mentioned computer-readable medium of the present invention can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present invention, the computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, in which the computer-readable program code is carried. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, and this computer-readable signal medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted by any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0123] In some embodiments, the client and the server can communicate using any currently known or future-developed network protocol such as HTTP (HyperText Transfer Protocol), and can be interconnected with digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed networks.

[0124] The above-mentioned computer-readable medium can be included in the above-mentioned electronic device; or it can exist separately without being assembled into the electronic device.

[0125] The above computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: obtain at least two Internet protocol addresses; send a node evaluation request including the at least two Internet protocol addresses to a node evaluation device, wherein the node evaluation device selects an Internet protocol address from the at least two Internet protocol addresses and returns it; receive the Internet protocol address returned by the node evaluation device; wherein the obtained Internet protocol addresses indicate edge nodes in a content delivery network.

[0126] Alternatively, the above computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: receive a node evaluation request including at least two Internet protocol addresses; select an Internet protocol address from the at least two Internet protocol addresses; return the selected Internet protocol address; wherein the received Internet protocol addresses indicate edge nodes in a content delivery network.

[0127] Computer program code for performing the operations of the present invention may be written in one or more programming languages or combinations thereof. The programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0128] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a portion of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks may occur in a different order than noted in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0129] The units described in the embodiments of the present invention can be implemented in software or in hardware. Among them, the name of the unit does not constitute a limitation on the unit itself in some cases. For example, the first acquisition unit can also be described as "the unit for acquiring at least two Internet protocol addresses".

[0130] The functions described above herein can be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), and so on.

[0131] In the context of the present invention, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0132] According to one or more embodiments of the present invention, Example 1 provides a method for generating a compilation file, the method including:

[0133] Pull the target compilation metadata from the conversion platform according to the target compilation event identifier;

[0134] Convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier;

[0135] Among them, preset compilation metadata corresponding to at least one preset compilation event identifier is stored in the conversion platform, at least one event attribute parameter data corresponding to the target compilation event identifier is defined in the target compilation metadata, and compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script.

[0136] According to one or more embodiments of the present invention, in Example 2, according to the method described in Example 1, the compilation configuration data includes constructor configuration data and assignment configuration data; wherein, the constructor configuration data is used to define adding a constructor in the compilation event script according to the attribute parameter identifier in the event attribute parameter data, and the assignment configuration data is used to define adding an assignment compilation statement in the compilation event script according to the attribute parameter identifier;

[0137] Among them, the compilation file is used to pull the target event data corresponding to each of the event attribute parameter data during the running of the target program.

[0138] According to one or more embodiments of the present invention, in Example 3, according to the method described in Example 2, the assignment configuration data includes duplicate assignment check configuration data, and the duplicate assignment check configuration data is used to define adding a duplicate assignment check compilation statement in the assignment compilation statement.

[0139] According to one or more embodiments of the present invention, in Example 4, according to the method described in Example 2, the method further includes:

[0140] Obtain the compilation file identifier and the called compilation event identifier in the compilation file call request corresponding to the target program;

[0141] Obtain the target compilation file corresponding to the compilation file identifier, and execute the compilation event script corresponding to the target compilation event identifier in the target compilation file;

[0142] Generate an execution error message according to the execution error data of the compilation event script, and output and display the execution error message;

[0143] Among them, the execution error data includes duplicate assignment error data and / or pulled property parameter error data, and the pulled property parameter error data is determined according to the pulled property parameters corresponding to the pulled target event data.

[0144] According to one or more embodiments of the present invention, Example 5 is based on the method described in Example 4. The pulled property parameters include at least one of the number of pulled identifiers, the pulled parameter identifier corresponding to each event property parameter data, and the pulled parameter type.

[0145] According to one or more embodiments of the present invention, Example 6 is based on the method described in Example 1. Pulling the target compilation metadata from the conversion platform according to the target compilation event identifier includes:

[0146] Querying the target platform conversion identifier corresponding to the target compilation event identifier from the conversion mapping list;

[0147] According to the target platform conversion identifier, sending a metadata pull request to the conversion platform and receiving the target compilation metadata sent by the conversion platform according to the metadata pull request;

[0148] Among them, at least one preset compilation event identifier and the corresponding preset platform conversion identifier for each preset compilation event identifier are stored in the conversion mapping list, and at least one preset platform conversion identifier and the corresponding preset compilation metadata for each preset platform conversion identifier are stored in the conversion platform.

[0149] According to one or more embodiments of the present invention, Example 7 is based on the method described in Example 6. Before pulling the target compilation metadata from the conversion platform according to the target compilation event identifier, the method further includes:

[0150] Obtaining the compilation list data corresponding to the preset compilation event identifier;

[0151] Sending the compilation list data to the conversion platform so that the conversion platform converts the received compilation list data into JSON format compilation identifier data; among them, the compilation identifier data contains the preset platform conversion identifier and the preset compilation metadata;

[0152] In response to receiving the preset platform conversion identifier sent by the conversion platform, storing the preset compilation event identifier and the preset platform conversion identifier correspondingly in the conversion mapping list.

[0153] According to one or more embodiments of the present invention, Example 8 is based on the method described in Example 1. Before adding the compilation event script to the compilation file corresponding to the target compilation event identifier, the method further includes:

[0154] If there is a compilation event script corresponding to the target compilation event identifier in the compilation file, delete the compilation event script from the compilation file.

[0155] According to one or more embodiments of the present invention, Example 9 provides a device for generating a compilation file, the device includes:

[0156] A target compilation metadata pulling module, configured to pull target compilation metadata from a conversion platform according to a target compilation event identifier;

[0157] A compilation file determination module, configured to convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to a compilation file corresponding to the target compilation event identifier;

[0158] Wherein, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, the target compilation metadata defines at least one event attribute parameter data corresponding to the target compilation event identifier, and the compilation configuration script records compilation configuration data corresponding to the event attribute parameter data.

[0159] According to one or more embodiments of the present invention, Example 10 provides a compilation file generation system, the system includes: a compilation server and a conversion platform connected by communication;

[0160] Wherein, the compilation server is configured to pull target compilation metadata from the conversion platform according to a target compilation event identifier, and convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to a compilation file corresponding to the target compilation event identifier;

[0161] Wherein, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, the target compilation metadata defines at least one event attribute parameter data corresponding to the target compilation event identifier, and the compilation configuration script records compilation configuration data corresponding to the event attribute parameter data.

[0162] According to one or more embodiments of the present invention, Example 11 is based on the generation system described in Example 10, and the compilation server is specifically configured to:

[0163] Query a target platform conversion identifier corresponding to the target compilation event identifier from a conversion mapping list, and according to the target platform conversion identifier, send a metadata pulling request to the conversion platform, and receive the target compilation metadata sent by the conversion platform according to the metadata pulling request;

[0164] The conversion platform is used to send the target compiled metadata corresponding to the target platform conversion identifier in the received metadata pulling request to the compilation server;

[0165] Wherein, at least one preset compilation event identifier and the preset platform conversion identifier corresponding to each of the preset compilation event identifiers are stored in the conversion mapping list, and at least one preset platform conversion identifier and the preset compiled metadata corresponding to each of the preset platform conversion identifiers are stored in the conversion platform.

[0166] According to one or more embodiments of the present invention, Example 12 provides a generating system according to Example 11, wherein the compilation server is further configured to:

[0167] Send the compilation list data corresponding to the preset compilation event identifier to the conversion platform, and store the preset compilation event identifier and the preset platform conversion identifier sent by the received conversion platform in the conversion mapping list correspondingly;

[0168] The conversion platform is used to convert the received compilation list data into compilation identifier data in JSON format, and send the preset platform conversion identifier in the compilation identifier data to the compilation server.

[0169] According to one or more embodiments of the present invention, Example 13 provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a processor to implement the method for generating a compilation file according to any one of Examples 1-8 when executed.

[0170] The above description is only a preferred embodiment of the present invention and an explanation of the applied technical principle. Those skilled in the art should understand that the disclosed scope of the present invention is not limited to the technical solution formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the technical solution formed by mutually replacing the above features with the (but not limited to) technical features having similar functions disclosed in the present invention.

[0171] Moreover, although the operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the foregoing discussion, these should not be construed as limitations on the scope of the invention. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented separately or in any suitable subcombination in multiple embodiments.

[0172] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A method for generating a compiled file, characterized in that Including: Pull the target compilation metadata from the conversion platform according to the target compilation event identifier; Convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier; Wherein, preset compilation metadata corresponding to at least one preset compilation event identifier is stored in the conversion platform, at least one event attribute parameter data corresponding to the target compilation event identifier is defined in the target compilation metadata, and compilation configuration data corresponding to the event attribute parameter data is recorded in the compilation configuration script.

2. The method according to claim 1, characterized in that, The compilation configuration data includes constructor configuration data and assignment configuration data; wherein, the constructor configuration data is used to define adding a constructor in the compilation event script according to the attribute parameter identifier in the event attribute parameter data, and the assignment configuration data is used to define adding an assignment compilation statement in the compilation event script according to the attribute parameter identifier; Wherein, the compilation file is used to pull target event data corresponding to each of the event attribute parameter data during the running of the target program.

3. The method according to claim 2, wherein The assignment configuration data includes duplicate assignment check configuration data, and the duplicate assignment check configuration data is used to define adding a duplicate assignment check compilation statement in the assignment compilation statement.

4. The method according to claim 2, characterized in that, The method further includes: Obtain the compilation file identifier and the called compilation event identifier in the compilation file call request corresponding to the target program; Obtain the target compilation file corresponding to the compilation file identifier, and execute the compilation event script corresponding to the target compilation event identifier in the target compilation file; Generate an execution error message according to the execution error data of the compilation event script, and output and display the execution error message; Wherein, the execution error data includes duplicate assignment error data and / or pulled attribute parameter error data, and the pulled attribute parameter error data is determined according to the pulled attribute parameter corresponding to the pulled target event data.

5. The method according to claim 4, characterized in that The pulled attribute parameter includes at least one of the number of pulled identifiers, the pulled parameter identifier corresponding to each event attribute parameter data, and the pulled parameter type.

6. The method according to claim 1, wherein The pulling the target compilation metadata from the conversion platform according to the target compilation event identifier includes: Query the target platform conversion identifier corresponding to the target compilation event identifier from the conversion mapping list; According to the target platform conversion identifier, send a metadata pull request to the conversion platform, and receive the target compilation metadata sent by the conversion platform according to the metadata pull request; Wherein, at least one preset compilation event identifier and the preset platform conversion identifier corresponding to each of the preset compilation event identifiers are stored in the conversion mapping list, and at least one preset platform conversion identifier and the preset compilation metadata corresponding to each of the preset platform conversion identifiers are stored in the conversion platform.

7. The method according to claim 6, wherein Before pulling the target compilation metadata from the conversion platform according to the target compilation event identifier, the method further includes: Obtain the compilation list data corresponding to the preset compilation event identifier; Send the compiled list data to the conversion platform so that the conversion platform converts the received compiled list data into compiled identification data in JSON format; wherein, the compiled identification data includes a preset platform conversion identifier and preset compilation metadata; In response to receiving the preset platform conversion identifier sent by the conversion platform, store the preset compilation event identifier and the preset platform conversion identifier in the conversion mapping list correspondingly.

8. The method according to claim 1, wherein Before adding the compilation event script to the compilation file corresponding to the target compilation event identifier, the method further includes: If there is a compilation event script corresponding to the target compilation event identifier in the compilation file corresponding to the target compilation event identifier, delete the compilation event script from the compilation file.

9. A generating device for a compiled file, characterized in that, Includes: A target compilation metadata pulling module, configured to pull target compilation metadata from the conversion platform according to the target compilation event identifier; A compilation file determination module, configured to convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier; Wherein, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, the target compilation metadata defines at least one event attribute parameter data corresponding to the target compilation event identifier, and the compilation configuration script records compilation configuration data corresponding to the event attribute parameter data.

10. A generation system for compilation files, characterized in that, Includes: A compilation server and a conversion platform that are communicatively connected; Wherein, the compilation server is configured to pull target compilation metadata from the conversion platform according to the target compilation event identifier, and convert the target compilation metadata into a compilation event script by executing a compilation configuration script, and add the compilation event script to the compilation file corresponding to the target compilation event identifier; Wherein, the conversion platform stores preset compilation metadata respectively corresponding to at least one preset compilation event identifier, the target compilation metadata defines at least one event attribute parameter data corresponding to the target compilation event identifier, and the compilation configuration script records compilation configuration data corresponding to the event attribute parameter data.

11. The generation system according to claim 10, wherein The compilation server is specifically configured to: Query the target platform conversion identifier corresponding to the target compilation event identifier from the conversion mapping list, and send a metadata pulling request to the conversion platform according to the target platform conversion identifier, and receive the target compilation metadata sent by the conversion platform according to the metadata pulling request; The conversion platform is configured to send the target compilation metadata corresponding to the target platform conversion identifier in the received metadata pulling request to the compilation server; Wherein, the conversion mapping list stores at least one preset compilation event identifier and the preset platform conversion identifiers respectively corresponding to the preset compilation event identifiers, and the conversion platform stores at least one preset platform conversion identifier and the preset compilation metadata respectively corresponding to the preset platform conversion identifiers.

12. The generation system according to claim 11, wherein The compilation server is further configured to: Send the compilation list data corresponding to the preset compilation event identifier to the conversion platform, and store the preset compilation event identifier and the preset platform conversion identifier received from the conversion platform in the conversion mapping list correspondingly; The conversion platform is configured to convert the received compilation list data into compilation identifier data in JSON format, and send the preset platform conversion identifier in the compilation identifier data to the compilation server.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions, and the computer instructions are used to implement the method for generating a compilation file according to any one of claims 1-8 when executed by a processor.

Images