From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Thu, 5 Apr 2018 17:02:02 +0200
Subject: Building separate files for a kernel module
In-Reply-To: <CAN19L9GzpC3=OFjdsb1fBgaM9a3S2YUP6rtnAqqKmRsTM-fRJA@mail.gmail.com>
References: <CAN19L9F9jKy_wtJ-BZTkHJa+z0TOUTT2wztj=GFN6fgJUR7d1Q@mail.gmail.com>
 <50983.1522905998@turing-police.cc.vt.edu>
 <CAN19L9GzpC3=OFjdsb1fBgaM9a3S2YUP6rtnAqqKmRsTM-fRJA@mail.gmail.com>
Message-ID: <20180405150202.GA32439@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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