public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Shea Levy <shea@shealevy.com>, linux-kernel@vger.kernel.org
Subject: Re: Build and Source Tree Requirements for Out-of-tree Modules
Date: Wed, 01 Jan 2014 15:04:27 -0500	[thread overview]
Message-ID: <52C474CB.8000300@gmail.com> (raw)
In-Reply-To: <52C43027.7010702@shealevy.com>

On 01/01/2014 10:11 AM, Shea Levy wrote:
> Hi all,
> 
> I am a package maintainer for the kernel for the NixOS
> distribution. We support users building out-of-tree modules and
> other packages that might depend on the kernel source or build
> trees, but make modules_install copies the entire source and build
> trees (we build with $(O) set) to $(INSTALL_PATH), and those are
> some big paths to keep around. Is there any documentation on which
> of those files should actually be needed by any out-of-tree tools?
> For example I'm guessing the intermediate object files in the build
> tree or the .c files in the source tree are not necessary, but it
> would be nice if there were a definitive list of what could be
> removed to save space.
Running 'make modules_prepare' in a clean source tree should set up
the sources with everything needed for out of tree modules, it largely
amounts to the .config file, a few scripts, and a couple of specific
other files.


  reply	other threads:[~2014-01-01 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 15:11 Build and Source Tree Requirements for Out-of-tree Modules Shea Levy
2014-01-01 20:04 ` Austin S Hemmelgarn [this message]
2014-01-02  2:24   ` Shea Levy

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=52C474CB.8000300@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shea@shealevy.com \
    /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