Cross-platform software development method, equipment and medium

Abstract

The invention relates to the technical field of smart home / smart home, particularly provides a cross-platform software development method and equipment and a medium, and aims to solve the technical problem of relatively high maintenance cost caused by repeated code writing for different systems in an existing development method. In order to achieve the purpose, the cross-platform software development method comprises the steps that the system type of a target platform is obtained; configuring a compiling environment based on the system type; creating a target project project; obtaining a library file corresponding to the system type based on the compiling environment and the target project project; and releasing the library file to a preset warehouse to obtain the target application program based on the library file. Thus, a developer only needs to maintain one set of core code library, the time and cost for independently developing each platform are reduced, and the development speed is increased.

Description

Technical Field

[0001] The present invention relates to the field of smart home / intelligent family technology, and specifically provides a cross-platform software development method, device and medium. Background Art

[0002] The security issues of mobile application development are receiving more and more attention, and developers need to ensure the security of the program and the protection of user privacy.

[0003] With the advent of the HarmonyOS system, the problem of code reuse has become increasingly prominent. An application may need to maintain three sets of codes: Android, iOS, and HarmonyOS. The maintenance cost of the application is getting higher and higher, and developers need to write code repeatedly.

[0004] To this end, this application proposes a cross-platform software development solution. Summary of the invention

[0005] In order to overcome the above defects, this application is proposed to solve or at least partially solve the technical problem that the existing development method needs to repeatedly write code for different systems, resulting in high maintenance costs. This application provides a cross-platform software development method, device and medium.

[0006] In a first aspect, the present application provides a cross-platform software development method, the method comprising:

[0007] Get the system type of the target platform;

[0008] Configuring a compilation environment based on the system type;

[0009] Create the target project;

[0010] Acquire a library file based on the compilation environment and the target project, wherein the library file corresponds to the system type of the target platform;

[0011] The library file is published to a preset warehouse, so that a target application is obtained based on the library file.

[0012] In one embodiment of the present application, configuring the compilation environment based on the system type includes:

[0013] Install the Rust compiler;

[0014] Install the Rust toolchain based on your system type.

[0015] In one embodiment of the present application, the step of creating a target project includes:

[0016] Select a code editor;

[0017] Using the code editor to create a target project;

[0018] Write Rust code for the target project to obtain the target project project.

[0019] In one embodiment of the present application, the acquiring of a library file corresponding to the system type based on the compilation environment and the target project includes:

[0020] Compile the target project using the Rust compiler in the compilation environment to obtain a binary file corresponding to the target project;

[0021] The binary file is packaged into a library file corresponding to the system type.

[0022] In one embodiment of the present application, the Rust tool chain includes any one of the cargo-ndk tool and the cargo-lipo tool;

[0023] Packing the binary file into a library file corresponding to the system type includes:

[0024] When the system type is Android, packaging the binary file based on the cargo-ndk tool to obtain a library file corresponding to the system type;

[0025] When the system type is IOS, the binary file is packaged based on the cargo-lipo tool to obtain a library file corresponding to the system type;

[0026] When the system type is HarmonyOS, a Clang link script is configured, and the binary file is packaged based on the configured Clang link script to obtain a library file corresponding to the system type.

[0027] In one embodiment of the present application, publishing the library file to a preset warehouse includes:

[0028] Create integrated modules;

[0029] Integrate the library file into the integration module;

[0030] The integration module is published to the preset warehouse.

[0031] In one embodiment of the present application, the creation of the integrated module includes:

[0032] When the system type is Android, using Android Studio to create the integration module;

[0033] When the system type is IOS, using Xcode to create the integration module;

[0034] When the system type is HarmonyOS, Dev-Echo is used to create the integrated module.

[0035] In one embodiment of the present application, publishing the integration module to the preset warehouse includes:

[0036] When the system type is Android, publishing the integration module to a Maven repository;

[0037] When the system type is IOS, publishing the integration module to a Git server;

[0038] When the system type is HarmonyOS, the integrated module is published to a preset warehouse.

[0039] In a second aspect, a computer device is provided, comprising:

[0040] at least one processor;

[0041] and, a memory communicatively coupled to the at least one processor;

[0042] Wherein, a computer program is stored in the memory, and when the computer program is executed by the at least one processor, it is the aforementioned cross-platform software development method.

[0043] In a third aspect, a computer-readable storage medium is provided, wherein a plurality of program codes are stored in the computer-readable storage medium, wherein the program codes are suitable for being loaded and run by a processor to execute any of the aforementioned cross-platform software development methods.

[0044] The above one or more technical solutions of the present application have at least one or more of the following beneficial effects:

[0045] The cross-platform software development method in this application includes: obtaining the system type of the target platform; configuring the compilation environment based on the system type; creating a target project engineering; obtaining the library file corresponding to the system type based on the compilation environment and the target project engineering; publishing the library file to the preset warehouse so that the target application is obtained based on the library file. In this way, the developer only needs to maintain a set of core code libraries, reducing duplication of work and improving the development speed. By writing once and running in multiple places, the time and cost of developing separately for each platform are reduced. The compilation environment is automatically configured according to different system types, which reduces the workload of manual configuration and reduces the possibility of errors. By creating a unified target project engineering, the same code library can be reused to reduce code redundancy. The generated library files can be reused on different platforms, avoiding the need to write code with similar functions for each platform. Maintaining a single core code library is simpler than maintaining multiple platform-specific code libraries, reducing code maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The disclosure of the present application will become more easily understood with reference to the accompanying drawings. It is easy for those skilled in the art to understand that these drawings are only for illustrative purposes and are not intended to limit the scope of protection of the present application. In addition, similar numbers in the drawings are used to represent similar components, among which:

[0047] Figure 1 This is a schematic diagram of the hardware environment of a cross-platform software development method in one embodiment of the present application;

[0048] Figure 2 This is a schematic diagram of the main process of a cross-platform software development method in one embodiment of the present application;

[0049] Figure 3 This is a complete flow chart of a cross-platform software development method in one embodiment of the present application;

[0050] Figure 4 It is a schematic diagram of the main structure of a cross-platform software development device in one embodiment of the present application;

[0051] Figure 5 It is a schematic diagram of the structure of a computer device in one embodiment of the present application. DETAILED DESCRIPTION

[0052] Some embodiments of the present application are described below with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are only used to explain the technical principles of the present application and are not intended to limit the protection scope of the present application.

[0053] In the description of the present application, "module" and "processor" may include hardware, software or a combination of the two. A module may include hardware circuits, various suitable sensors, communication ports, memory, and may also include software parts, such as program code, or a combination of software and hardware. The processor may be a central processing unit, a microprocessor, an image processor, a digital signal processor or any other suitable processor. The processor has data and / or signal processing functions. The processor may be implemented in software, hardware or a combination of the two. Non-temporary computer-readable storage media include any suitable medium that can store program code, such as a disk, a hard disk, an optical disk, a flash memory, a read-only memory, a random access memory, etc. The term "A and / or B" means all possible combinations of A and B, such as only A, only B or A and B. The term "at least one A or B" or "at least one of A and B" has a similar meaning to "A and / or B" and may include only A, only B or A and B. The singular terms "one" and "the" may also include plural forms.

[0054] With the current traditional development methods, an application may need to maintain three sets of codes: Android, iOS, and HarmonyOS. The maintenance cost of the application is getting higher and higher, and developers need to write code repeatedly.

[0055] To this end, the present application proposes a cross-platform software development method, device and storage medium.

[0056] According to one aspect of the embodiments of the present application, a cross-platform software development method, device and storage medium are provided. The cross-platform software development method, device and storage medium are widely used in smart home (Smart Home), smart home, smart home device ecology, smart residential (Intelligence House) ecology and other whole-house intelligent digital control application scenarios. Optionally, in this embodiment, the above-mentioned cross-platform software development method, device and storage medium can be applied to Figure 1 In the hardware environment composed of the terminal device 10 and the server 20 shown in FIG. Figure 1 As shown, the server 20 is connected to the terminal device 10 via a network, and can be used to provide services (such as application services, etc.) for the terminal or a client installed on the terminal. A database can be set on the server or independently of the server to provide data storage services for the server 20. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data computing services for the server 20.

