为了生成一个约8MB大小的installable OpenWrt固件镜像文件，您需要：

1. 在您的操作系统上安装OpenWrt构建系统及其先决条件。
2. 大约3-4 GB的空余硬盘空间
3. 环境变量：
   • 不应设置SED。如已设置，在编译前执行`unset SED`。(参见Ticket 10612.)
   • GREP_OPTIONS不应使用–initial-tab或其它会影响其输出的选项
   • 在您~/.bashrc文件中的PATH变量中，将<buildroot dir>/staging_dir/host/bin and <buildroot dir>/staging_dir/toolchain-<platform>-<gcc_ver>-<libc_ver>/bin放在最前。构建开始后很快就会创建staging目录不久创建，而toolchain目录将在toolchain构建开始时创建。构建过程将创建多个子shell，其中会有一些需要toolchain可执行文件设置于PATH变量中.

1. 以非root用户来进行工作 2. 在<buildsystem root>目录中完成所有命令，例如~/openwrt/trunk/

1. 更新OpenWrt源。
2. 更新feeds的package 包.
3. 配置编译。
4. 开始编译。这会自动编译工具链，交叉编译源代码，打包包文件，最后生成可以可以刷写的镜像文件。
5. 进入安装OpenWrt环节

如果您想签出主干代码，使用如下命令：

git clone https://www.github.com/openwrt/openwrt

如果您想签出某个发布版源码，使用如下命令：

git clone https://www.github.com/openwrt/openwrt -b chaos_calmer

(请于Github上验证发布版名称.)

OpenWrt源码变动频繁。建议总是使用最新的源码进行工作。

git pull

更新源:

./scripts/feeds update -a

安装下载好的包: (可选)

./scripts/feeds install -a   (或者 'install <PACKAGENAME>' )

开始OpenWrt Buildroot基于ncurses的 文本配置界面:

make menuconfig

• 这个菜单允许你选择目标平台，也就是你想要用来编译你要包含进固件镜像的软件包的工具链(toolchain)的版本。

• 在更新源码和源以后运行这个配置界面，确保你的配置中包含的软件包是最新的。

在启用默认配置以前先选择的你的目标平台

make defconfig

Menuconfig拥有一个文本界面，它包括选择要处理的目标平台，要编译的软件包，要被包含进固件文件的软件包和一些内核设置等。

make menuconfig

这会自动更新你现在存在的配置的依赖，方便你你准备编译你更新过的镜像。

It has from the beginning on been the intention, with the development of 'menuconfig', to create a simple yet powerful environment for the configuration of individual OpenWrt images. Menuconfig is more or less self-explanatory, and even the most specialized configuration needs can be solved with its help. Depending on the the particular target platform, package requirements and kernel module needs, the standard process of configuration will include modifying:

1. 目标系统
2. 软件包设定
3. 系统构建设定
4. 内核模块

Target system is selected from the extensive list of supported platforms, with the numerous target profiles – ranging from specific devices to generic profiles, all depending on the particular device at hand. Package selection has the option of either 'selecting all package', which might be un-practical in certain situation, or relying on the default set of packages will be adequate or make an individual selection. It is here needed to mention that some package combinations might break the build process, so it can take some experimentation before the expected result is reached. Added to this, the OpenWrt developers are themselves only maintaining a smaller set of packages – which includes all default packages – but, the feeds-script makes it very simple to handle a locally maintained set of packages and integrate them in the build-process.

这儿有三种选项可选：

• < > 该代码将不会被编译
• <M> 该代码将被交叉编译，生成的ipk软件包将被放在 /buildsystem/bla/bla/bla, 但该软件包不会放入固件中
• <*> 该代码将被放入固件中 (on the SqashFS partition)

The final step before the process of compiling the intended image(s) is to exit 'menuconfig' – this also includes the option to save a specific configuration or load an already existing, and pre-configured, version.

Exit the TUI, and choose to save your settings.

While you won't typically need to do this, you can do it:

make kernel_menuconfig

See: Customizing the kernel options

The 'Build system settings' include some efficient options for changing package locations which makes it easy to handle a local package set:

1. Local mirror for source packages
2. Download folder

