CN117251165B - Buildroot compilation method, device, terminal and medium - Google Patents

Abstract

The present invention provides a Buildroot compilation method, device, terminal and medium, by first saving all Buildroot dependency packages of the latest version downloaded, and then adapting each Buildroot dependency package required by the code involved in the compilation, so as to designate the address path for obtaining the Buildroot dependency package during the compilation process as the preset address path, and finally cross-compile each Buildroot dependency package involved in the compilation according to the preset address path. The present invention does not need to download dependency packages, so the dependency packages will not be incompletely downloaded due to network problems, and time is greatly saved, and the integrity of the dependency packages is guaranteed and the compilation is stable.

Description

Buildroot compilation method, device, terminal and medium

Technical Field

The present invention relates to the field of computer technology, and in particular to a Buildroot compilation method, device, terminal and medium.

Background technique

Buildroot is an open source automatic build framework for embedded Linux systems on the Linux platform. The entire Buildroot is composed of Makefile scripts and Kconfig configuration files. Just like compiling the Linux kernel, you can compile a complete Linux system software that can be directly burned to the machine and run by configuring buildroot and modifying menuconfig.

Buildroot will download a large number of dependency packages during the build process. If the network is unstable, the download of dependency packages will be interrupted or inaccessible. If the dependency packages are not downloaded completely and are compiled one by one, the compilation will appear to be successful, but the actual compilation will fail, which will also waste a lot of time.

Summary of the invention

In view of the above-mentioned shortcomings of the prior art, an object of the present invention is to provide a Buildroot compilation method, device, terminal and medium to solve the above-mentioned prior art problems.

To achieve the above-mentioned object and other related objects, the present invention provides a Buildroot compilation method, the method comprising: saving all Buildroot dependency packages of the latest version downloaded, and correspondingly defining a preset address path; adapting each Buildroot dependency package required by the code involved in the compilation, so that the address path for obtaining the Buildroot dependency package during the compilation process is designated as the preset address path; and cross-compiling each Buildroot dependency package involved in the compilation according to the preset address path.

In one embodiment of the present invention, adapting each Buildroot dependency package involved in the compilation includes: determining whether the version of each Buildroot dependency package required by the code involved in the compilation is correct; if the version is correct, removing the download information used to download the corresponding Buildroot dependency package during the compilation process; and setting the address path for obtaining the corresponding Buildroot dependency package during the compilation process to the preset address path.

In one embodiment of the present invention, determining whether the versions of each Buildroot dependency package required for the code involved in the compilation are correct includes: determining each Buildroot dependency package required for the code involved in the compilation among all saved Buildroot dependency packages; judging whether the versions of each determined Buildroot dependency package meet the Buildroot dependency package version required for the code compilation; if so, the version is correct; if not, the version is incorrect and the latest version of the Buildroot dependency package needs to be downloaded again.

In one embodiment of the present invention, removing the download information corresponding to the download of the Buildroot dependency package during the compilation process includes: removing the download information of each Buildroot dependency package required for the corresponding download in the code, and removing the download information of the corresponding download of the associated Buildroot dependency package in each required Buildroot dependency package.

In one embodiment of the present invention, setting the address path corresponding to obtaining the Buildroot dependency package during the compilation process as the preset address path includes: setting the address path in the code for obtaining each required Buildroot dependency package and the address path in each Buildroot dependency package for obtaining the associated Buildroot dependency package to the preset address path.

In one embodiment of the present invention, the method of setting the address path in each Buildroot dependency package for obtaining the associated Buildroot dependency package as the preset address path includes: setting the address paths of the Buildroot dependency packages required for obtaining the patch files, compilation files, and installation files in the Buildroot dependency package to the preset address paths, respectively.

To achieve the above-mentioned purpose and other related purposes, the present invention provides a Buildroot compilation device, which includes: a dependency package saving module, used to save all Buildroot dependency packages of the latest version downloaded, and define a preset address path accordingly; a dependency package adaptation module, connected to the dependency package saving module, used to adapt each Buildroot dependency package required by the code involved in the compilation, so that the address path of the Buildroot dependency package obtained during the compilation process is specified as the preset address path; a compilation module, connected to the dependency package adaptation module, used to cross-compile each Buildroot dependency package involved in the compilation according to the preset address path.

