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 <[EMAIL PROTECTED]> 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
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
