mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: murtuja bharmal <murtuja_bharmal@yahoo.com>
Cc: linux-kernel@vger.kernel.org,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: Kbuild Makefile output
Date: Thu, 15 May 2008 19:42:23 +0200	[thread overview]
Message-ID: <20080515174222.GB24024@uranus.ravnborg.org> (raw)
In-Reply-To: <339763.26248.qm@web95104.mail.in2.yahoo.com>

On Thu, May 15, 2008 at 11:07:19PM +0530, murtuja bharmal wrote:
> Hello All.
> I want to collect all my object file in onedirectory and then want to create a kernel module.
> For example: This my directory structure.
> dir
> |
> --------------------------------------
> |            |        |        |
> dir1    dir2       dir3   dir4
> This is my makefile in 'dir'.
> obj-m := test.o
> test-objs += \
>                 dir1/test1.o  \
>                 dir2/test2.o  \
>                 dir3/test3.o
> all:
>             make -C /usr/src/linux M=`pwd` modules
> 
> Now I want to save all output objectfile test1.o test2.o test3.o in one directory
> called 'dir4' not in source directory. 'test.o' should look all this object file in 'dir4' for linking, not in the source directory and 'test.ko' should also be create in 'dir4'.
> Can any one tell me, what is require changes in Kernel Makefile for the same.

Do not do that...

If you really need to do so - please explain why so we can understand the rationale.
There are ~2000 modules that does not need this so what makes your maodule so special?

[Added kbuild@vger to cc as you also asked there]

	Sam

  reply	other threads:[~2008-05-15 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 17:37 murtuja bharmal
2008-05-15 17:42 ` Sam Ravnborg [this message]
2008-05-15 18:01   ` murtuja bharmal
2008-05-15 18:31   ` murtuja bharmal
2008-05-15 20:58     ` Joel Becker

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=20080515174222.GB24024@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=murtuja_bharmal@yahoo.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

all inboxes | Powered by JetHome®