Rust for Linux List
 help / color / mirror / Atom feed
From: Nicolas Schier <nicolas@fjasle.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH 23/23] kbuild: allow to start building external module in any directory
Date: Fri, 4 Oct 2024 22:05:20 +0200	[thread overview]
Message-ID: <20241004-little-rigorous-ammonite-6a8ce2@lindesnes> (raw)
In-Reply-To: <20240917141725.466514-24-masahiroy@kernel.org>

On Tue, Sep 17, 2024 at 11:16:51PM +0900, Masahiro Yamada wrote:
> Unless an explicit O= option is provided, external module builds must
> start from the kernel directory.
> 
> This can be achieved by using the -C option:
> 
>   $ make -C /path/to/kernel M=/path/to/external/module
> 
> This commit allows starting external module builds from any directory,
> so you can also do the following:
> 
>   $ make -f /path/to/kernel/Makefile M=/path/to/external/module
> 
> The key difference is that the -C option changes the working directory
> and parses the Makefile located there, while the -f option only
> specifies the Makefile to use.
> 
> As shown in the examples in Documentation/kbuild/modules.rst, external
> modules usually have a wrapper Makefile that allows you to build them
> without specifying any make arguments. The Makefile typically contains
> a rule as follows:
> 
>     KDIR ?= /path/to/kernel
>     default:
>             $(MAKE) -C $(KDIR) M=$(CURDIR) $(MAKECMDGOALS)
> 
> The log will appear as follows:
> 
>     $ make
>     make -C /path/to/kernel M=/path/to/external/module
>     make[1]: Entering directory '/path/to/kernel'
>     make[2]: Entering directory '/path/to/exernal/module'
>       CC [M]  helloworld.o
>       MODPOST Module.symvers
>       CC [M]  helloworld.mod.o
>       CC [M]  .module-common.o
>       LD [M]  helloworld.ko
>     make[2]: Leaving directory '/path/to/exernal/module'

s/exernal/external/, also above.

>     make[1]: Leaving directory '/path/to/kernel'
> 
> This changes the working directory twice because the -C option first
> switches to the kernel directory, and then Kbuild internally recurses
> back to the external module directory.
> 
> With this commit, the wrapper Makefile can directly include the kernel
> Makefile:
> 
>     KDIR ?= /path/to/kernel
>     export KBUILD_EXTMOD = $(CURDIR)
>     include $(KDIR)/Makefile
> 
> This avoids unnecessary sub-make invocations:
> 
>     $ make
>       CC [M]  helloworld.o
>       MODPOST Module.symvers
>       CC [M]  helloworld.mod.o
>       CC [M]  .module-common.o
>       LD [M]  helloworld.ko
> 
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> 
>  Documentation/kbuild/modules.rst | 21 +++++++++++++++++++++
>  Makefile                         |  8 ++++++--
>  2 files changed, 27 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/kbuild/modules.rst b/Documentation/kbuild/modules.rst
> index 03347e13eeb5..5610cfa426bb 100644
> --- a/Documentation/kbuild/modules.rst
> +++ b/Documentation/kbuild/modules.rst
> @@ -88,6 +88,12 @@ executed to make module versioning work.
>  
>  		$ make -C /lib/modules/`uname -r`/build M=$PWD modules_install
>  
> +	Starting from Linux 6.13, you can use the -f option instead of -C. This
> +	will avoid unnecessary change of the working directory. The external
> +	module will be output to the directory where you invoke make.
> +
> +		$ make -f /lib/modules/`uname -r`/build/Makefile M=$PWD
> +
>  2.2 Options
>  ===========
>  
> @@ -246,6 +252,21 @@ module 8123.ko, which is built from the following files::
>  	consisting of several hundred lines, and here it really pays
>  	off to separate the kbuild part from the rest.
>  
> +	Linux 6.13 and later support another way. The external module Makefile
> +	can include the kernel Makefile directly, rather than invoking sub Make.
> +
> +	Example 3::
> +
> +		--> filename: Kbuild
> +		obj-m  := 8123.o
> +		8123-y := 8123_if.o 8123_pci.o
> +
> +		--> filename: Makefile
> +		KDIR ?= /lib/modules/`uname -r`/build

KDIR ?= /lib/modules/$(shell uname -r)/build

This patch is another very good idea, thanks!

Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>

> +		export KBUILD_EXTMOD = $(CURDIR)
> +		include $(KDIR)/Makefile
> +
> +
>  3.4 Building Multiple Modules
>  =============================
>  
> diff --git a/Makefile b/Makefile
> index 81603a50c757..88c160ac7b3c 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -189,9 +189,13 @@ ifdef KBUILD_EXTMOD
>          objtree := $(realpath $(KBUILD_OUTPUT))
>          $(if $(objtree),,$(error specified kernel directory "$(KBUILD_OUTPUT)" does not exist))
>      else
> -        objtree := $(CURDIR)
> +        objtree := $(abs_srctree)
>      endif
> -    output := $(or $(KBUILD_EXTMOD_OUTPUT),$(KBUILD_EXTMOD))
> +    # If Make is invoked from the kernel directory (either kernel
> +    # source directory or kernel build directory), external modules
> +    # are built in $(KBUILD_EXTMOD) for backward compatibility,
> +    # otherwise, built in the current directory.
> +    output := $(or $(KBUILD_EXTMOD_OUTPUT),$(if $(filter $(CURDIR),$(objtree) $(abs_srctree)),$(KBUILD_EXTMOD)))
>      # KBUILD_EXTMOD might be a relative path. Remember its absolute path before
>      # Make changes the working directory.
>      export abs_extmodtree := $(realpath $(KBUILD_EXTMOD))
> -- 
> 2.43.0
> 

