[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54E4AA4C.4050509@suse.cz>
Date: Wed, 18 Feb 2015 16:05:48 +0100
From: Michal Marek <mmarek@...e.cz>
To: Kiran Raparthy <kumarsharma.r@...il.com>,
linux-kernel@...r.kernel.org
CC: Rom Lemarchand <romlem@...roid.com>, linux-kbuild@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [RFC] kbuild: make it possible to specify the module output dir
On 2015-02-09 11:58, Kiran Raparthy wrote:
> From: Rom Lemarchand <romlem@...roid.com>
>
> kbuild: make it possible to specify the module output dir
>
> Make modinst_dir user-defined on the command line.
>
> This allows to do things like:
> make MODLIB=output/ modinst_dir=. modules_install
>
> to ensure all the .ko are in the output/ directory.
Please explain the use case and why it is needed. There are two
user-changeable variables used by modules_install:
INSTALL_MOD_PATH - prepended to /lib/modules/..., to allow installation
to a staging directory by non-root
INSTALL_MOD_DIR - for out-of-tree modules; specifies the subdirectory
of /lib/modules/.../ to put the modules under
(default: "extra").
The hierarchy used in the source tree is reflected under
/lib/modules/.../extra, but that should not be an issue.
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists