mirror of
https://github.com/brain-hackers/u-boot-brain
synced 2024-06-09 23:36:03 +09:00
9e4140329e
This commit changes the working directory where the build process occurs. Before this commit, build process occurred under the source tree for both in-tree and out-of-tree build. That's why we needed to add $(obj) prefix to all generated files in makefiles like follows: $(obj)u-boot.bin: $(obj)u-boot Here, $(obj) is empty for in-tree build, whereas it points to the output directory for out-of-tree build. And our old build system changes the current working directory with "make -C <sub-dir>" syntax when descending into the sub-directories. On the other hand, Kbuild uses a different idea to handle out-of-tree build and directory descending. The build process of Kbuild always occurs under the output tree. When "O=dir/to/store/output/files" is given, the build system changes the current working directory to that directory and restarts the make. Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj=<sub-dir>" syntax for descending into sub-directories. (We can write it like "make $(obj)=<sub-dir>" with a shorthand.) This means the current working directory is always the top of the output directory. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Tested-by: Gerhard Sittig <gsi@denx.de>
16 lines
337 B
Makefile
16 lines
337 B
Makefile
X86DIR = x86emu
|
|
|
|
obj-y = atibios.o biosemu.o besys.o bios.o \
|
|
$(X86DIR)/decode.o \
|
|
$(X86DIR)/ops2.o \
|
|
$(X86DIR)/ops.o \
|
|
$(X86DIR)/prim_ops.o \
|
|
$(X86DIR)/sys.o \
|
|
$(X86DIR)/debug.o
|
|
|
|
EXTRA_CFLAGS += -I$(srctree)/$(src) -I$(srctree)/$(src)/include \
|
|
-D__PPC__ -D__BIG_ENDIAN__
|
|
|
|
CFLAGS += $(EXTRA_CFLAGS)
|
|
CPPFLAGS += $(EXTRA_CFLAGS)
|