-- 
Nicolas

  reply	other threads:[~2024-10-04 20:05 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17 14:16 [PATCH 00/23] kbuild: support building external modules in a separate build directory Masahiro Yamada
2024-09-17 14:16 ` [PATCH 01/23] kbuild: doc: update the description about Kbuild/Makefile split Masahiro Yamada
2024-09-18 15:35   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 02/23] kbuild: doc: remove description about grepping CONFIG options Masahiro Yamada
2024-09-18 15:35   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 03/23] kbuild: doc: remove outdated description of the limitation on -I usage Masahiro Yamada
2024-09-18 15:38   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 04/23] kbuild: doc: remove the description about shipped files Masahiro Yamada
2024-09-18 16:24   ` Nicolas Schier
2024-09-19 16:53     ` Masahiro Yamada
2024-09-17 14:16 ` [PATCH 05/23] kbuild: doc: describe the -C option precisely for external module builds Masahiro Yamada
2024-09-18 16:44   ` Nicolas Schier
2024-09-18 16:47   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 06/23] kbuild: doc: replace "gcc" in external module description Masahiro Yamada
2024-09-19 11:22   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 07/23] kbuild: remove unnecessary prune of rust/alloc for rustfmt Masahiro Yamada
2024-09-19 11:23   ` Nicolas Schier
2024-09-19 13:46     ` Nicolas Schier
2024-09-30 14:29       ` Miguel Ojeda
2024-09-17 14:16 ` [PATCH 08/23] kbuild: simplify find command " Masahiro Yamada
2024-09-19 13:54   ` Nicolas Schier
2024-09-19 13:59     ` Masahiro Yamada
2024-09-30 18:37   ` Miguel Ojeda
2024-10-01  2:18     ` Masahiro Yamada
2024-10-01  5:45       ` Miguel Ojeda
2024-09-17 14:16 ` [PATCH 09/23] speakup: use SPKDIR=$(src) to specify the source directory Masahiro Yamada
2024-10-03 18:25   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 10/23] kbuild: refactor the check for missing config files Masahiro Yamada
2024-09-25 14:04   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 11/23] kbuild: check the presence of include/generated/rustc_cfg Masahiro Yamada
2024-09-25 14:10   ` Nicolas Schier
2024-09-30 14:37   ` Miguel Ojeda
2024-09-17 14:16 ` [PATCH 12/23] scripts/nsdeps: use VPATH as src_prefix Masahiro Yamada
2024-09-25 14:18   ` Nicolas Schier
2024-09-26  7:30     ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 13/23] kbuild: replace two $(abs_objtree) with $(CURDIR) in top Makefile Masahiro Yamada
2024-09-25 14:27   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 14/23] kbuild: add $(objtree)/ prefix to some in-kernel build artifacts Masahiro Yamada
2024-09-26  7:50   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 15/23] kbuild: rename abs_objtree to abs_output Masahiro Yamada
2024-09-26  7:51   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 16/23] kbuild: use 'output' variable to create the output directory Masahiro Yamada
2024-09-26  7:54   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 17/23] kbuild: build external modules in their directory Masahiro Yamada
2024-10-03 18:41   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 18/23] kbuild: remove extmod_prefix, MODORDER, MODULES_NSDEPS variables Masahiro Yamada
2024-10-03 18:47   ` Nicolas Schier
2024-11-10  1:36     ` Masahiro Yamada
2024-09-17 14:16 ` [PATCH 19/23] kbuild: support building external modules in a separate build directory Masahiro Yamada
2024-10-03 19:47   ` Nicolas Schier
2024-10-04 19:45     ` Nicolas Schier
2024-11-10  1:36       ` Masahiro Yamada
2024-11-10  1:36     ` Masahiro Yamada
2024-09-17 14:16 ` [PATCH 20/23] kbuild: support -fmacro-prefix-map for external modules Masahiro Yamada
2024-10-04 18:51   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 21/23] kbuild: use absolute path in the generated wrapper Makefile Masahiro Yamada
2024-10-04 19:02   ` Nicolas Schier
2024-11-29 23:31   ` Caleb Connolly
2024-11-30  9:19     ` Masahiro Yamada
2024-09-17 14:16 ` [PATCH 22/23] kbuild: make wrapper Makefile more convenient for external modules Masahiro Yamada
2024-10-04 19:46   ` Nicolas Schier
2024-09-17 14:16 ` [PATCH 23/23] kbuild: allow to start building external module in any directory Masahiro Yamada
2024-10-04 20:05   ` Nicolas Schier [this message]
2024-09-20 10:39 ` [PATCH 00/23] kbuild: support building external modules in a separate build directory Nicolas Schier
2024-09-20 12:58   ` Masahiro Yamada
2024-09-20 13:41     ` Nicolas Schier
2024-09-28  6:50 ` Masahiro Yamada
2024-09-30 14:28   ` Miguel Ojeda
2024-10-04 20:16 ` Nicolas Schier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241004-little-rigorous-ammonite-6a8ce2@lindesnes \
    --to=nicolas@fjasle.eu \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox