/openbmc/u-boot/board/avionic-design/tec-ng/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/board/h2200/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/board/avionic-design/medcom-wide/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/board/compal/paz00/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/board/avionic-design/tec/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/arch/nds32/ |
H A D | config.mk | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/fs/ubifs/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/board/avionic-design/plutux/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/board/compulab/trimslice/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/post/lib_powerpc/fpu/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/drivers/bios_emulator/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/arch/sandbox/cpu/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/board/samsung/origen/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/scripts/ |
H A D | Kbuild.include | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
H A D | Makefile.build | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/examples/api/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/arch/arm/cpu/armv7/ |
H A D | config.mk | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/arch/powerpc/lib/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/dts/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/examples/standalone/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/arch/x86/lib/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/lib/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/ |
H A D | config.mk | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/tools/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|
/openbmc/u-boot/common/ |
H A D | Makefile | 9e4140329ee9a787d0f96ac2829d618d47f7973f Tue Feb 04 02:24:24 CST 2014 Masahiro Yamada <yamada.m@jp.panasonic.com> kbuild: change out-of-tree build
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>
|