In one embodiment of the present invention, the dependency package adaptation module includes: a version determination unit, used to determine whether the version of each Buildroot dependency package required by the code involved in the compilation is correct; a download information removal unit, connected to the version determination unit, used to remove the download information used to download the corresponding Buildroot dependency package during the compilation process when the version is correct; an address path setting unit, connected to the download information removal unit, used to set the address path corresponding to obtaining the Buildroot dependency package during the compilation process to the preset address path.

To achieve the above-mentioned object and other related objects, the present invention provides a Buildroot compilation terminal, comprising: one or more memories and one or more processors; the one or more memories are used to store computer programs; the one or more processors are connected to the memories and are used to run the computer program to execute the Buildroot compilation method.

To achieve the above objectives and other related objectives, the present invention provides a computer-readable storage medium storing a computer program, wherein the computer program executes the Buildroot compilation method when executed by one or more processors.

As described above, the present invention is a Buildroot compilation method, device, terminal and medium, which has the following beneficial effects: the present invention first saves all the Buildroot dependency packages of the latest version downloaded, and then adapts the Buildroot dependency packages required by the code involved in the compilation, so as to specify the address path for obtaining the Buildroot dependency package during the compilation process as the preset address path, and finally cross-compiles the Buildroot dependency packages involved in the compilation according to the preset address path. The present invention does not need to download dependency packages, so the dependency packages will not be incompletely downloaded due to network problems, and it also greatly saves time, ensures the integrity of the dependency packages and stable compilation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic flow chart of a Buildroot compilation method according to an embodiment of the present invention.

FIG. 2 is a flow chart showing a conventional Buildroot compilation method.

FIG. 3 is a schematic diagram showing a flow chart of a Buildroot compilation method in an embodiment of the present invention.

FIG. 4 is a schematic diagram showing the structure of a Buildroot compilation system in an embodiment of the present invention.

FIG. 5 is a schematic diagram showing the structure of a dependency package adaptation module in an embodiment of the present invention.

FIG. 6 is a schematic diagram showing the structure of a Buildroot compilation terminal in an embodiment of the present invention.

Detailed ways

The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

It should be noted that in the following description, reference is made to the accompanying drawings, which describe several embodiments of the present invention. It should be understood that other embodiments may also be used, and that mechanical composition, structural, electrical and operational changes may be made without departing from the spirit and scope of the present invention. The following detailed description should not be considered restrictive, and the scope of the embodiments of the present invention is limited only by the claims of the published patents. The terms used here are only for describing specific embodiments and are not intended to limit the present invention. Spatially related terms, such as "upper", "lower", "left", "right", "below", "below", "lower", "above", "upper", etc., may be used in the text to facilitate the description of the relationship between an element or feature shown in the figure and another element or feature.

Throughout the specification, when a part is said to be "connected" to another part, this includes not only the case of "direct connection" but also the case of "indirect connection" by placing other elements therebetween. In addition, when a part is said to "include" a certain constituent element, unless otherwise stated, it does not exclude other constituent elements, but means that other constituent elements may be included.

The terms first, second and third are used to describe various parts, components, regions, layers and/or segments, but are not limited thereto. These terms are only used to distinguish a certain part, component, region, layer or segment from other parts, components, regions, layers or segments. Therefore, the first part, component, region, layer or segment described below may refer to the second part, component, region, layer or segment within the scope of the present invention.

Furthermore, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless there is an indication to the contrary in the context. It should be further understood that the terms "comprise", "include" indicate the presence of the described features, operations, elements, components, items, kinds, and/or groups, but do not exclude the presence, occurrence or addition of one or more other features, operations, elements, components, items, kinds, and/or groups. The terms "or" and "and/or" used herein are interpreted as inclusive, or mean any one or any combination. Therefore, "A, B or C" or "A, B and/or C" means "any of the following: A; B; C; A and B; A and C; B and C; A, B and C". Exceptions to this definition will only occur when the combination of elements, functions or operations is inherently mutually exclusive in some way.

The present invention provides a Buildroot compilation method, by first saving all Buildroot dependency packages of the latest version downloaded, and then adapting each Buildroot dependency package required by the code involved in the compilation, so as to designate the address path for obtaining the Buildroot dependency package during the compilation process as the preset address path, and finally cross-compile each Buildroot dependency package involved in the compilation according to the preset address path. The present invention does not need to download dependency packages, so the dependency packages will not be incompletely downloaded due to network problems, and time is greatly saved, and the integrity of the dependency packages is guaranteed and the compilation is stable.

At the same time, in order to make the purpose, technical solution and advantages of the present invention more clear, the technical solution in the embodiment of the present invention is further described in detail through the following embodiments and in combination with the accompanying drawings. It should be understood that the specific embodiments described here are only used to explain the present invention and are not used to limit the invention.

Before further describing the present invention in detail, the nouns and terms involved in the embodiments of the present invention are explained. The nouns and terms involved in the embodiments of the present invention are applicable to the following interpretations:

<1>Build: It is to recompile the entire project completely, regardless of whether it has been compiled before. The build process often generates a release package, which depends on the configuration of the IDE. Build is rarely used in practice because it is basically not used during development. When releasing to production, it is generally released using tools such as ANT.

<2>Buildroot: It is an open source automatic build framework for embedded Linux systems on the Linux platform. The entire Buildroot is composed of Makefile scripts and Kconfig configuration files. Just like compiling the Linux kernel, you can compile a complete Linux system software (including boot, kernel, rootfs, and various libraries and applications in rootfs) that can be directly burned to the machine and run through buildroot configuration and menuconfig modification.

<3> Compilation: Translate a program compiled in a certain programming language into executable code or program described in binary language.

<4> Cross-compilation: It can be understood that the program compiled on the current compilation platform can run on another target platform with a different architecture.

<5> Makefile: The makefile describes the compilation order and compilation rules of all files in the entire project. Makefile also has its own writing rules. Usually, the IDE we use will generate the corresponding makefile, and then compile according to the makefile, but these operations are completed by the IDE, and we only need to click a compile button.

<6>Kconfig: It is a text file, which is mainly used as a configuration option to configure various configuration interface source files during kernel configuration.

<7>menuconfig: is a graphical configuration interface that can be displayed on the terminal. It not only greatly facilitates our modification of configuration files, but also automatically handles dependencies.

The following is a detailed description of the embodiments of the present invention with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention. The present invention can be embodied in many different forms and is not limited to the embodiments described herein.

FIG1 is a schematic diagram showing a flow chart of a Buildroot compilation method according to an embodiment of the present invention.

The method comprises:

Step S1: Save all Buildroot dependency packages of the latest version downloaded, and define a preset address path accordingly.

Specifically, connect to the network, download the latest version of all Buildroot dependency packages, save them in your own project, and define a preset address path for the save location. Among them, Buildroot dependency packages are software packages that Buildroot relies on during the compilation process, such as some library files, including static libraries and dynamic libraries.

Step S2: adapting each Buildroot dependency package required by the code involved in the compilation, so as to designate the address path for obtaining the Buildroot dependency package during the compilation process as the preset address path.

In one embodiment, step S2 includes:

Determine whether the versions of the Buildroot dependency packages required by the compiled code are correct;

If the version is correct, remove the download information for downloading the corresponding Buildroot dependency package during the compilation process;

The address path for obtaining the Buildroot dependency package during the compilation process is set to the preset address path.

In the above manner, the address path for obtaining the Buildroot dependency package during the compilation process can be specified as the preset address path.

In a specific embodiment, determining whether the versions of the Buildroot dependency packages required by the compiled code are correct includes:

Determine the Buildroot dependency packages required for the compiled code from all the saved Buildroot dependency packages; specifically, pull the required Buildroot dependency packages from all the saved Buildroot dependency packages;

Determine whether the versions of the determined Buildroot dependency packages meet the Buildroot dependency package versions required for code compilation; specifically, determine whether the versions of the pulled Buildroot dependency packages meet the Buildroot dependency package versions required for code compilation; the determination method may be to determine by the version number of the dependency package or the identifier of the dependency package.

If it matches, the version is correct and you can proceed to the next step;

If they do not match, the version is incorrect and you need to re-download the latest version of the Buildroot dependency package, save it, and re-determine the Buildroot dependency package and version.

In a specific embodiment, removing the download information for downloading the corresponding Buildroot dependency package during the compilation process includes:

Remove the download information of each Buildroot dependency package required for download in the code, and remove the download information of the corresponding Buildroot dependency package in each required Buildroot dependency package.

Specifically, the removed download information is mainly divided into two parts: one is to remove the download information of each Buildroot dependency package that needs to be downloaded during the compilation process in the code; and because each Buildroot dependency package may also depend on other Buildroot dependency packages, it is also necessary to remove the download addresses of other associated Buildroot dependency packages that need to be downloaded when the corresponding Buildroot dependency package is compiled in each Buildroot dependency package, that is, remove another part; for example, dependency package A also depends on dependency packages B and C, then the download information of dependency packages B and C needs to be removed from the dependency package.

Based on the above method, the steps of downloading each Buildroot dependency package when compiling the code and downloading other Buildroot dependency packages when compiling the Buildroot dependency package are skipped and will not be executed.

In a specific embodiment, setting the address path corresponding to obtaining the Buildroot dependency package during the compilation process to the preset address path includes: setting the address path in the code for obtaining each required Buildroot dependency package and the address path in each Buildroot dependency package for obtaining the associated Buildroot dependency package to the preset address path.

Specifically, based on the above-mentioned removal of download information, which is mainly divided into two parts, setting the address path is also divided into two parts: one is to set the address path in the code for obtaining the required Buildroot dependency packages to the preset address path, so that the code can directly obtain the required Buildroot dependency packages based on the preset address path during the compilation process; the other is to set the address path in each Buildroot dependency package for obtaining the Buildroot dependency package associated therewith to the preset address path, that is, during the compilation process of the Buildroot dependency package, the corresponding Buildroot dependency package can obtain the corresponding dependent Buildroot dependency package through the preset address path.

In a preferred embodiment, each Buildroot dependency package includes: a patch file (patch), a compile file (compile) and an installation file (install); wherein the patch file is used for patching, and may depend on other Buildroot dependency packages during the patching process; the compile file is used for compilation, and may depend on other Buildroot dependency packages during the compilation process; the installation file is used for installation, and may depend on other Buildroot dependency packages during the installation process.

The manner of setting the address path in each Buildroot dependency package for obtaining the associated Buildroot dependency package as the preset address path includes: setting the address paths of the Buildroot dependency packages required for obtaining the patch files, the compiled files, and the installation files in the Buildroot dependency package as the preset address paths, respectively.

Thus, it can be achieved that when patching the Buildroot dependency package, the dependent Buildroot dependency package can be obtained from the preset address path to complete the patching; when compiling the Buildroot dependency package, the dependent Buildroot dependency package can be obtained from the preset address path to complete the compilation work; when installing, the dependent Buildroot dependency package can be obtained from the preset address path to complete the installation work.

Step S3: cross-compile each Buildroot dependent package involved in the compilation according to the preset address path.

Specifically, during the compilation process, first, the various Buildroot dependency packages required for the code involved in the compilation are obtained according to the preset address path, and then the various Buildroot dependency packages are cross-compiled. When the Buildroot dependency package is compiled, the corresponding dependent Buildroot dependency package is obtained through the preset address path, thereby completing the Buildroot compilation.

Therefore, the Buildroot compilation of the present invention does not need to download dependency packages, and the required Buildroot dependency packages can be directly obtained from the location where the downloaded Buildroot dependency packages are saved in advance through a preset address path. Even if the network environment is unstable, it will not cause incomplete download of the dependency packages, and it reduces the download time and improves the compilation efficiency.

In order to better describe the Buildroot compilation method, the following specific examples are provided for illustration;

Embodiment 1: A Buildroot compilation method.

As shown in FIG2 , the existing Buildroot compilation method usually downloads a large number of dependency packages and then cross-compiles the Buildroot dependency packages. This may easily cause the download of dependency packages to be interrupted or inaccessible when the network is unstable, and compilation may fail if the dependency packages are not completely downloaded.

The Buildroot compilation method of this embodiment does not need to download dependent packages before compilation. As shown in FIG3 , the method includes:

Step 1: Copy the dependency package downloaded previously.

Connect to the Internet, download the Buildroot dependency package, and save it in your own project.

Step 2: Adaptation of dependency packages.

First, determine whether the version of the Buildroot dependency package is correct; if the version is correct, remove the downloaded part of the Buildroot dependency package; finally, set the address path of the Buildroot dependency package to the save address of the Buildroot dependency package; the address path that needs to be set for the corresponding Buildroot dependency package: including the address path of the Buildroot dependency package in patch, compile and install.

Step 3: Cross-compile between dependent packages.

Compile the Buildroot dependency packages in order according to the set new address path.

