From: Ralf Baechle <ralf@linux-mips.org>
To: Song Wang <wsonguci@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: kbuild support to build one module with multiple separate components?
Date: Fri, 9 Jul 2004 23:57:00 +0200 [thread overview]
Message-ID: <20040709215700.GB4316@linux-mips.org> (raw)
In-Reply-To: <20040706230050.53313.qmail@web40006.mail.yahoo.com>
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
prev parent reply other threads:[~2004-07-09 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 23:00 kbuild support to build one module with multiple separate components? Song Wang
2004-07-09 21:57 ` Ralf Baechle [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=20040709215700.GB4316@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=wsonguci@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