[0057] The network may include but is not limited to at least one of the following: wired network, wireless network. The wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth. The terminal device 10 may be but is not limited to a PC, a mobile phone, a tablet computer, a smart air conditioner, a smart range hood, a smart refrigerator, a smart oven, a smart stove, a smart washing machine, a smart water heater, a smart washing equipment, a smart dishwasher, a smart projection equipment, a smart TV, a smart clothes drying rack, a smart curtain, a smart audio and video, a smart socket, a smart speaker, a smart speaker, a smart fresh air equipment, a smart kitchen and bathroom equipment, a smart bathroom equipment, a smart sweeping robot, a smart window cleaning robot, a smart mopping robot, a smart air purification equipment, a smart steamer, a smart microwave oven, a smart kitchen treasure, a smart purifier, a smart water dispenser, a smart door lock, etc.

[0058] See attached Figure 2 , Figure 2 It is a flowchart of the main steps of a cross-platform software development method according to an embodiment of the present application.

[0059] like Figure 2 As shown, the cross-platform software development method in the embodiment of the present application mainly includes the following steps S10 to S50.

[0060] Step S10: Obtain the system type of the target platform.

[0061] System refers to the specific operating system used to develop cross-platform applications.

[0062] The target platform may refer to a computer device.

[0063] The system type refers to the specific operating system type of the target platform, such as Android, iOS, HarmonyOS, etc.

[0064] Step S20: configuring the compilation environment based on the system type.

[0065] The compilation environment refers to the toolset and configuration used to compile and build software, including compilers, tool chains, etc. In cross-platform development, it usually involves configuring different tool chains for different platforms so that executable files or library files can be generated for specific platforms.

[0066] Step S30: Create a target project.

[0067] The target project refers to the actual software project to be developed, which includes all relevant source code, resource files, configuration files, etc.

[0068] Step S40: Obtaining a library file corresponding to the system type based on the compilation environment and the target project.

[0069] Library files are collections of precompiled code used to provide specific functionality in software development. They can be static libraries (such as .a files) or shared libraries (such as .so files).

[0070] Step S50: publishing the library file to a preset warehouse, so as to obtain a target application based on the library file.

[0071] A preset repository is a central repository for storing and managing library files. It can be private or public and is used to easily distribute and update library files.

[0072] Based on the above steps S10-S50, first obtain the system type of the target platform; configure the compilation environment based on the system type; create a target project; obtain the library file corresponding to the system type based on the compilation environment and the target project; publish the library file to the preset warehouse so that the target application can be obtained based on the library file. In this way, developers only need to maintain a set of core code libraries, which reduces duplication of work and improves development speed. By writing once and running in multiple places, the time and cost of developing separately for each platform are reduced. Automatically configure the compilation environment according to different system types, reduce the workload of manual configuration, and reduce the possibility of errors. By creating a unified target project project, the same code library can be reused to reduce code redundancy. The generated library files can be reused on different platforms, avoiding the need to write code with similar functions for each platform. Maintaining a single core code library is simpler than maintaining multiple platform-specific code libraries, reducing code maintenance costs.

[0073] The above steps S10 to S50 are further explained below.

[0074] Specifically, for the above step S10, first clarify on which types of devices the developed application will run, such as smartphones, tablets, etc. These devices usually run different operating systems, such as Android, iOS, HarmonyOS, etc. By identifying the specific operating system type on each target platform, record its operating system name and version number.

[0075] The above is a further description of step S10 , and the following is a further description of step S20 .

[0076] Specifically, step S20 can be implemented through the following steps S201 to S202.

[0077] Step S201: Install the Rust compiler.

[0078] Specifically, you first need to install the Rust compiler. The Rust official website provides installation scripts for different operating systems, which can be used to install the Rust compiler and related tools such as Rustup.

[0079] Step S202: Install the Rust tool chain based on the system type.

[0080] The Rust toolchain refers to a collection of tools, libraries, and package managers that are necessary for the Rust programming language to support developers from writing code to ultimately deploying applications. For example, package managers and build tools, toolchain managers, standard libraries and other libraries, and auxiliary tools can all serve as examples of the Rust toolchain.

[0081] For auxiliary tools, in order to package library files for the Android platform, you need to install cargo-ndk; in order to package library files for the iOS platform, you need to install cargo-lipo.

[0082] By configuring the compilation environment according to the system type, the workload of manual configuration is reduced and the possibility of errors is reduced; at the same time, developers can more easily build secure, efficient and reliable applications.

[0083] The above is a further description of step S20 , and the following is a further description of step S30 .

[0084] Specifically, step S30 can be implemented through the following steps S301 to S303.

[0085] Step S301: Select a code editor.

[0086] In software development, IDE (Integrated Development Environment) is a very important tool. It provides developers with a comprehensive software development platform that covers multiple functions such as code editing, compilation, debugging, version control, etc.

[0087] For example, for mobile cross-platform development in Rust language, RustRover or VS Code can be used as IDE tools. RustRover or VS Code tools provide good support for Rust language, including syntax highlighting, code completion, debugging and other functions, which can help developers develop Rust applications more efficiently.

[0088] Step S302: Create a target project using a code editor.

[0089] Specifically, you can use the command line tool in the code editor to create a new Rust project, and you can also save the Rust project as a src / lib.rs file.

[0090] Step S303: Write Rust code for the target project to obtain the target project project.

[0091] Next, write Rust code for the created Rust project, such as defining functions, structures, enumerations, etc., and ensure that these codes can be called by other platforms. In this way, you can create and develop a Rust project in a configured compilation environment.

[0092] In addition, you can further define Rust code to interact with languages ​​of other platforms. Specifically, for Android system, use rust's JNI crate to interact with Java or Kotlin. For HarmonyOS system, use NAPI to interact with arkts. For iOS platform, you can use FFI (Foreign Function Interface) to interact with Swift or Objective-C.

[0093] The above is a further description of step S30 , and the following is a further description of step S40 .

[0094] Specifically, step S40 can be implemented through the following steps S401 to S402.

[0095] Step S401: Use the Rust compiler in the compilation environment to compile the target project to obtain a binary file corresponding to the target project.

[0096] Specifically, by using the Rust compiler to compile the target project, you can get the binary file corresponding to the target project.

[0097] Step S402: Pack the binary file into a library file corresponding to the system type.

[0098] In a specific embodiment of the present application, the Rust tool chain includes auxiliary tools, and the auxiliary tools include any one of a cargo-ndk tool and a cargo-lipo tool. When the system type is Android, the binary file is packaged based on the cargo-ndk tool to obtain a library file corresponding to the system type; when the system type is IOS, the binary file is packaged based on the cargo-lipo tool to obtain a library file corresponding to the system type; when the system type is HarmonyOS, the Clang link script is configured, and the binary file is packaged based on the configured Clang link script to obtain a library file corresponding to the system type.

[0099] Specifically, for the Android system, you can use the installed cargo-ndk tool to package the binary file to generate a .so library file, which can be directly called in the Android application.

[0100] For IOS systems, you can use the installed cargo-lipo tool to package the binary files to generate a .a file (static library file), which can be directly called in iOS applications.

[0101] For the HarmonyOS system, create a script file (for example, aarch64-unknown-linux-ohos-clang.sh) and generate a .a or .so file (library file) based on the configured script file. The file can be directly called in the HarmonyOS application.

[0102] The above is a further description of step S40 , and the following is a further description of step S50 .

[0103] Specifically, step S50 can be implemented through the following steps S501 to S503.

[0104] Step S501: Create an integrated module.

[0105] An integrated module refers to a collection of library files. For example, a Library module can be used as an example of the integrated module.

[0106] In a specific implementation of the present application, the creation of the integrated module includes: when the system type is Android, using Android Studio to create the integrated module; when the system type is IOS, using Xcode to create the integrated module; when the system type is HarmonyOS, using Dev-Echo to create the integrated module.

[0107] Step S502: Integrate the library file into the integration module.

[0108] Specifically, for the Android system, you can use Android Studio to create an empty Library module and integrate the .so library file generated by Rust into it.

[0109] For iOS, you can use Xcode to create an empty Library module and integrate the static library file (.a file) generated by Rust into it.

[0110] For the HarmonyOS system, you can use Dev-Echo to create an empty Library module and integrate the library files generated by Rust into it.

[0111] Step S503: Publish the integrated module to the preset warehouse.

[0112] A preset repository is a central repository for storing and managing library files. It can be private or public and is used to easily distribute and update library files.