Similar to the principle of the above embodiment, the present invention provides a Buildroot compilation device.

The following provides specific embodiments in conjunction with the accompanying drawings:

FIG4 is a schematic diagram showing the structure of a Buildroot compilation device according to an embodiment of the present invention.

The device comprises:

Dependency package saving module 1 is used to save all Buildroot dependency packages of the latest version downloaded, and define a preset address path accordingly;

The dependency package adaptation module 2 is connected to the dependency package storage module 1 and is used to adapt each Buildroot dependency package required by the code involved in the compilation, so as to specify the address path of the Buildroot dependency package obtained during the compilation process as the preset address path;

Compilation module 3 is connected to the dependency package adaptation module and is used to cross-compile each Buildroot dependency package involved in the compilation according to the preset address path.

It should be noted that it should be understood that the division of the modules in the system embodiment of FIG. 4 is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or physically separated. Moreover, these modules can be all implemented in the form of software calling through processing elements; or all implemented in the form of hardware; or some modules can be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware;

For example, each module may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASIC), or one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a module above is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

Since the implementation principle of the Buildroot compilation device has been described in the above embodiments, it will not be repeated here.

In one embodiment, as shown in Figure 5, the dependency package adaptation module 2 includes: a version determination unit 21, used to determine whether the version of each Buildroot dependency package required by the code involved in the compilation is correct; a download information removal unit 22, connected to the version determination unit 21, used to remove the download information used to download the corresponding Buildroot dependency package during the compilation process when the version is correct; an address path setting unit 23, connected to the download information removal unit 22, used to set the address path corresponding to obtaining the Buildroot dependency package during the compilation process to the preset address path.

In one embodiment, the version determination unit 21 is used to determine the Buildroot dependency packages required by the code involved in the compilation among all the saved Buildroot dependency packages; judge whether the versions of the determined Buildroot dependency packages meet the Buildroot dependency package versions required for the code compilation; if they meet, the version is correct; if not, the version is incorrect and the latest version of the Buildroot dependency package needs to be downloaded again.

In one embodiment, the download information removing unit 22 is used to remove the download information of each Buildroot dependency package required for downloading in the code, and to remove the download information of the corresponding download associated Buildroot dependency package in each required Buildroot dependency package.

In one embodiment, the address path setting unit 23 is used to set the address path in the code for obtaining each required Buildroot dependency package and the address path in each Buildroot dependency package for obtaining the associated Buildroot dependency package as the preset address path.

In one embodiment, the method of setting the address path in each Buildroot dependency package for obtaining the associated Buildroot dependency package to the preset address path includes: setting the address paths of the Buildroot dependency packages required for obtaining the patch files, compiled files, and installation files in the Buildroot dependency package to the preset address paths, respectively.

FIG6 is a schematic diagram showing the structure of the Buildroot compilation terminal in an embodiment of the present invention.

The Buildroot compilation terminal 100 includes: a memory 101 and a processor 102. The memory 101 is used to store computer programs; the processor 102 runs the computer programs to implement the Buildroot compilation method as shown in FIG1 .

Optionally, the number of the memories 101 may be one or more, and the number of the processors 102 may be one or more, but FIG. 6 takes one as an example.

Optionally, the processor 102 in the Buildroot compilation terminal 100 will load one or more instructions corresponding to the application process into the memory 101 according to the steps described in Figure 1, and the processor 102 will run the application stored in the first memory 101, thereby realizing various functions in the Buildroot compilation method described in Figure 1.

Optionally, the memory 101 may include but is not limited to high-speed random access memory and non-volatile memory. For example, one or more disk storage devices, flash memory devices or other non-volatile solid-state storage devices; the processor 102 may include but is not limited to a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

Optionally, the processor 102 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

The present invention also provides a computer-readable storage medium storing a computer program, wherein the computer program implements the Buildroot compilation method shown in FIG1 when it is run. The computer-readable storage medium may include, but is not limited to, a floppy disk, an optical disk, a CD-ROM (Compact Disc Read Only Memory), a magneto-optical disk, a ROM (Read Only Memory), a RAM (Random Access Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory), a magnetic card or an optical card, a flash memory, or other types of media/machine-readable media suitable for storing machine-executable instructions. The computer-readable storage medium may be a product that is not connected to a computer device, or a component that is connected to a computer device for use.

In summary, the Buildroot compilation method, device, terminal and medium of the present invention, by first saving all the latest version of the downloaded Buildroot dependency packages, and then adapting each Buildroot dependency package required for the code involved in the compilation, so as to obtain the address path of the Buildroot dependency package during the compilation process as the preset address path, and finally cross-compile each Buildroot dependency package involved in the compilation according to the preset address path. The present invention does not need to download the dependency package, so it will not cause the dependency package to be incompletely downloaded due to network problems, and it also greatly saves time, ensures the integrity of the dependency package and stable compilation. Therefore, the present invention effectively overcomes the various shortcomings in the prior art and has a high industrial utilization value.

The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present invention. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed by the present invention shall still be covered by the claims of the present invention.

Claims (6)

1. A Buildroot compilation method, characterized in that the method comprises: Save all the Buildroot dependency packages of the latest version downloaded, and define a preset address path accordingly; Adapting each Buildroot dependency package required by the code involved in the compilation, so as to specify the address path for obtaining the Buildroot dependency package during the compilation process as the preset address path; According to the preset address path, cross-compile each Buildroot dependency package involved in the compilation; Among them, the adaptation of each Buildroot dependency package involved in the compilation includes: Determine whether the versions of the Buildroot dependency packages required by the compiled code are correct; If the version is correct, remove the download information for downloading the corresponding Buildroot dependency package during the compilation process; which includes: removing the download information of each Buildroot dependency package required for downloading during the compilation process in the code, and removing the download information of the corresponding Buildroot dependency package in each required Buildroot dependency package; The address path corresponding to the Buildroot dependency package obtained during the compilation process is set to the preset address path; wherein, it includes: setting the address path in the code for obtaining each required Buildroot dependency package and the address path in each Buildroot dependency package for obtaining the associated Buildroot dependency package to the preset address path. 2. The Buildroot compilation method according to claim 1, wherein determining whether the versions of the Buildroot dependency packages required by the compiled code are correct comprises: Determine the Buildroot dependency packages required for the compiled code among all the saved Buildroot dependency packages; Determine whether the versions of each Buildroot dependency package determined meet the Buildroot dependency package versions required for code compilation; If they match, the version is correct; If they do not match, the version is incorrect and you need to re-download the latest version of the Buildroot dependency package. 3. The Buildroot compilation method according to claim 1, wherein the method of setting the address path for obtaining the associated Buildroot dependency package in each Buildroot dependency package to the preset address path comprises: The address paths of the Buildroot dependency packages required for obtaining the patch files, the compiled files, and the installation files in the Buildroot dependency packages are respectively set as the preset address paths. 4. A Buildroot compilation device, characterized in that the device comprises: The dependency package saving module is used to save all the Buildroot dependency packages of the latest version downloaded, and define a preset address path accordingly; A dependency package adaptation module, connected to the dependency package storage module, is used to adapt each Buildroot dependency package required by the code involved in the compilation, so as to specify the address path of the Buildroot dependency package obtained during the compilation process as the preset address path; A compilation module, connected to the dependency package adaptation module, is used to cross-compile each Buildroot dependency package involved in the compilation according to the preset address path; Wherein, the dependency package adaptation module includes: The version determination unit is used to determine whether the versions of the Buildroot dependency packages required by the compiled code are correct; A download information removal unit, connected to the version determination unit, is used to remove the download information for downloading the corresponding Buildroot dependency package during the compilation process when the version is correct; wherein, the download information of each Buildroot dependency package required for downloading in the code during the compilation process is removed, and the download information of the corresponding Buildroot dependency package in each required Buildroot dependency package is removed respectively; An address path setting unit is connected to the download information removal unit and is used to set the address path for obtaining the Buildroot dependency package during the compilation process to the preset address path; wherein, it includes: setting the address path in the code for obtaining each required Buildroot dependency package and the address path in each Buildroot dependency package for obtaining the associated Buildroot dependency package to the preset address path. 5. A Buildroot compilation terminal, characterized by comprising: one or more memories and one or more processors; The one or more memories are used to store computer programs; The one or more processors, connected to the memory, are configured to run the computer program to perform the method according to any one of claims 1 to 3. 6. A computer-readable storage medium, characterized in that a computer program is stored therein, wherein the computer program, when executed by one or more processors, performs the method according to any one of claims 1 to 3.