CN116521157A - Project integration method and device, storage medium and electronic device - Google Patents

Project integration method and device, storage medium and electronic device Download PDF

Info

Publication number
CN116521157A
CN116521157A CN202310315925.4A CN202310315925A CN116521157A CN 116521157 A CN116521157 A CN 116521157A CN 202310315925 A CN202310315925 A CN 202310315925A CN 116521157 A CN116521157 A CN 116521157A
Authority
CN
China
Prior art keywords
static library
item
identification information
static
determining
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310315925.4A
Other languages
Chinese (zh)
Inventor
王栋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qingdao Haier Technology Co Ltd
Haier Smart Home Co Ltd
Haier Uplus Intelligent Technology Beijing Co Ltd
Original Assignee
Qingdao Haier Technology Co Ltd
Haier Smart Home Co Ltd
Haier Uplus Intelligent Technology Beijing Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qingdao Haier Technology Co Ltd, Haier Smart Home Co Ltd, Haier Uplus Intelligent Technology Beijing Co Ltd filed Critical Qingdao Haier Technology Co Ltd
Priority to CN202310315925.4A priority Critical patent/CN116521157A/en
Publication of CN116521157A publication Critical patent/CN116521157A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/36Software reuse
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/40Transformation of program code
    • G06F8/41Compilation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30Computing systems specially adapted for manufacturing

Landscapes

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

Abstract

The application discloses a project integration method and device, a storage medium and an electronic device, and relates to the technical field of smart families, wherein the project integration method comprises the following steps: determining a first static library corresponding to a first item, wherein the first static library is a compiling product generated by a first item calling component; determining a third static library from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second project calling component; publishing the third static library to the first item to complete integration of the second item with the first item; through the steps, the problems that in the prior art, under the integration scene of the router and the active, the static library generated by the router calling component collides with the existing static library of the active, so that the router item cannot be automatically released and further cannot be smoothly integrated with the active are solved.

Description