[0113] In a specific embodiment of the present application, publishing the integrated module to the preset warehouse includes: when the system type is Android, publishing the integrated module to the Maven warehouse; when the system type is IOS, publishing the integrated module to the Git server; when the system type is HarmonyOS, publishing the integrated module to the preset warehouse.

[0114] Exemplarily, for the Android system, the Library module (integrated module) is published as an AAR (Android Archive) file to the Maven repository.

[0115] For iOS, publish the Library module (integrated module) as a CocoaPod to the Git server.

[0116] For the HarmonyOS system, the Library module (integrated module) is published to the private repository as a HAR (HarmonyOSArchive) file.

[0117] By integrating library files into integrated modules, dependencies and version control can be managed more easily, and encapsulated library files can be reused in multiple projects to obtain target applications, thereby reducing development time and costs.

[0118] Figure 3It is a complete flowchart of a cross-platform software development method in one embodiment of the present application.

[0119] like Figure 3 As shown, the cross-platform software development method in this embodiment can be specifically implemented through the following steps S1 to S6.

[0120] Step S1: Configure the compilation environment.

[0121] Step S2: Create a Rust project and compile the Rust project to generate a binary file.

[0122] Step S3: Pack the binary file to obtain the library file of the Android platform.

[0123] Step S4: Package the binary file to obtain the library file of the HarmonyOS platform.

[0124] Step S5: Pack the binary file to obtain the library file of the iOS platform.

[0125] Step S6: Integrate the library file into the integration module and publish it to the preset warehouse.

[0126] This application can significantly reduce the work of repetitive code writing by using the Rust language for cross-platform development, and the same code base can be used on different operating systems. Rust's powerful performance and concurrency can help developers better optimize applications and improve user experience. Rust's own language structure can help developers avoid common memory safety issues, such as null pointer references and buffer overflows; Rust supports asynchronous programming, which can help developers better handle asynchronous tasks.

[0127] It should be pointed out that although the various steps in the above embodiments are described in a specific order, those skilled in the art can understand that in order to achieve the effect of the present application, different steps do not have to be executed in such an order. They can be executed simultaneously (in parallel) or in other orders. These changes are within the scope of protection of the present application.

[0128] Furthermore, the present application also provides a cross-platform software development device.

[0129] See attached Figure 4 , Figure 4 It is a main structural block diagram of a cross-platform software development device according to an embodiment of the present application.

[0130] like Figure 4As shown, the cross-platform software development device in the embodiment of the present application mainly includes a first acquisition module 11, a configuration module 12, a creation module 13, a second acquisition module 14 and a publishing module 15. In some embodiments, one or more of the first acquisition module 11, the configuration module 12, the creation module 13, the second acquisition module 14 and the publishing module 15 can be combined into one module.

[0131] In some embodiments, the first acquisition module 11 may be configured to acquire a system type of a target platform.

[0132] The configuration module 12 may be configured to configure the compilation environment based on the system type.

[0133] The creation module 13 may be configured to create a target project.

[0134] The second acquisition module 14 may be configured to acquire a library file corresponding to the system type based on the compilation environment and the target project.

[0135] The publishing module 15 may be configured to publish the library file to a preset warehouse, so that a target application is obtained based on the library file.

[0136] In one implementation, the description of the specific implementation functions can refer to steps S10-S50.

[0137] The cross-platform software development device is used to execute Figure 2 The cross-platform software development method embodiment shown in the figure has similar technical principles, technical problems solved and technical effects produced. Technical personnel in this technical field can clearly understand that for the convenience and conciseness of description, the specific working process and related instructions of the cross-platform software development device can refer to the contents described in the embodiment of the cross-platform software development method, which will not be repeated here.

[0138] Further, it should be understood that since the setting of each module is only for illustrating the functional units of the device of the present application, the physical devices corresponding to these modules may be the processor itself, or a part of the software in the processor, a part of the hardware, or a part of the combination of software and hardware. Therefore, the number of each module in the figure is only schematic.

[0139] It is understood by those skilled in the art that each module in the device can be adaptively split or merged. Such splitting or merging of specific modules will not cause the technical solution to deviate from the principle of the present application, and therefore, the technical solutions after splitting or merging will fall within the protection scope of the present application.

