Re: Trouble making module

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Wed, Oct 13, 2010 at 3:57 PM, Wouter Simons <lkml@xxxxxxxxxxxxxxxx> wrote:
On 10/13/2010 12:20 PM, Robert P. J. Day wrote:
> On Wed, 13 Oct 2010, Dave Hylands wrote:
>
>> That looks reasonable, although the normal way of specifying multiple
>> files in an object is like:
>>
>> obj-m := composite_driver.o
>> composite_driver-objs := file1.o file2.o
>>
>> which is what you mentioned with the excerpt from the kbuild documenation.
>>
>> ...snip...
>>
>>> (did I get it right the second time around? ;-)
>>
>> Mostly. You used composite_driver-y rather then composite_driver-objs
>
>   from memory, there are two ways to do that, an old way and a new way
> although the coffee hasn't kicked in sufficiently to allow me to
> remember which one is which.  help, anyone?
>
I believe composite_driver-y works for CONFIG_ based inclusion. Such as:

obj-$(CONFIG_COMP_DRIVER)       := comp_driver.o
comp_driver-y                   := file1.o file2.o
comp_driver-$(CONFIG_COMP_DRIVER_OPTIONAL) += optional.o

Again, this is just what I learned form the kbuild documents and I am no
expert.

Wouter
Guys I sorted it out .
Thank you all for your replies .
Gaurav's mail really helped me out .
I actually put a space in  M= $(PWD) .
Note the whitespace between = and $ . That was the root of all causes :-)
Hope you people dont spent most of your time debugging the make file . its really irritating

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux