From: colin@cvidal.org (Colin Vidal)
To: kernelnewbies@lists.kernelnewbies.org
Subject: build external module splited into several files
Date: Mon, 04 Apr 2016 21:43:27 +0200 [thread overview]
Message-ID: <1459799007.2600.11.camel@cvidal.org> (raw)
In-Reply-To: <20160404184740.GC32131@kroah.com>
On Mon, 2016-04-04 at 11:47 -0700, Greg KH wrote:
> On Mon, Apr 04, 2016 at 08:00:09PM +0200, Colin Vidal wrote:
> >?
> > Hi all,
> >?
> > I'm currently reading LDD the 3rd edition. Chapter 2 says that if
> > we
> > need for example to build module "foo.c" which is split in two
> > other
> > files "sub1.c" and "sub2.c", we just have to define the following
> > Kbuild variable in the makefile:
> >?
> > foo-objs := sub1.o sub2.o
> >?
> > I suppose that?
> >?
> > foo-y := sub1.o sub2.o
> >?
> > has the same semantic ? That's not very clear to me.
> Nope, not at all, stick with the "foo-objs" string instead please.
Hi Greg,
thanks for the clarification! However, I'm sorry but I'm still
confused: it's said in Documentation/kbuild/makefiles.txt on section
3.3, that if a module kernel is build from several sources file, we
have to use the module_name-y variable. Maybe a misunderstood the
context of this doc (the example is from in-tree kernel module) ?
> That should resolve your other issues here.
>?
> hope this helps,
Well, I tried again (with X-objs) but I've get the same issue :( No
hurry anyways, I have a scull driver to implements... :)
Thanks,
Colin
(PS: sorry for duplication)
prev parent reply other threads:[~2016-04-04 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 18:00 build external module splited into several files Colin Vidal
2016-04-04 18:47 ` Greg KH
2016-04-04 19:43 ` Colin Vidal [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=1459799007.2600.11.camel@cvidal.org \
--to=colin@cvidal.org \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).