In the case of the first option, you simply enter a full URL to the web or ftp server on which the package sources are hosted. Download folder would in the same way be the path to a local folder on the build system (or network). If you have a web/ftp-server hosting the tarballs, the OpenWrt build system will try this one before trying to download from the location(s) mentioned in the Makefiles . Similar if a local 'download folder', residing on the build system, has been specified.

The 'Kernel modules' option is required if you need specific (non-standard) drivers and so forth – this would typically be things like modules for USB or particular network interface drivers etc.

在很多情况下，您可能需要使用自己准备好的配置去创建一个自己定制的固件，如果是这样，请把您的配置文件放在下面的路径：

<buildroot dir>/files/

举例：假如说您需要一个使用预配置文件/etc/config/firewall来构建固件，那么把您的firewall配置文件文件放到下面的路径：

<buildroot dir>/files/etc/config

为构建镜像，一切已就绪。现只需一条命令:

make

或者：

make world

该命令会触发一连串的活动。之前也说过，它将会：

1. 编译工具链
2. 然后用这个工具链交叉编译源文件
3. 创建opkg软件包
4. 创建可随时刷机的镜像。

可通过-j选项启用多个进程以加速构建过程：

make -j 3

• 使用标准公式 <你的CPU个数 + 1>
• 构建过程中若产生随机错误，尝试去掉-j选项重新构建

如果你想在构建时干别的，你可以让构建进程只使用闲置的CPU和I/O资源（双核CPU）：

ionice -c 3 nice -n 20 make -j 2

为OpenWrt开发或打包软件时，可以方便地只构建关心的包（以cups包为例）：

make package/cups/compile V=99

For the package mc (midnight commander), which is contained the feed packages it looks like this:

make package/feeds/packages/mc/compile v=99

如果构建不知怎么搞的出错了，亮出错误的最简单方式是：

make V=99 2>&1 | tee build.log | grep -i error

以上命令会保存一份详尽的编译输出（同时把stdout泵至stderr）到/openwrt/trunk/build.log，并只在屏幕上输出错误。

另一个例子：

ionice -c 3 nice -n 20 make -j 2 V=99 CONFIG_DEBUG_SECTION_MISMATCH=y 2>&1 | tee build.log | egrep -i '(warn|error)'

再来一个例子：

somthing something screen

以上命令会保存一份详尽的编译输出（同时把stdout泵至stderr）到build.log，并只在屏幕上输出警告和错误，且在双核CPU上只使用后台资源。

取决于你的CPU，构建过程可能要花上很久、或更久的时间。如果你想要提示音，可使用echo -e '\a':

make V=99 ; echo -e '\a'

编译成功后的固件bin文件在 /openwrt/trunk/bin 目录下.

cd ~/openwrt/trunk/bin
ls */

You might need to clean your build environment every now and then. The following make-targets are useful for that job:

make clean

deletes contents of bin and build_dir directories.

make dirclean

deletes contents of /bin and /build_dir directories and additionally /staging_dir and /toolchain (=the cross-compile tools). 'Dirclean' is your basic "Full clean" operation.

make distclean

nukes everything you have compiled or configured and also deletes all downloaded feeds contents and package sources.

CAUTION: In addition to all else, this will erase your build configuration (.config), your toolchain and all other sources. Use with care!

There are numerous other functionalities in the OpenWrt build system, but the above should have covered some of the fundamentals.

• https://forum.openwrt.org/viewtopic.php?pid=129319#p129319
• https://forum.openwrt.org/viewtopic.php?id=28267

First get more information on the problem using the make option "make V=99".

• Missing source code file, due to download problems.

First check if the URL path in the make file contains a trailing slash, then try with it removed (helped several times). Otherwise try to download the source code manually and put it into "dl" directory

• Compilation errors.

Try to update the main source and all the feeds (Warning! May result in other problems). Check for a related bug in (TRAC), use the filters to find it. Otherwise report the problem there, by mentioning the package, the target data (CPU, image, etc.) and the code revisions (main & package). Compiling with make -j … sometimes gives random errors. Try compiling without -j first before reporting the problem.

• OpenWrt Buildroot – Technical Reference
• http://downloads.openwrt.org/docs/buildroot-documentation.html
• https://dev.openwrt.org/browser/trunk/docs/working.tex