Project integration method and device, storage medium and electronic device
Technical Field
The application relates to the technical field of smart home, in particular to a project integration method and device, a storage medium and an electronic device.
Background
In mixed-editing of native and flutter, we want to let flutter module (flutter item) at IOS end be compiled and released automatically through CI/CD pipeline, and can be referenced by pod in native engineering. If the router module only uses the router package (router plug-in), the final compiled product is uniformly integrated in the App. However, if the plug element (plug component) is included, each plug element will also generate a corresponding static library when compiling because of the native code. These static libraries need to be published as part of the router module if the active end is not used; if the active end refers to the concurrent, the active end cannot follow the flutter module to issue, otherwise, the conflict is caused.
In the prior art, under the integrated scene of the router and the native, the static library generated by the router calling component collides with the existing static library of the native, so that the router item cannot be automatically issued and further cannot be successfully integrated with the native, and an effective solution is not proposed yet.
Disclosure of Invention
The embodiment of the invention provides a project integration method and device, a storage medium and an electronic device, which at least solve the problems that in the prior art, under the integration scene of a router and a native, a static library generated by a router calling component collides with the existing static library of the native, so that the router project cannot be automatically released and further cannot be successfully integrated with the native.
According to an embodiment of the present invention, there is provided an item integration method including: determining a first static library corresponding to a first item, wherein the first static library is a compiling product generated by a first item calling component; determining a third static library from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second project calling component; and publishing the third static library to the first item to complete integration of the second item and the first item.
In an exemplary embodiment, determining a third static library from the first static library among the second static libraries includes: determining a fourth static library in the second static library according to the first static library, wherein components corresponding to the fourth static library are called by the first item and the second item; and screening the second static library according to the fourth static library to obtain the third static library.
In an exemplary embodiment, before determining a fourth static library from the second static library according to the first static library, the method further comprises: compiling the second item to obtain the second static library; acquiring first identification information of the first static library and second identification information of the second static library; and determining third identification information according to the first identification information and the second identification information, and generating a first file according to the third identification information, wherein the first identification information and the second identification information both comprise the third identification information.
In an exemplary embodiment, generating the first file according to the third identification information includes: generating the first file in a target format; and storing the third identification information in the first file, and storing the first file in a code warehouse of the second item.
In an exemplary embodiment, determining a fourth static library from the first static library among the second static libraries includes: acquiring the first file from a code warehouse of the second item, and matching the second identification information in the third identification information stored in the first file; and determining a second static library corresponding to the second identification information matched with the third identification information as the fourth static library.
In an exemplary embodiment, determining a fourth static library from the first static library among the second static libraries includes: acquiring first identification information of the first static library, and storing the first identification information in a second file; compiling the second item to obtain the second static library; and determining the second static library as a fourth static library in the case that the second identification information of the second static library is determined to exist in the second file.
In one exemplary embodiment, publishing the third static library into the first item comprises: acquiring path information of the pod container of the first item; and publishing the third static library according to the path information.
According to another embodiment of the present invention, there is also provided an item integration apparatus including: the first determining module is used for determining a first static library corresponding to a first item, wherein the first static library is a compiling product generated by the first item calling component; the second determining module is used for determining a third static library from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second project calling component; and the publishing module is used for publishing the third static library to the first item so as to complete integration of the second item and the first item.
According to yet another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium having a computer program stored therein, wherein the computer program is configured to perform the above item integration method when run.
According to still another aspect of the embodiments of the present invention, there is further provided an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the item integration method described above through the computer program.
In the embodiment of the application, a first static library corresponding to a first item is determined, wherein the first static library is a compiling product generated by a first item calling component; determining a third static library to be published from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second item calling component; then, a third static library is issued to the first item so as to complete integration of the second item and the first item; through the steps, before the compiled products of the second item are automatically released, the compiled products which can conflict with the first item are removed from the second static library, so that the release of the third static library is smoothly completed; therefore, the problem that in the prior art, under the integrated scene of the flutter and the native, a static library generated by a flutter calling component can conflict with the existing static library of the native, so that a flutter item cannot be automatically issued and further cannot be smoothly integrated with the native is solved; the method and the device realize automatic selection of correct compiling products for release, and enable the flutter item to be successfully integrated with the native item.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the description of the embodiments or the prior art will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a schematic diagram of a hardware environment of an alternative project integration method according to an embodiment of the present application;
FIG. 2 is a flow chart of an alternative project integration method according to an embodiment of the invention;
FIG. 3 is a flow diagram of an alternative project integration method according to an embodiment of the invention;
FIG. 4 is a block diagram of an alternative item integration apparatus according to an embodiment of the invention;
fig. 5 is a block diagram of another alternative item integration apparatus according to an embodiment of the invention.
Detailed Description
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
According to one aspect of the embodiments of the present application, a method of item integration is provided. The project integration method is widely applied to full-house intelligent digital control application scenes such as intelligent Home (Smart Home), intelligent Home equipment ecology, intelligent Home (Intelligence House) ecology and the like. Alternatively, in the present embodiment, the above-described item integration method may be applied to a hardware environment constituted by the terminal device 102 and the server 104 as shown in fig. 1. As shown in fig. 1, the server 104 is connected to the terminal device 102 through a network, and may be used to provide services (such as application services and the like) for a terminal or a client installed on the terminal, a database may be set on the server or independent of the server, for providing data storage services for the server 104, and cloud computing and/or edge computing services may be configured on the server or independent of the server, for providing data computing services for the server 104.
The network may include, but is not limited to, at least one of: wired network, wireless network. The wired network may include, but is not limited to, at least one of: a wide area network, a metropolitan area network, a local area network, and the wireless network may include, but is not limited to, at least one of: WIFI (Wireless Fidelity ), bluetooth. The terminal device 102 may not be limited to a PC, a mobile phone, a tablet computer, an intelligent air conditioner, an intelligent smoke machine, a refrigerator device, an intelligent oven, an intelligent cooking range, an intelligent washing machine, an intelligent water heater, an intelligent washing device, an intelligent dish washer, an intelligent projection device, an intelligent television, an intelligent clothes hanger, an intelligent curtain, an intelligent video, an intelligent socket, an intelligent sound box, an intelligent fresh air device, an intelligent kitchen and toilet device, an intelligent bathroom device, an intelligent sweeping robot, an intelligent window cleaning robot, an intelligent mopping robot, an intelligent air purifying device, an intelligent steam box, an intelligent microwave oven, an intelligent kitchen appliance, an intelligent purifier, an intelligent water dispenser, an intelligent door lock, and the like.
In this embodiment, an item integration method is provided and applied to a computer terminal, and fig. 2 is a flowchart of an alternative item integration method according to an embodiment of the present invention, where the flowchart includes the following steps:
step S202, determining a first static library corresponding to a first item, wherein the first static library is a compiling product generated by a first item calling component;
the first item may be understood as a native item, or may be another item, which is not limited in this application.
Step S204, determining a third static library from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second project calling component;
the second item may be understood as a router item, or may be another item, which is not limited in this application.
Step S206, publishing the third static library to the first item to complete the integration of the second item and the first item.
In the embodiment of the application, a first static library corresponding to a first item is determined, wherein the first static library is a compiling product generated by a first item calling component; determining a third static library to be published from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second item calling component; then, a third static library is issued to the first item so as to complete integration of the second item and the first item; through the steps, before the compiled products of the second item are automatically released, the compiled products which can conflict with the first item are removed from the second static library, so that the release of the third static library is smoothly completed; therefore, the problems that in the prior art, under the integrated scene of the flutter and the native, a static library generated by a flutter calling component can conflict with the existing static library of the native, so that a flutter item cannot be automatically issued and further cannot be successfully integrated with the native are solved; the method and the device realize automatic selection of correct compiling products for release, and enable the flutter item to be successfully integrated with the native item.
Optionally, the step S204 is executed, and determining, according to the first static library, a third static library from the second static library includes: determining a fourth static library in the second static library according to the first static library, wherein components corresponding to the fourth static library are called by the first item and the second item; and screening the second static library according to the fourth static library to obtain the third static library.
The step of determining a third static library from the second static library comprises: firstly, determining a fourth static library in a second static library according to the first static library, wherein components corresponding to the fourth static library are called by the first item and the second item, namely the fourth static library is a conflict static library of the first item and the second item; after determining the fourth static library (i.e., the conflict static library), screening the fourth static library from the second static library to obtain a third static library to be released.
Optionally, the steps described above are performed: before determining a fourth static library in the second static library according to the first static library, the method further comprises: compiling the second item to obtain the second static library; acquiring first identification information of the first static library and second identification information of the second static library; and determining third identification information according to the first identification information and the second identification information, and generating a first file according to the third identification information, wherein the first identification information and the second identification information both comprise the third identification information.
Optionally, before determining the fourth static library, compiling the second item to obtain the second static library; and then acquiring identification information of the first static library and the second static library, namely information such as static library names and the like for identifying the static library, determining third identification information contained in the first identification information and the second identification information, and generating a first file according to the third identification information.
Optionally, generating the first file according to the third identification information includes: generating the first file in a target format; and storing the third identification information in the first file, and storing the first file in a code warehouse of the second item.
The step of generating the first file according to the third identification information comprises: first, a first file in a target format is generated, all third identification information is stored in the first file, and then the obtained first file stored with the third identification information is stored in a code warehouse of a second item.
The first file in the target format may be a yaml file, a palm file, a hart file, or other files in other formats, which is not limited in this application.
Optionally, determining a fourth static library from the second static library according to the first static library includes: acquiring the first file from a code warehouse of the second item, and matching the second identification information in the third identification information stored in the first file; and determining a second static library corresponding to the second identification information matched with the third identification information as the fourth static library.
Based on the above steps, the first file is obtained from the code repository of the second item, then the second identification information is matched in the third identification information stored in the first file, if the second identification information is matched, that is, the second identification information exists in the first file, the second static library corresponding to the second identification information is determined to be the fourth static library.
Optionally, determining a fourth static library from the second static library according to the first static library includes: acquiring first identification information of the first static library, and storing the first identification information in a second file; compiling the second item to obtain the second static library; and determining the second static library as a fourth static library in the case that the second identification information of the second static library is determined to exist in the second file.
Optionally, the scheme of determining the fourth static library may further include the following steps: first, first identification information of the first static library is acquired, and then a second file is generated to store the first identification information; then compiling the second item to obtain a second static library; and if the second identification information of the second static library is determined to exist in the second file, determining the second static library as a fourth static library.
Optionally, publishing the third static library into the first item includes: acquiring path information of the pod container of the first item; and publishing the third static library according to the path information.
Based on the above steps, after the third static library is determined, the third static library needs to be released into the first item, which is specifically implemented by the following scheme: the path information of the pod container of the first item is acquired first, and then the third static library is issued according to the path information, wherein the pod container is used for storing the third static library.
Optionally, the embodiment of the present application further provides an optional project integration method, as shown in fig. 3, and fig. 3 is a schematic flow diagram of an optional project integration method according to an embodiment of the present invention; the method specifically comprises the following steps:
step 1, starting;
step 2, saving static library names which are in conflict with native in the router plug in an include file in a router module code library, and receiving version control;
step 3, flutter build IOS is carried out to construct an IOS product;
step 4, acquiring the generated App.frame work;
step 5, traversing a static library (equivalent to the IOS product) to determine whether the static library is in an include file; if yes, the processing is not carried out, and if not, the step 6 is executed;
step 6, adding the static library to select all static libraries which have no conflict with Native, and then returning to the execution step 5 until all static libraries are traversed;
step 7, publishing the finally obtained static library (corresponding to the third static library) to a pod private library (corresponding to the pod container);
and 8, ending.
By arranging static libraries which collide with native in the construction of the router module in advance, arranging the names of the colliding static libraries into a text file include, archiving the text file into a router module code warehouse, and receiving version control. The document is maintained all the time in the code development process, so that the conflict component is effectively removed in the CI/CD automatic construction process; flutter build IOS is then performed to build the IOS product; acquiring a generated App. Circularly traversing the generated static libraries, and selecting all static libraries which have no conflict with the native; finally, the product is released to the pod private library. Through the steps, a first static library corresponding to a first item is determined, wherein the first static library is a compiling product generated by a first item calling component; determining a third static library to be published from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second item calling component; then, a third static library is issued to the first item so as to complete integration of the second item and the first item; through the steps, before the compiled products of the second item are automatically released, the compiled products which can conflict with the first item are removed from the second static library, so that the release of the third static library is smoothly completed; therefore, the problems that in the prior art, under the integrated scene of the flutter and the native, a static library generated by a flutter calling component can conflict with the existing static library of the native, so that a flutter item cannot be automatically issued and further cannot be successfully integrated with the native are solved; the method and the device realize automatic selection of correct compiling products for release, and enable the flutter item to be successfully integrated with the native item.
From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of the various embodiments of the present invention.
In this embodiment, an item integration device is further provided, and the item integration device is used to implement the foregoing embodiments and preferred embodiments, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
FIG. 4 is a block diagram of an alternative item integration apparatus according to an embodiment of the invention; as shown in fig. 4, includes:
a first determining module 42, configured to determine a first static library corresponding to a first item, where the first static library is a compiled product generated by the first item calling component;
the first item may be understood as a native item, or may be another item, which is not limited in this application.
A second determining module 44, configured to determine a third static library from the first static library in a second static library, where the second static library is a compiled product generated by a second item calling component;
the second item may be understood as a router item, or may be another item, which is not limited in this application.
And a publishing module 46, configured to publish the third static library to the first item, so as to complete integration of the second item and the first item.
Through the device, a first static library corresponding to a first item is determined, wherein the first static library is a compiling product generated by a first item calling component; determining a third static library to be published from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second item calling component; then, a third static library is issued to the first item so as to complete integration of the second item and the first item; through the steps, before the compiled products of the second item are automatically released, the compiled products which can conflict with the first item are removed from the second static library, so that the release of the third static library is smoothly completed; therefore, the problems that in the prior art, under the integrated scene of the flutter and the native, a static library generated by a flutter calling component can conflict with the existing static library of the native, so that a flutter item cannot be automatically issued and further cannot be successfully integrated with the native are solved; the method and the device realize automatic selection of correct compiling products for release, and enable the flutter item to be successfully integrated with the native item.
Optionally, the second determining module 44 is further configured to determine a fourth static library from the second static library according to the first static library, where components corresponding to the fourth static library are all invoked by the first item and the second item; and screening the second static library according to the fourth static library to obtain the third static library.
The step of determining a third static library from the second static library comprises: firstly, determining a fourth static library in a second static library according to the first static library, wherein components corresponding to the fourth static library are called by the first item and the second item, namely the fourth static library is a conflict static library of the first item and the second item; after determining the fourth static library (i.e., the conflict static library), screening the fourth static library from the second static library to obtain a third static library to be released.
Optionally, another optional item integration apparatus is provided in an embodiment of the present application, as shown in fig. 5, and fig. 5 is a block diagram of another optional item integration apparatus according to an embodiment of the present invention, where the item integration apparatus further includes:
a compiling module 48, configured to compile the second item to obtain the second static library; acquiring first identification information of the first static library and second identification information of the second static library; and determining third identification information according to the first identification information and the second identification information, and generating a first file according to the third identification information, wherein the first identification information and the second identification information both comprise the third identification information.
Optionally, before determining the fourth static library, compiling the second item to obtain the second static library; and then acquiring identification information of the first static library and the second static library, namely information such as static library names and the like for identifying the static library, determining third identification information contained in the first identification information and the second identification information, and generating a first file according to the third identification information.
The generating module 50 is further configured to generate the first file in a target format; and storing the third identification information in the first file, and storing the first file in a code warehouse of the second item.
The step of generating the first file according to the third identification information comprises: first, a first file in a target format is generated, all third identification information is stored in the first file, and then the obtained first file stored with the third identification information is stored in a code warehouse of a second item.
The first file in the target format may be a yaml file, a palm file, a hart file, or other files in other formats, which is not limited in this application.
Optionally, the second determining module 44 is further configured to obtain the first file from a code repository of the second item, and match the second identification information in the third identification information stored in the first file; and determining a second static library corresponding to the second identification information matched with the third identification information as the fourth static library.
Based on the above steps, the first file is obtained from the code repository of the second item, then the second identification information is matched in the third identification information stored in the first file, if the second identification information is matched, that is, the second identification information exists in the first file, the second static library corresponding to the second identification information is determined to be the fourth static library.
Optionally, the second determining module 44 is further configured to obtain first identification information of the first static library, and store the first identification information in a second file; compiling the second item to obtain the second static library; and determining the second static library as a fourth static library in the case that the second identification information of the second static library is determined to exist in the second file.
Optionally, the scheme of determining the fourth static library may further include the following steps: first, first identification information of the first static library is acquired, and then a second file is generated to store the first identification information; then compiling the second item to obtain a second static library; and if the second identification information of the second static library is determined to exist in the second file, determining the second static library as a fourth static library.
Optionally, the publishing module 46 is further configured to obtain path information of the pod container of the first item; and publishing the third static library according to the path information.
Based on the above steps, after the third static library is determined, the third static library needs to be released into the first item, which is specifically implemented by the following scheme: the path information of the pod container of the first item is acquired first, and then the third static library is issued according to the path information, wherein the pod container is used for storing the third static library.
An embodiment of the present invention also provides a storage medium including a stored program, wherein the program executes the method of any one of the above.
Alternatively, in the present embodiment, the above-described storage medium may be configured to store program code for performing the steps of:
s1, determining a first static library corresponding to a first item, wherein the first static library is a compiling product generated by a first item calling component;
s2, determining a third static library from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second project calling component;
and S3, publishing the third static library to the first item to complete integration of the second item and the first item.
An embodiment of the invention also provides an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.
Optionally, the electronic apparatus may further include a transmission device and an input/output device, where the transmission device is connected to the processor, and the input/output device is connected to the processor.
Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:
s1, determining a first static library corresponding to a first item, wherein the first static library is a compiling product generated by a first item calling component;
s2, determining a third static library from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second project calling component;
and S3, publishing the third static library to the first item to complete integration of the second item and the first item.
Alternatively, in the present embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Alternatively, specific examples in this embodiment may refer to examples described in the foregoing embodiments and optional implementations, and this embodiment is not described herein.
It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a memory device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A method of item integration, comprising:
determining a first static library corresponding to a first item, wherein the first static library is a compiling product generated by a first item calling component;
determining a third static library from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second project calling component;
and publishing the third static library to the first item to complete integration of the second item and the first item.
2. The method of claim 1, wherein determining a third static library from the first static library from the second static library comprises:
determining a fourth static library in the second static library according to the first static library, wherein components corresponding to the fourth static library are called by the first item and the second item;
and screening the second static library according to the fourth static library to obtain the third static library.
3. The project integration method of claim 2, wherein before determining a fourth static library from the second static library from the first static library, the method further comprises:
compiling the second item to obtain the second static library;
acquiring first identification information of the first static library and second identification information of the second static library;
and determining third identification information according to the first identification information and the second identification information, and generating a first file according to the third identification information, wherein the first identification information and the second identification information both comprise the third identification information.
4. The item integration method of claim 3, wherein generating a first file from the third identification information comprises:
generating the first file in a target format;
and storing the third identification information in the first file, and storing the first file in a code warehouse of the second item.
5. The method of claim 4, wherein determining a fourth static library from the first static library from the second static library comprises:
acquiring the first file from a code warehouse of the second item, and matching the second identification information in the third identification information stored in the first file;
and determining a second static library corresponding to the second identification information matched with the third identification information as the fourth static library.
6. The project integration method of claim 2, wherein determining a fourth static library from the first static library among the second static libraries comprises:
acquiring first identification information of the first static library, and storing the first identification information in a second file;
compiling the second item to obtain the second static library;
and determining the second static library as a fourth static library in the case that the second identification information of the second static library is determined to exist in the second file.
7. The project integration method of claim 1, wherein publishing the third static library into the first project comprises:
acquiring path information of the pod container of the first item;
and publishing the third static library according to the path information.
8. An item integration apparatus, comprising:
the first determining module is used for determining a first static library corresponding to a first item, wherein the first static library is a compiling product generated by the first item calling component;
the second determining module is used for determining a third static library from a second static library according to the first static library, wherein the second static library is a compiling product generated by a second project calling component;
and the publishing module is used for publishing the third static library to the first item so as to complete integration of the second item and the first item.
9. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a stored program, wherein the program, when run, performs the method of any one of claims 1 to 7.
10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of the claims 1 to 7 by means of the computer program.
CN202310315925.4A 2023-03-28 2023-03-28 Project integration method and device, storage medium and electronic device Pending CN116521157A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310315925.4A CN116521157A (en) 2023-03-28 2023-03-28 Project integration method and device, storage medium and electronic device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310315925.4A CN116521157A (en) 2023-03-28 2023-03-28 Project integration method and device, storage medium and electronic device

Publications (1)

Publication Number Publication Date
CN116521157A true CN116521157A (en) 2023-08-01

Family

ID=87391124

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310315925.4A Pending CN116521157A (en) 2023-03-28 2023-03-28 Project integration method and device, storage medium and electronic device

Country Status (1)

Country Link
CN (1) CN116521157A (en)

Similar Documents

Publication Publication Date Title
CN116033006A (en) Data processing method, system, storage medium and electronic device
CN114697150A (en) Command issuing method and device, storage medium and electronic device
CN116107975A (en) Control method and device of equipment, storage medium and electronic device
CN116027937A (en) Rendering method and device of component to be edited, storage medium and electronic device
CN116521157A (en) Project integration method and device, storage medium and electronic device
CN111105298A (en) Purchasing recommendation method and system based on intelligent scene of Internet of things
CN114675928A (en) Container mirror image construction method and device, storage medium and electronic device
CN115345225A (en) Method and device for determining recommended scene, storage medium and electronic device
CN116301767A (en) Interface file generation method and device, storage medium and electronic device
CN116450229A (en) Pre-starting method and device of application software, storage medium and electronic device
CN115002014B (en) Method and device for determining test result, storage medium and electronic device
CN117707488A (en) Function response method and device, storage medium and electronic device
CN114938365B (en) Function module updating method and device, storage medium and electronic device
CN117573320A (en) Task node execution method and device, storage medium and electronic device
CN116225456A (en) Program deployment method, device, storage medium and terminal
CN116737337A (en) Log sending method and device, storage medium and electronic equipment
CN116382766A (en) Page packaging method and device, storage medium and electronic device
CN115269926A (en) Family map determination method and device, storage medium and electronic device
CN115480809A (en) Method and device for determining code submission amount, storage medium and electronic device
CN116382107A (en) Equipment instruction acquisition method and device, storage medium and electronic device
CN117742821A (en) Method and device for determining update flow, storage medium and electronic device
CN116107551A (en) Application data detection method and device, storage medium and electronic device
CN117749843A (en) Scene triggering method and device, storage medium and electronic device
CN116521767A (en) Data information determining method and device, storage medium and electronic device
CN116303535A (en) Data query method and device, storage medium and electronic device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination