From: Sam Ravnborg <sam@ravnborg.org>
To: Qian_Riny@emc.com
Cc: linux-kbuild@vger.kernel.org
Subject: Re: How to separate obj and src for external module build?
Date: Tue, 5 Aug 2008 22:44:26 +0200 [thread overview]
Message-ID: <20080805204426.GC5464@uranus.ravnborg.org> (raw)
In-Reply-To: <74FD445BA9418847A54455595122B4B43F7F4F@CORPUSMX70C.corp.emc.com>
On Tue, Aug 05, 2008 at 04:47:44AM -0400, Qian_Riny@emc.com wrote:
> Hi,
>
> I want to put all obj files (*.o, *.ko etc) into a different directory
> (e.g. obj/)
> rather than the same src (*.c, Makefile) directory while building an
> external module:
> $(MAKE) -C $(KERNELDIR) M=$(SRC) modules
> How to do it?
>
> I tried to use O (KBUILD_OUTPUT), but still no luck. It seems that
> O (KBUILD_OUTPUT) is just used for kernel build output.
>
> $(MAKE) -C $(KERNELDIR) M=$(SRC) O=$(OBJ) modules
> It doesn't work.
This is not yet supported by kbuild and I have no plans to look
into it at the moment.
Sam
prev parent reply other threads:[~2008-08-05 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 8:47 How to separate obj and src for external module build? Qian_Riny
2008-08-05 20:44 ` Sam Ravnborg [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=20080805204426.GC5464@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Qian_Riny@emc.com \
--cc=linux-kbuild@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