User Tools

Site Tools


使用镜像生成工具 (Image Builder)

Image Builder(以前称为Image Generator)是一个预编译环境,适用在不从源代码编译的情况创建自定义镜像文件。 它下载预编译的软件包并集成在一个可擦写的镜像中。


  • 您想在有限闪存中放入更多软件包。
  • 您想跟进用于开发的“快照版”。
  • 您的设备只有32MB或更低的内存,以至于opkg无法很好的工作。
  • 您想要将特殊定制的固件刷入大量设备。

实现相同目标的替代指南有: 使用Image Builder构建自己固件的入门指南


:!: Image Builder仅可运行在64位Linux环境下,您甚至可以在32位Windows系统的虚拟机(如virtualbox)中运行64位的Linux。
:!: Image Builder具有构建系统的一些相同先决条件Build system – Installation



apt-get install subversion build-essential libncurses5-dev zlib1g-dev gawk git ccache gettext libssl-dev xsltproc wget unzip python


yum install subversion git gawk gettext ncurses-devel zlib-devel openssl-devel libxslt wget
yum group install "Development Tools"

Fedora 27+

dnf install @c-development @development-tools @development-libs zlib-static which


您可以下载包含Image Builder的压缩文件,它通常在您找到设备固件映像文件的同一下载页面中。 例如,您在以下页面可以下载ar71xx/generic设备的所有固件映像文件:。在此页面,您也可以看到包含Image Builder的名为lede-imagebuilder-ar71xx-generic.Linux-x86_64.tar.xz的压缩文件。

当然,Image Builder也可以由构建系统生成,因为需要创建映像文件。如果启用了构建OpenWrt Image Builder选项,则Image Builder将在您找到固件映像的同一文件夹(source/bin/targets/xxx)中生成,您可以使用它从编译期间获得的软件包创建更多镜像文件。


您从OpenWrt页面下载的Image Builder已配置为不从官方存储库下载任何非默认软件包。 软件包源在解压目录中的repositories.conf文件中配置。源约定以opkg原生格式配置。这可以是官方软件包存储库,也可以是自定义生成的存储库。


## Place your custom repositories here, they must match the architecture and version.
# src/gz %n
# src custom file:///usr/src/openwrt/bin/ramips/packages

## Remote package repositories
src/gz openwrt_core
src/gz openwrt_base
src/gz openwrt_luci
src/gz openwrt_packages
src/gz openwrt_routing
src/gz openwrt_telephony

## This is the local package repository, do not remove!
src imagebuilder file:packages

您从源代码编译而来的Image Builderrepositories.conf缺少“Remote package repositories”链接.


src custom file:///usr/src/lede/bin/ramips/packages

并将其修改为指向您拥有软件包和软件包列表的本地文件夹。 如果您有在线的自定义存储库,请复制以下代码并替换修改:

src/gz reboot

line instead.


make image command will create a default image for a default device with default (essential) packages. In most cases it's not what you wanted.

To change this not-so-useful default behavior you can use three variables passed as arguments:

  • PROFILE - specifies the target image to build
  • PACKAGES - a list of packages to embed into the image
  • FILES - directory with custom files to include

Example syntax:

$ make image PROFILE=XXX PACKAGES="pkg1 pkg2 pkg3 -pkg4 -pkg5 -pkg6" FILES=files/

See the sections below for a more in-depth explanation. After the make command is finished, the generated images are stored in the bin/device-architecture directory, just like if you were compiling them.

here the output of make help:

Available Commands:
      help:   This help text
      info:   Show a list of available target profiles
      clean:  Remove images and temporary build files
      image:  Build an image (see below for more information).

Building images:
      By default 'make image' will create an image with the default
      target profile and package set. You can use the following parameters
      to change that:

      make image PROFILE="<profilename>" # override the default target profile
      make image PACKAGES="<pkg1> [<pkg2> [<pkg3> ...]]" # include extra packages
      make image FILES="<path>" # include extra files from <path>
      make image BIN_DIR="<path>" # alternative output directory for the images
      make image EXTRA_IMAGE_NAME="<string>" # Add this to the output image filename (sanitized)

The built image will be found under the subdirectory ./bin/targets/<target>/generic .

PROFILE Variable



Pre-defined Profiles

Run make info to obtain a list of defined profiles. Example output from make info is listed below.

ar71xx-generic Profiles
Available Profiles:

    Default Profile
    Packages: kmod-usb-core kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
    Aigale Ai-BR100
    Packages: kmod-usb2 kmod-usb-ohci
    Asus RP-N53
    Asus RT-N14u
    Buffalo WHR-1166D
    Buffalo WHR-300HP2
