Openwrt (1) -- Introduction to openwrt buildroot

Openwrt (1)-Introduction to openwrt buildroot: http://wiki.openwrt.org/about/toolchainbuildrootbefore talking about openwrt buildroot, let's first talk about buildroot. Buildroot is actually a compiled script, which includes a set of makefiles and patch files. It is mainly used for compiling simple systems or embedded systems and supports multiple CPU architectures, these include x86, arm, MIPS, and PowerPC. It can generate tool chains for cross-compilation, file systems, kernel images, and bootloader images. Related content can go to the buildroot home page to view the http://www.buildroot.orgOpenWRT buildroot introduction so openwrt buildroot is what to play? It is actually a buildroot, but it is a script for compiling the openwrt system specially for compiling openwrt. As for why it is called openwrt buildroot, it is because when openwrt is transplanted, A lot of modifications have been made! The main task of openwrt buildroot is to generate a cross-compilation chain and a file system. The cross-compilation tool chain is a set of cross-compilation tools that can compile source code files for your target system. So why is it called the cross-compilation tool chain? Because most of the embedded or micro-small systems do not put the compilation tool chain into the system due to CPU or flash restrictions or avoiding waste. Of course, the exception of X86 is, hey. How can I compile my code into an embedded system? We usually use specific tools on the X86 general Linux system to compile and generate code that can be executed by the target system and upload it to the target system. The specific compilation tool chain of this compilation platform and the target platform is the cross-compilation tool chain mentioned above. A cross-compilation tool chain consists of the compiler (GCC), binary tool binutils (assembler, linker, etc.), and standard C function library (GNU libc or uclibc ). It has two main features: 1. It can run on the X86 general-purpose CPU architecture; 2. It can compile and generate code for a specific CPU architecture (such as arm and MIPS. The standard C library used by the openwrt tool chain is uclibc, a small Standard C library designed for embedded systems. So even if we use the alix.2d2 board, this is also the x86 CPU. Using the openwrt system, what you compile on the X86 architecture Linux cannot run on openwrt. Okay, I admit it's a bit biased... The real identity of openwrt buildroot is the same as that of shoes. There is a vote on the Internet for GCC, binutils, and uclibc source code. Can I download it by myself and compile it by myself? The answer is yes, ~~ If you are not afraid of trouble (the original translation, foreigners are really good, understand the characteristics that everyone is afraid of trouble, and then enlarge it out ). We mentioned earlier that openwrt buildroot is a collection of many makefiles and patch files. It will automatically configure the source code for us, add known patches for each version, and finally generate IndeedAvailable cross-compilation tool chains. In addition, it can also generate a system. This proportion of space is not suitable. How can one of the two main tasks of openwrt buildroot be described so little? There is no way. The original text is in soy sauce... Finally, I would like to express my admiration for openwrt buildroot. Although openwrt buildroot is mainly intended for developers, end users who do not have the foundation of professional skills can also use it to compile and generate their own system firmware.