[0140] It is understood by those skilled in the art that all or part of the processes in the method for implementing the above-mentioned embodiment of the present application can also be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium may include: any entity or device, medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory, random access memory, electrical carrier signal, telecommunication signal and software distribution medium, etc. that can carry the computer program code.

[0141] Furthermore, the present application also provides a computer device, which may include at least one processor; and a memory connected to the at least one processor; wherein a computer program is stored in the memory, and when the computer program is executed by the at least one processor, the cross-platform software development method described in any of the above embodiments is implemented. Figure 5 As shown, Figure 5 exemplarily shows the structure of a computer device, which includes a processor 100 and a memory 200.

[0142] Further, the present application also provides a computer-readable storage medium. In a computer-readable storage medium embodiment according to the present application, the computer-readable storage medium can be configured to store a program for executing the cross-platform software development method of the above-mentioned method embodiment, and the program can be loaded and run by the processor to implement the above-mentioned cross-platform software development method. For ease of explanation, only the parts related to the embodiment of the present application are shown. For specific technical details not disclosed, please refer to the method part of the embodiment of the present application. The computer-readable storage medium can be a memory device formed by various electronic devices. Optionally, the computer-readable storage medium in the embodiment of the present application is a non-temporary computer-readable storage medium.

[0143] So far, the technical solutions of the present application have been described in conjunction with the specific implementations shown in the accompanying drawings, but it is easy for those skilled in the art to understand that the protection scope of the present application is obviously not limited to these specific implementations. Without departing from the principles of the present application, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present application.

Claims

1. A cross-platform software development method, characterized in that: The method comprises: Get the system type of the target platform; Configuring a compilation environment based on the system type; Create the target project; Acquire a library file corresponding to the system type based on the compilation environment and the target project; The library file is published to a preset warehouse, so that a target application is obtained based on the library file.

2. The cross-platform software development method according to claim 1, characterized in that: The configuring the compilation environment based on the system type includes: Install the Rust compiler; Install the Rust toolchain based on the system type.

3. The cross-platform software development method according to claim 1, characterized in that: The creating of the target project includes: Get a code editor; Using the code editor to create a target project; Write Rust code for the target project to obtain the target project project.

4. The cross-platform software development method according to claim 1, characterized in that: The acquiring of a library file corresponding to the system type based on the compilation environment and the target project includes: Compile the target project using the Rust compiler in the compilation environment to obtain a binary file corresponding to the target project; The binary file is packaged to obtain a library file corresponding to the system type.

5. The cross-platform software development method according to claim 4, characterized in that: The Rust tool chain includes any one of the cargo-ndk tool and the cargo-lipo tool; Packaging the binary file includes: When the system type is Android, packaging the binary file based on the cargo-ndk tool to obtain a library file corresponding to the system type; When the system type is IOS, packaging the binary file based on the cargo-li po tool to obtain a library file corresponding to the system type; When the system type is HarmonyOS, a Clang link script is configured, and the binary file is packaged based on the configured Clang link script to obtain a library file corresponding to the system type.

6. The cross-platform software development method according to claim 1, characterized in that: Publishing the library file to a preset warehouse includes: Create integrated modules; Integrate the library file into the integration module; The integration module is published to the preset warehouse.

7. The cross-platform software development method according to claim 6, characterized in that: The creation of the integrated module comprises: When the system type is Android, using Android Studio to create the integration module; When the system type is IOS, using Xcode to create the integration module; When the system type is HarmonyOS, Dev-Echo is used to create the integrated module.

8. The cross-platform software development method according to claim 6, characterized in that: The step of publishing the integration module to the preset warehouse includes: When the system type is Android, publishing the integration module to a Maven repository; When the system type is IOS, publishing the integration module to a Git server; When the system type is HarmonyOS, the integrated module is published to a preset warehouse.

9. A computer device, characterized in that: include: at least one processor; and, a memory communicatively coupled to the at least one processor; The memory stores a computer program, and when the computer program is executed by the at least one processor, the cross-platform software development method according to any one of claims 1 to 8 is implemented.

10. A computer-readable storage medium storing a plurality of program codes, characterized in that: The program code is suitable for being loaded and run by a processor to execute the cross-platform software development method according to any one of claims 1 to 8.

Images