From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Building separate files for a kernel module
Date: Thu, 5 Apr 2018 17:02:02 +0200 [thread overview]
Message-ID: <20180405150202.GA32439@kroah.com> (raw)
In-Reply-To: <CAN19L9GzpC3=OFjdsb1fBgaM9a3S2YUP6rtnAqqKmRsTM-fRJA@mail.gmail.com>
On Thu, Apr 05, 2018 at 11:49:36AM -0300, Martin Galvan wrote:
> 2018-04-05 2:26 GMT-03:00 <valdis.kletnieks@vt.edu>:
> > On Wed, 04 Apr 2018 18:29:21 -0300, Martin Galvan said:
> >
> >> PS: Yes, I'm aware I could just add $(bar-objs) to mydriver-y and
> >> avoid building bar.a, but I really need to have those files as a
> >> separate library.
> >
> > What's driving the requirement for a separate library?
>
> I want my module to be DKMS-enabled, but since the 'bar' binaries
> don't use anything Linux-specific I don't want to distribute the
> sources for it.
Hahaha, good luck, please discuss this with a lawyer as to the
legalities involved. You are on your own here.
greg k-h
next prev parent reply other threads:[~2018-04-05 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 21:29 Building separate files for a kernel module Martin Galvan
2018-04-05 5:26 ` valdis.kletnieks at vt.edu
2018-04-05 14:49 ` Martin Galvan
2018-04-05 15:02 ` Greg KH [this message]
2018-04-09 17:19 ` Martin Galvan
2018-04-18 15:57 ` Daniel.
2018-04-18 15:57 ` Daniel.
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=20180405150202.GA32439@kroah.com \
--to=greg@kroah.com \
--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).