All of lore.kernel.org
 help / color / mirror / Atom feed
From: horserivers@gmail.com (horseriver)
To: kernelnewbies@lists.kernelnewbies.org
Subject: where is the build rule for kernel's subdirs?
Date: Mon, 14 Jan 2013 15:23:28 +0800	[thread overview]
Message-ID: <20130114072328.GD4289@debian.localdomain> (raw)
In-Reply-To: <50F43339.4040701@infradead.org>

On Mon, Jan 14, 2013 at 08:32:57AM -0800, Randy Dunlap wrote:
> On 01/13/13 20:33, horseriver wrote:
> > hi:
> > 
> >    How does   kbuild   build objects for subdirs of kernel source ? 
> 
> It goes into subdirs recursively.
> 
> 
> From top-level Makefile:
> 
> # Objects we will link into vmlinux / subdirs we need to visit
> init-y		:= init/
> drivers-y	:= drivers/ sound/ firmware/
> net-y		:= net/
> libs-y		:= lib/
> core-y		:= usr/
> 
> 
> Then each subdir's Makefile has its own rules.

  I do not think so !

  every makefile in these subdirs only have defined obj files ,but not contained build rules .

  Thanks!
> 
> -- 
> ~Randy

      reply	other threads:[~2013-01-14  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  4:33 where is the build rule for kernel's subdirs? horseriver
2013-01-14 16:32 ` Randy Dunlap
2013-01-14  7:23   ` horseriver [this message]

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=20130114072328.GD4289@debian.localdomain \
    --to=horserivers@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.