From: Sam Ravnborg <sam@ravnborg.org>
To: yiding_wang@agilent.com
Cc: linux-kernel@vger.kernel.org,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: 2.5.x module make questions
Date: Tue, 29 Jul 2003 23:09:16 +0200 [thread overview]
Message-ID: <20030729210916.GA20154@mars.ravnborg.org> (raw)
In-Reply-To: <334DD5C2ADAB9245B60F213F49C5EBCD05D55239@axcs03.cos.agilent.com>
On Tue, Jul 29, 2003 at 02:45:35PM -0600, yiding_wang@agilent.com wrote:
> Team,
>
> I have two questions regarding kbuild.
> 1, According to doc., makefile can do descending. Could make carry ascending?
Kbuild is not designed to support ascending, and I do not think it is
possible to tweak it to do so. If you manage to tweak kbuild to support it
do not complain if it breakes. This is not intended neither supported.
> 2, Does old style of makefile still work (it should according to the article of "Driver porting: compiling external module")?
What Corbet suggest in the referenced doc is to have the following:
ifndef KERNELRELEASE
here goes old style Makefile
else
here goes Kbuild makefile
endif
And this is _only_ the topmost makefile. And the oldstyle part is only
to make it simple to do make -C kernelsrcdir SUBDIRS=$PWD modules
kbuild does not support old-style Makefiles, but fragments are supported.
May I request you to read Documentation/kbuild/makefiles.txt - this
is an up-to-date description of what kbuild supports, and what syntax to use.
The most complex examples of use in the kernel today is some of the
arch Makefiles. Maybe they can help you?
> export TOPDIR
> export CFLAGS
>
> all : ag.o
>
> ag.o: ../../../../t/s/ts.o ../../../f/c/fc.o ../../../f/i/fi.o s/sl.o
> ld -r -o ag.o ../../../../t/s/ts.o ../../../f/c/fc.o ../../../f/i/fi.o s/sl.o
This looks really ugly. I do not expect kbuild to even get close to help
you here. kbuild is designed around the idea that objects are built
directory-by-directory, and in the upper level directory the are linked.
What you have surely does not follow that principle.
> Any suggestion is welcomed. If the kbuild cannot do ascending, I have to change the source tree structure but that is the least I want to do.
This is my best suggestion. Follow the normal way of doing things in the
kernel make it easier/possible to use the infrastructure provided
by the kernel.
PS. Please also read the paper by Kai Germashewski from OLS -
see www.linuxsymposium.org - it provide good background info on kbuild.
Sam
next prev parent reply other threads:[~2003-07-29 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 20:45 yiding_wang
2003-07-29 21:09 ` Sam Ravnborg [this message]
2003-08-11 11:27 ` David Woodhouse
2003-07-29 21:33 yiding_wang
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=20030729210916.GA20154@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=yiding_wang@agilent.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®