summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2019-03-30 21:04:14 +0900
committerMasahiro Yamada <yamada.masahiro@socionext.com>2019-04-02 23:27:15 +0900
commit25b146c5b8ceecd43c311552d325a4e403c639f2 (patch)
treee8d022671481b5add2d94347c8f6355e24178f8f /scripts
parent6b1a9a02c72fdb6e1d67949bb01b66e07d88ace9 (diff)
downloadlinux-25b146c5b8ceecd43c311552d325a4e403c639f2.tar.bz2
kbuild: allow Kbuild to start from any directory
Kbuild always runs in the top of the output directory. If Make starts in the source directory with O=, it relocates the working directory to the location specified by O=. Also, users can start build from the output directory by using the Makefile generated by scripts/mkmakefile. With a little more effort, Kbuild will be able to start from any directory path. This commit allows to specify the source directory by using the -f option. For example, you can do: $ cd path/to/output/dir $ make -f path/to/source/dir/Makefile Or, for the equivalent behavior, you can do: $ make O=path/to/output/dir -f path/to/source/dir/Makefile KBUILD_SRC is now deprecated. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: Kieran Bingham <kbingham@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions