Both relative path and absolute path have pros and cons. For example,
we can move the source and objtree around together by using the
relative path to the source tree.
Do not force the absolute path to the source tree. If you prefer the
absolute path, you can specify KBUILD_ABS_SRCTREE=1.
Signed-off-by: Masahiro Yamada <[email protected]>
---
scripts/mkmakefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/mkmakefile b/scripts/mkmakefile
index 4d0faebb1719..1cb174751429 100755
--- a/scripts/mkmakefile
+++ b/scripts/mkmakefile
@@ -12,6 +12,6 @@ if [ "${quiet}" != "silent_" ]; then
fi
cat << EOF > Makefile
-# Automatically generated by $(realpath $0): don't edit
-include $(realpath $1/Makefile)
+# Automatically generated by $0: don't edit
+include $1/Makefile
EOF
--
2.17.1
On Thu, Aug 22, 2019 at 12:59 PM Masahiro Yamada
<[email protected]> wrote:
>
> Both relative path and absolute path have pros and cons. For example,
> we can move the source and objtree around together by using the
> relative path to the source tree.
>
> Do not force the absolute path to the source tree. If you prefer the
> absolute path, you can specify KBUILD_ABS_SRCTREE=1.
>
> Signed-off-by: Masahiro Yamada <[email protected]>
> ---
Applied to linux-kbuild.
> scripts/mkmakefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/mkmakefile b/scripts/mkmakefile
> index 4d0faebb1719..1cb174751429 100755
> --- a/scripts/mkmakefile
> +++ b/scripts/mkmakefile
> @@ -12,6 +12,6 @@ if [ "${quiet}" != "silent_" ]; then
> fi
>
> cat << EOF > Makefile
> -# Automatically generated by $(realpath $0): don't edit
> -include $(realpath $1/Makefile)
> +# Automatically generated by $0: don't edit
> +include $1/Makefile
> EOF
> --
> 2.17.1
>
--
Best Regards
Masahiro Yamada