-and many many more-

After you find the appropriate profile pass it to the make image command:

For example, if we wanted to generate a default image for for Asus RT-N14u (from above).

$ make image PROFILE=rt-n14u


The PACKAGES variable allows to include and/or exclude packages in the firmware image. By default (empty PACKAGES variable) the Image Generator will create a minimal image with device-specific kernel and drivers, uci, ssh, switch, firewall, ppp and ipv6 support.


$ make image PACKAGES="pkg1 pkg2 pkg3 -pkg4 -pkg5 -pkg6"

The example above will include pkg1, pkg2, pkg3, and exclude pkg4, pkg5, pkg6, note the “-” before each excluded package.

You don't need to list all dependencies of the packages you need in this list, the Image Generator uses opkg to resolve automatically the package dependencies and install other required packages.

Tip: The list of currently installed packages on your device can be obtained with the command below:

echo $(opkg list_installed | awk '{ print $1 }')

FILES Variable

The FILES variable allows custom configuration files to be included in images built with Image Generator. This is especially useful if you need to change the network configuration from default before flashing, or if you are preparing an image for mass-flashing many devices.


$ make image FILES=files/

Note: The files/ folder must be in the same folder where you issue the make command.


The following example shows:

  1. Creating the directory for the configuration files
  2. Using scp to transfer uci configuration files from a WL500GP router to the files/etc/config directory
  3. Generating an image for WL500GP with custom packages and uci configuration files
mkdir -p files/etc/config
scp root@ files/etc/config/
scp root@ files/etc/config/
scp root@ files/etc/config/
make image PROFILE=wl500gp PACKAGES="nano openvpn -ppp -ppp-mod-pppoe" FILES=files/


您可以使用make clean命令来清除临时构建文件和已生成的镜像文件。


This is not a standard feature of the Image Builder.

Note that it requires patching of the Makefile

1. 创建一个包含了文件完整径名为'files_remove',如:


2. 给Makefile打补丁

 ifneq ($(USER_FILES),)
 	$(MAKE) copy_files
+ifneq ($(FILES_REMOVE),)
+	@echo
+	@echo Remove useless files
+	while read filename; do				\
+	    rm -rfv "$(TARGET_DIR)$$filename";	\
+	done < $(FILES_REMOVE);
 	$(MAKE) package_postinst
 	$(MAKE) build_image

3. 重构固件

# make image \
    PROFILE=tlwr841 \
    PACKAGES="igmpproxy ip iptraf kmod-ipt-nathelper-extra openvpn-polarssl tcpdump-mini -firewall -ip6tables -kmod-ip6tables -kmod-ipv6 -odhcp6c -ppp -ppp-mod-pppoe" \

Building the Image Generator with all packages inside

It is possible to build the Image Generator and integrate in it all packages so it will be able to generate images without downloading packages:

In the graphical configuration, select “Build the LEDE Image Builder” to build the image builder, then select Global Build SettingsSelect all packages by default, save and exit. Then build the image, including IGNORE_ERRORS=1 as there might be unmaintained packages that fail to compile.

Enabling IGNORE_ERRORS=1 should only be done once the kernel and required packages are known to compile successfully.


Note: Don't call make defconfig or leave an old .config file in the path as Select all packages by default will only set the package selection to [m] for packages that are not already configured otherwise!(make defconfig will set most packages to [n], i.e. do not build.)

Adding/Modifying Profiles

The image generation is tied to the profile names. If you add a new profile without also adding an appropriate macro to the image-generation Makefile, no suitable firmware file will get generated when using the custom profile. :!: Make sure to remove the /tmp directory to get modified package selection from profiles to work.

The location of the profiles for the pre-compiled package for brcm47xx-for-Linux-i686 was target/linux/brcm47xx/profiles/

Remarkably, all that needs to be done to add a new profile, is to add a new file to the profiles directory. While this may have been the case in earlier releases, for 17.01, it appears that manual editing of .targetinfo is also required.

Here is what the profiles/ profile file looks like:

define Profile/Broadcom-b43
  NAME:=Broadcom BCM43xx WiFi (default)
  PACKAGES:=kmod-b43 kmod-b43legacy

define Profile/Broadcom-b43/Description
	Package set compatible with hardware using Broadcom BCM43xx cards
$(eval $(call Profile,Broadcom-b43))
zh/docs/guide-user/additional-software/imagebuilder.txt · Last modified: 2018/10/14 10:38 by lujimmy