1: uboot配置
先执行make<borad_name>_config命令进行配置,然后执行make进行编译
我们以smdk2410_config为例子:
首先 make smdk2410_config:
smdk2410_config : unconfig
@$(MKCONFIG) $(@:_config=) arm arm920t smdk2410 NULL s3c24x0
注释:@$(MKCONFIG) //在MKCONFIG := $(SRCTREE)/mkconfig
$(@:_config=) // smdk2410_config 即把_config去掉,即smdk2410
所以这句话就是./mkconfig smdk2410 arm arm920t smdk2410 NULL s3c24x0
那我们下面来分析mkconfig
while [ $# -gt 0 ] ; do
case "$1" in
--) shift ; break ;;
-a) shift ; APPEND=yes ;;
-n) shift ; BOARD_NAME="${1%%_config}" ; shift ;;
*) break ;;
esac
done
注释:
$# 表述参数的个数 smdk2410 ./mkconfig smdk2410 arm arm920t smdk2410 NULL s3c24x0 可以知道参数个数为6个.$1个参数为smdk2410即跳出while()循环
此处有一个要特殊说明下$0为当前程序的名称
[ "${BOARD_NAME}" ] || BOARD_NAME="$1"
[ $# -lt 4 ] && exit 1
[ $# -gt 6 ] && exit 1
注: ${BOARD_NAME}"为空, BOARD_NAME="$1" 即BOARD_NAME= smdk2410;由上面可以知道,参数个数为6所以上面都不会去运行。
if [ "$SRCTREE" != "$OBJTREE" ] ; then
mkdir -p ${OBJTREE}/include
mkdir -p ${OBJTREE}/include2
cd ${OBJTREE}/include2
rm -f asm
ln -s ${SRCTREE}/include/asm-$2 asm
LNPREFIX="../../include2/asm/"
cd ../include
rm -rf asm-$2
rm -f asm
mkdir asm-$2
ln -s asm-$2 asm
else
cd ./include
rm -f asm
ln -s asm-$2 asm
fi
注:if [ "$SRCTREE" != "$OBJTREE" ] ; 是指在编译uboot的时候存放生成文件的目录和源码的目录是否相同,如果不同的话创建目录,SRCTREE和OBJTREE的两个值是从makefile中传过来的。我们没有去定义OBJTREE,所以这两个值是相同的。那么是走else这一路:
cd ./include
rm -f asm //删除之前的文件asm
ln -s asm-$2 asm //创建一符号链接,即创建asm 指向asm-asm
rm -f asm-$2/arch //删除asm-asm/arch 下的文件
if [ -z "$6" -o "$6" = "NULL" ] ; then
ln -s ${LNPREFIX}arch-$3 asm-$2/arch
else
ln -s ${LNPREFIX}arch-$6 asm-$2/arch
fi
注:-z判断是否为字符串,如果为空则为真, 【-o OPTIONNAME ] 如果 shell选项 “OPTIONNAME” 开启则为真 $6 = s3c24x0,是字符串且不为空,所以走else
s ${LNPREFIX}为空所以这句话是ln -s arch-s3c24x0 asm-asm/arc 即创建一符号链接,指向arm-arm/arc
if [ "$2" = "arm" ] ; then
rm -f asm-$2/proc
ln -s ${LNPREFIX}proc-armv asm-$2/proc
fi
注:由上可知$2 = arm 所以继续运行,先删除arm-arm/proc, ln -s proc-armv asm-arm/proc 创建一个软连接asm-asm/proc指向proc-armv
echo "ARCH = $2" > config.mk
echo "CPU = $3" >> config.mk
echo "BOARD = $4" >> config.mk
这三句话的意思是:向config.mk写入(当前在include目录下)ARCH = asm CPU =arm920t BORAD = smdk2410 (第一次编译是没有的需要创建,之后直接就覆盖之前的值)
[ "$5" ] && [ "$5" != "NULL" ] && echo "VENDOR = $5" >> config.mk
[ "$6" ] && [ "$6" != "NULL" ] && echo "SOC = $6" >> config.mk
注:这两句话的意思是,如果$5和$6不为空那么VENDOR = $5, SOC= $6,由上面可知 $5=NULL,$6=S3C24xo 即向.config.mk写入SOC的值
if [ "$APPEND" = "yes" ] # Append to existing config file
then
echo >> config.h
else
> config.h # Create new config file
fi
echo "/* Automatically generated - do not edit */" >>config.h
echo "#include <configs/$1.h>" >>config.h
exit 0
注:走else 创建config.h这个文件,然后向 config.h输入一些字符串到config.h文件中
总结:mkconfig主要是生成include/mkconfig和include/include两个文件,并把值赋给BORDNAME, ARCH,CPU,BORAD,VENDOR,SOC
注:
Target:宿主机平台
Architecture:定义芯片架构(如MIPS、POWERPC、ARM等)
CPU:定义芯片指令集版本(如ARM7、ARM9、ARM11等)
Board:芯片厂商,它细分为两类
[VENDOR]:按厂商划分(如AT9200、S3C44B0等)
[SOC]:按SOC类型(如S3C2440、S3C2410等)
2:make
我们先分析下makefile:
使用make生成的目标文件会存放在源代码的目录下,为了保持源代码干净,我们可以把生成的目标文件单独存放在另外的目录下,读readme我们可以知道如下操作可以达到目的。
1 make O=/tmp/build smdk2410_config
2: export BUILD_DIR=/tmp/build
make smdk2410_config
make all
我们分析目标和源代码在同一目录
HOSTARCH := $(shell uname -m | \
sed -e s/i.86/i386/ \
-e s/sun4u/sparc64/ \
-e s/arm.*/arm/ \
-e s/sa110/arm/ \
-e s/powerpc/ppc/ \
-e s/macppc/ppc/)
注:
获取主机系统架构
uname -m 输出的是主机的CPU架构类型。sed -e s /abc/def/ 用def代替abc
我的电脑是i686.运行uname -m 输出的结果是i686 所以对应 i.86执行脚本sed -e s 之后得到的结果是i386
HOSTOS := $(shell uname -s | tr '[:upper:]' '[:lower:]' | \
sed -e 's/\(cygwin\).*/cygwin/')
注:获取主机的系统的操作类型
uname -s 输出的是主机的系统类型,我使用的是linux的ubuntu 9.10版本, 所以uname -s 输出的是Linux 经过 tr '[:upper:]' '[:lower:]'(大写转换成小写)得到的结果是linux, 所以HOSTS = linux
ifdef O
ifeq ("$(origin O)", "command line")
BUILD_DIR := $(O)
endif
endif
注:设定输出目标
O即是运行makefile的参数,如果O存在,则运行ifeq ("$(origin O)", "command line"), 函数$( origin, variable) 输出的结果是一个字符串,输出结果由变量variable定义的方式决定,若variable在命令行中定义过,则origin函数返回值为"command line"。假若在命令行中执行了“exportBUILD_DIR=/tmp/build”的命令,则“$(origin O)”值为“command line”,而BUILD_DIR被设置为“/tmp/build”。
ifneq ($(BUILD_DIR),)
saved-output := $(BUILD_DIR)
# Attempt to create a output directory.
$(shell [ -d ${BUILD_DIR} ] || mkdir -p ${BUILD_DIR})
# Verify if it was successful.
BUILD_DIR := $(shell cd $(BUILD_DIR) && /bin/pwd)
$(if $(BUILD_DIR),,$(error output directory "$(saved-output)" does not exist))
endif
注:定义输出目录,由上述可知,BUDIR_DIR为空,如果{BUILD_DIR}不为空,则去判断{BUILD_DIR}没有定义如果没有定义则创建{BUILD_DIR},并且进入$(BUILD_DIR)把路径值赋值BUILD_DIR
OBJTREE := $(if $(BUILD_DIR),$(BUILD_DIR),$(CURDIR))
SRCTREE := $(CURDIR)
TOPDIR := $(SRCTREE)
LNDIR := $(OBJTREE)
export TOPDIR SRCTREE OBJTREE
MKCONFIG := $(SRCTREE)/mkconfig
export MKCONFIG
ifneq ($(OBJTREE),$(SRCTREE))
REMOTE_BUILD := 1
export REMOTE_BUILD
endif
注:若BUILD_DIR的值为空则把CURDIR的赋值给BUILDIR,有上述可知BUILD_DIR为空,所以把CURDIR的值赋值给BUILD_DIR。由此可知:
OBJDIR = CURDIR;
SRCTREE = CURDIR;
TOPDIR = SRCTRE;
LNDIR = CURDIR;
ifneq ($(OBJTREE),$(SRCTREE))
obj := $(OBJTREE)/
src := $(SRCTREE)/
else
obj :=
src :=
endif
export obj src
注:把OBJTREE 的值赋值给obj,SRCTREE的值赋值给src
make all
若没有执行过make<boradname>_config命令,直接执行make 或者make all ,编译就会停止,就会有如下错误信息提示 :System not configured - see README
是怎样执行这个操作呢:
ifeq ($(OBJTREE)/include/config.mk,$(wildcard $(OBJTREE)/include/config.mk))
*******
******
else
all $(obj)u-boot.hex $(obj)u-boot.srec $(obj)u-boot.bin \
$(obj)u-boot.img $(obj)u-boot.dis $(obj)u-boot \
$(SUBDIRS) version gdbtools updater env depend \
dep tags ctags etags $(obj)System.map:
@echo "System not configured - see README" >&2
@ exit 1
endif
($(OBJTREE)/include/config.mk,$(wildcard $(OBJTREE)/include/config.mk))若(OBJTREE)/include/config.mk存在并且是(wildcard $(OBJTREE)/include/config.mk)展开的字符串,否则就为空。如果没有执行过make<board_name>_config 那么(OBJTREE)/include/config.mk就为空,就会执行else 就会显示System not configured - see README。
那么我们现在来看执行过make <borad_name>_config
#load ARCH, BOARD, and CPU configuration
include $(OBJTREE)/include/config.mk //注:把make<board_name>_config生成的config.mk包含进来
export ARCH CPU BOARD VENDOR SOC
ifndef CROSS_COMPILE
ifeq ($(HOSTARCH),ppc)
CROSS_COMPILE =
else
ifeq ($(ARCH),ppc)
CROSS_COMPILE = powerpc-linux-
endif
ifeq ($(ARCH),arm)
CROSS_COMPILE = arm-linux-
endif
ifeq ($(ARCH),i386)
ifeq ($(HOSTARCH),i386)
CROSS_COMPILE =
else
CROSS_COMPILE = i386-linux-
endif
endif
ifeq ($(ARCH),mips)
CROSS_COMPILE = mips_4KC-
endif
ifeq ($(ARCH),nios)
CROSS_COMPILE = nios-elf-
endif
ifeq ($(ARCH),nios2)
CROSS_COMPILE = nios2-elf-
endif
ifeq ($(ARCH),m68k)
CROSS_COMPILE = m68k-elf-
endif
ifeq ($(ARCH),microblaze)
CROSS_COMPILE = mb-
endif
ifeq ($(ARCH),blackfin)
CROSS_COMPILE = bfin-elf-
endif
ifeq ($(ARCH),avr32)
CROSS_COMPILE = avr32-
endif
endif
endif
export CROSS_COMPILE
注:设置编译器。由此可知我们是arm所以使用的arm-linux-
# load other configuration
include $(TOPDIR)/config.mk
注:包含顶层的config.mk
看下config.mk主要做了些什么动作
ifneq ($(OBJTREE),$(SRCTREE))
ifeq ($(CURDIR),$(SRCTREE))
dir :=
else
dir := $(subst $(SRCTREE)/,,$(CURDIR))
endif
obj := $(if $(dir),$(OBJTREE)/$(dir)/,$(OBJTREE)/)
src := $(if $(dir),$(SRCTREE)/$(dir)/,$(SRCTREE)/)
$(shell mkdir -p $(obj))
else
obj :=
src :=
endif
注:由于目标输出到源代码目录下,所以执行完上面的代码后src和obj都是空
PLATFORM_RELFLAGS =
PLATFORM_CPPFLAGS = //预处理选项
PLATFORM_LDFLAGS = //链接选项
注:先把三个编译选项清零
ifdef ARCH
sinclude $(TOPDIR)/$(ARCH)_config.mk # include architecture dependend rules
endif
ifdef CPU
sinclude $(TOPDIR)/cpu/$(CPU)/config.mk # include CPU specific rules
endif
ifdef SOC
sinclude $(TOPDIR)/cpu/$(CPU)/$(SOC)/config.mk # include SoC specific rules
endif
ifdef VENDOR
BOARDDIR = $(VENDOR)/$(BOARD)
else
BOARDDIR = $(BOARD)
endif
ifdef BOARD
sinclude $(TOPDIR)/board/$(BOARDDIR)/config.mk # include board specific rules
endif
注:
$(ARCH)的值是“arm”,因此将“lib_arm/config.mk”包含进来。lib_arm/config.mk脚本指定了交叉编译器,添加了一些跟CPU架构相关的编译选项。
$(CPU)的值是“arm920t”,因此将“cpu/arm920t/config.mk”包含进来。这个脚本主要设定了跟arm920t处理器相关的编译选项。
$(SOC)的值是s3c24x0,因此Make程序尝试将cpu/arm920t/s3c24x0/config.mk包含进来,而这个文件并不存在,但是由于用的是“sinclude”命令,所以并不会报错。
Make将“board/smdk2410/config.mk”包含进来。config.mk里面只有一句脚本
TEXT_BASE = 0x33F80000
U-Boot编译时将使用TEXT_BASE作为代码段连接的起始地址。
CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
else if [ -x /bin/bash ]; then echo /bin/bash; \
else echo sh; fi ; fi)
注:选择shell脚本
ifeq ($(HOSTOS)-$(HOSTARCH),darwin-ppc)
HOSTCC = cc
else
HOSTCC = gcc
endif
HOSTCFLAGS = -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
HOSTSTRIP = strip
注:选择编译器并设置编译选项
cc-option = $(shell if $(CC) $(CFLAGS) $(1) -S -o /dev/null -xc /dev/null \
> /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi ;)
变量CC和CFLAGS在后面的代码定义为延时变量,其中的CC即arm-linux-gcc。函数cc-option用于检查编译器CC是否支持某选项。将2个选项作为参数传递给函数,该函数调用CC编译器检查参数1是否支持,若支持则函数返回参数1,否则返回参数2 (因此CC编译器必须支持参数1或参数2,若两个都不支持则会编译出错)。可以像下面这样调用cc-option函数,并将支持的选项添加到FLAGS中:
FLAGS +=$(call cc-option,option1,option2)
AS = $(CROSS_COMPILE)as
LD = $(CROSS_COMPILE)ld
CC = $(CROSS_COMPILE)gcc
CPP = $(CC) -E
AR = $(CROSS_COMPILE)ar
NM = $(CROSS_COMPILE)nm
STRIP = $(CROSS_COMPILE)strip
OBJCOPY = $(CROSS_COMPILE)objcopy
OBJDUMP = $(CROSS_COMPILE)objdump
RANLIB = $(CROSS_COMPILE)RANLIB
注:指定交叉编译环境
对于arm开发板,其中的CROSS_COMPILE在makefile 中已经定义过,其值为arm-linux-
ifneq (,$(findstring s,$(MAKEFLAGS)))
ARFLAGS = cr //设置AR选项
else
ARFLAGS = crv
endif
RELFLAGS= $(PLATFORM_RELFLAGS)
DBGFLAGS= -g # -DDEBUG //调试选项
OPTFLAGS= -Os #-fomit-frame-pointer //优化选项
ifndef LDSCRIPT
LDSCRIPT := $(TOPDIR)/board/$(BOARDDIR)/u-boot.lds.debug
ifeq ($(CONFIG_NAND_U_BOOT),y)
LDSCRIPT := $(TOPDIR)/board/$(BOARDDIR)/u-boot-nand.lds
else
LDSCRIPT := $(TOPDIR)/board/$(BOARDDIR)/u-boot.lds //这个文件定义了链接时各个文件是怎么存放的
endif
endif
OBJCFLAGS += --gap-fill=0xff
gccincdir := $(shell $(CC) -print-file-name=include)
CPPFLAGS := $(DBGFLAGS) $(OPTFLAGS) $(RELFLAGS) \
-D__KERNEL__ -DTEXT_BASE=$(TEXT_BASE) \
ifneq ($(OBJTREE),$(SRCTREE))
CPPFLAGS += -I$(OBJTREE)/include2 -I$(OBJTREE)/include
endif
CPPFLAGS += -I$(TOPDIR)/include
CPPFLAGS += -fno-builtin -ffreestanding -nostdinc \
-isystem $(gccincdir) -pipe $(PLATFORM_CPPFLAGS)
ifdef BUILD_TAG
CFLAGS := $(CPPFLAGS) -Wall -Wstrict-prototypes \
-DBUILD_TAG='"$(BUILD_TAG)"'
else
CFLAGS := $(CPPFLAGS) -Wall -Wstrict-prototypes
endif
# avoid trigraph warnings while parsing pci.h (produced by NIOS gcc-2.9)
# this option have to be placed behind -Wall -- that's why it is here
ifeq ($(ARCH),nios)
ifeq ($(findstring 2.9,$(shell $(CC) --version)),2.9)
CFLAGS := $(CPPFLAGS) -Wall -Wno-trigraphs
endif
endif
# $(CPPFLAGS) sets -g, which causes gcc to pass a suitable -g<format>
# option to the assembler.
AFLAGS_DEBUG :=
# turn jbsr into jsr for m68k
ifeq ($(ARCH),m68k)
ifeq ($(findstring 3.4,$(shell $(CC) --version)),3.4)
AFLAGS_DEBUG := -Wa,-gstabs,-S
endif
endif
AFLAGS := $(AFLAGS_DEBUG) -D__ASSEMBLY__ $(CPPFLAGS)
LDFLAGS += -Bstatic -T $(LDSCRIPT) -Ttext $(TEXT_BASE) $(PLATFORM_LDFLAGS)
注:U-Boot编译时将使用TEXT_BASE作为代码段连接的起始地址
# Location of a usable BFD library, where we define "usable" as
# "built for ${HOST}, supports ${TARGET}". Sensible values are
# - When cross-compiling: the root of the cross-environment
# - Linux/ppc (native): /usr
# - NetBSD/ppc (native): you lose ... (must extract these from the
# binutils build directory, plus the native and U-Boot include
# files don't like each other)
#
# So far, this is used only by tools/gdb/Makefile.
ifeq ($(HOSTOS)-$(HOSTARCH),darwin-ppc)
BFD_ROOT_DIR = /usr/local/tools
else
ifeq ($(HOSTARCH),$(ARCH))
# native
BFD_ROOT_DIR = /usr
else
#BFD_ROOT_DIR = /LinuxPPC/CDK # Linux/i386
#BFD_ROOT_DIR = /usr/pkg/cross # NetBSD/i386
BFD_ROOT_DIR = /opt/powerpc
endif
endif
ifeq ($(PCI_CLOCK),PCI_66M)
CFLAGS := $(CFLAGS) -DPCI_66M
endif
ifndef REMOTE_BUILD
%.s: %.S
$(CPP) $(AFLAGS) -o $@ $<
%.o: %.S
$(CC) $(AFLAGS) -c -o $@ $<
%.o: %.c
$(CC) $(CFLAGS) -c -o $@ $<
else
$(obj)%.s: %.S
$(CPP) $(AFLAGS) -o $@ $<
$(obj)%.o: %.S
$(CC) $(AFLAGS) -c -o $@ $<
$(obj)%.o: %.c
$(CC) $(CFLAGS) -c -o $@ $<
endif
注:指定隐含编译规则
根据以上的定义,以“.s”结尾的目标文件将根据第一条规则由同名但后缀为“.S”的源文件来生成,若不存在“.S”结尾的同名文件则根据最后一条规则由同名的“.c”文件生成。
下面回来接着分析Makefile的内容:
OBJS = cpu/$(CPU)/start.o
ifeq ($(CPU),i386)
OBJS += cpu/$(CPU)/start16.o
OBJS += cpu/$(CPU)/reset.o
endif
ifeq ($(CPU),ppc4xx)
OBJS += cpu/$(CPU)/resetvec.o
endif
ifeq ($(CPU),mpc83xx)
OBJS += cpu/$(CPU)/resetvec.o
endif
ifeq ($(CPU),mpc85xx)
OBJS += cpu/$(CPU)/resetvec.o
endif
ifeq ($(CPU),mpc86xx)
OBJS += cpu/$(CPU)/resetvec.o
endif
ifeq ($(CPU),bf533)
OBJS += cpu/$(CPU)/start1.o cpu/$(CPU)/interrupt.o cpu/$(CPU)/cache.o
OBJS += cpu/$(CPU)/cplbhdlr.o cpu/$(CPU)/cplbmgr.o cpu/$(CPU)/flush.o
endif
OBJS := $(addprefix $(obj),$(OBJS))
LIBS = lib_generic/libgeneric.a
LIBS += board/$(BOARDDIR)/lib$(BOARD).a
LIBS += cpu/$(CPU)/lib$(CPU).a
ifdef SOC
LIBS += cpu/$(CPU)/$(SOC)/lib$(SOC).a
endif
LIBS += lib_$(ARCH)/lib$(ARCH).a
LIBS += fs/cramfs/libcramfs.a fs/fat/libfat.a fs/fdos/libfdos.a fs/jffs2/libjffs2.a \
fs/reiserfs/libreiserfs.a fs/ext2/libext2fs.a
LIBS += net/libnet.a
LIBS += disk/libdisk.a
LIBS += rtc/librtc.a
LIBS += dtt/libdtt.a
LIBS += drivers/libdrivers.a
LIBS += drivers/nand/libnand.a
LIBS += drivers/nand_legacy/libnand_legacy.a
LIBS += drivers/usb/libusb.a
LIBS += drivers/sk98lin/libsk98lin.a
LIBS += common/libcommon.a
LIBS += $(BOARDLIBS)
LIBS := $(addprefix $(obj),$(LIBS))
.PHONY : $(LIBS)
注:LIBS变量指明了U-Boot需要的库文件,包括平台/开发板相关的目录、通用目录下相应的库,都通过相应的子目录编译得到的。
以下几个跟平台相关
OBJS = cpu/$(CPU)/start.o
LIBS += board/$(BOARDDIR)/lib$(BOARD).a
LIBS += cpu/$(CPU)/lib$(CPU).a
LIBS += cpu/$(CPU)/$(SOC)/lib$(SOC).a
LIBS += cpu/$(CPU)/$(SOC)/lib$(SOC).a
其余与平台都无关
ifeq ($(CONFIG_NAND_U_BOOT),y)
NAND_SPL = nand_spl
U_BOOT_NAND = $(obj)u-boot-nand.bin
endif
注:如果uboot 支持nand flash启动,那么就定义了CONFIG_NAND_U_BOOT宏
ALL = $(obj)u-boot.srec $(obj)u-boot.bin $(obj)System.map $(U_BOOT_NAND)
$(obj)u-boot.hex: $(obj)u-boot
$(OBJCOPY) ${OBJCFLAGS} -O ihex $< $@
$(obj)u-boot.srec: $(obj)u-boot
$(OBJCOPY) ${OBJCFLAGS} -O srec $< $@
$(obj)u-boot.bin: $(obj)u-boot
$(OBJCOPY) ${OBJCFLAGS} -O binary $< $@
注:最终生成u-boot.srec, u-boot.bin,System.map而这些文件又依赖于uboot.其中u-boot是ELF文件,u-boot.srec是Motorola S-Record format文件,System.map 是U-Boot的符号表,u-boot.bin是最终烧写到开发板的二进制可执行的文件。我们看看u-boot是怎么生成的
$(obj)u-boot: depend version $(SUBDIRS) $(OBJS) $(LIBS) $(LDSCRIPT)
注:依赖目标depend:生成各个子目录的.depend文件,.denpend列出每个目标文件的依赖文件,生成方法,调用每个子目录的make _depend
depend dep:
for dir in $(SUBDIRS) ; do $(MAKE) -C $$dir _depend ; done
依赖目标生成版本信息version 生成的版本信息到${VERSION_FILE}中
version:
@echo -n "#define U_BOOT_VERSION \"U-Boot " > $(VERSION_FILE); \
echo -n "$(U_BOOT_VERSION)" >> $(VERSION_FILE); \
echo -n $(shell $(CONFIG_SHELL) $(TOPDIR)/tools/setlocalversion \
$(TOPDIR)) >> $(VERSION_FILE); \
echo "\"" >> $(VERSION_FILE)
伪目标:(SUBDIRS)执行tools, examples, post, post/cpu目录下面的make
SUBDIRS = tools \
examples \
post \
post/cpu
$(SUBDIRS):
$(MAKE) -C $@ all
伪目标:(OBJS) //即CPU/start.o
echo $(OBJS)
$(MAKE) -C cpu/$(CPU) $(if $(REMOTE_BUILD),$@,$(notdir $@))
伪目标:(LIBS) //这个目标太多,即是每个子文件的库*.a,通过相应的子文件里的make得到
$(MAKE) -C $(dir $(subst $(obj),,$@))
伪目标:(LDSCRIPT)
ifeq ($(CONFIG_NAND_U_BOOT),y)
LDSCRIPT := $(TOPDIR)/board/$(BOARDDIR)/u-boot-nand.lds
else
LDSCRIPT := $(TOPDIR)/board/$(BOARDDIR)/u-boot.lds
endif
LDFLAGS += -Bstatic -T $(LDSCRIPT) -Ttext $(TEXT_BASE) $(PLATFORM_LDFLAGS)
对于smdk2410,LDSCRIPT即链接脚本文件是board/smdk2410/u-boot.lds
OUTPUT_ARCH(arm)ENTRY(_start)
SECTIONS
{
. = 0x00000000;
. = ALIGN(4);
.text : //.text的基地址是由LDFLAG S中 $(TEXT_BASE)决定你,在smdk2410中指定基地址为0x33f80000
{
cpu/arm920t/start.o (.text) //start.o为首
*(.text)
}
. = ALIGN(4);
.rodata : { *(.rodata) }
. = ALIGN(4);
.data : { *(.data) }
. = ALIGN(4);
.got : { *(.got) }
. = .;
__u_boot_cmd_start = .;
.u_boot_cmd : { *(.u_boot_cmd) }
__u_boot_cmd_end = .;
. = ALIGN(4);
__bss_start = .;
.bss : { *(.bss) }
_end = .;
}
执行链接命令
cd $(LNDIR) && $(LD) $(LDFLAGS) $$UNDEF_SYM $(__OBJS) \
--start-group $(__LIBS) --end-group $(PLATFORM_LIBS) \
-Map u-boot.map -o u-bo
注:其实就是把start.o和各个子目录makefile生成的库文件按照LDFLAGS链接在一起,生成elf文件u_boot,和链接时内存分配图文件u-boot.map
总结:工程的编译流程也就是通过编译make<board_name>_config时传入ARCH,CPU,BOARD,SOC参数,mkconfig根据参数将include 相应的头文件链接好生成config.h,然后执行make,进入相应的子文件夹执行makefile生成相应的obj文件和相应的*.a库文件,最后链接所有目标文件,生成镜像。不同格式的镜像都是调用elf格式的镜像直接或者间接转换而来