From: Song Wang <wsonguci@yahoo.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: sam@ravnborg.org, kbuild-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: kbuild support to build one module with multiple separate components?
Date: Wed, 14 Jul 2004 14:59:07 -0700 (PDT) [thread overview]
Message-ID: <20040714215907.93421.qmail@web40001.mail.yahoo.com> (raw)
In-Reply-To: <20040709215700.GB4316@linux-mips.org>
Hi, Ralf
Thanks for the reply.
I looked through kbuild documentation. This is
a variable called lib-y to build .a, for instance,
lib-y := a.o, b.o
Then lib.a will be produced. However, in this case,
you can build a lib.a for each sub module, but
they will have the same name, I don't know how you
can link them together.
I think the current kbuild system does simplify
the Makefiles in 2.6, but it also reduces the
flexibility.
-Song
--- Ralf Baechle <ralf@linux-mips.org> wrote:
> On Tue, Jul 06, 2004 at 04:00:50PM -0700, Song Wang
> wrote:
>
> > This is wrong, because kbuild will treat A as
> > independent module. All I want is to treat
> > A as component of the only module mymodule.o. It
> > should be linked to mymodule.o
> >
> > Any idea on how to write a kbuild Makefile to
> > support such kind of single module produced
> > by linking multiple components and each component
> > is located in separate directory? Thanks.
>
> That's a limitation in the current kbuild system.
> You either have to put
> all files into a single directory or if you don't
> want that split your
> module into several independant modules. What I
> haven't tried is using
> .a libraries but they're generally deprecated in
> kbuild.
>
> Ralf
>
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
next parent reply other threads:[~2004-07-14 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040709215700.GB4316@linux-mips.org>
2004-07-14 21:59 ` Song Wang [this message]
2004-07-02 18:36 Song 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=20040714215907.93421.qmail@web40001.mail.yahoo.com \
--to=wsonguci@yahoo.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®