SteveL

What I want to do is be able to build a module both inside and outside of the kernel build system.

• Inside=at the top level of the Linux sources do: make menuconfig, make etc
• Outside=just go into a working directory with the module source in and type 'make'

In my Kbuild I have:

obj-$(CONFIG_THING) := thing.o
thing-y := thing_1.o \
thing_2.o

This works when I build within the kernel build system (make menuconfig, make etc...)
when I set CONFIG_THING to m via the Kconfig system I get a thing.ko built.
when I set CONFIG_THING to y via the Kconfig system I get thing support built into the kernel.

I thought that a Makefile similar to that below would help, but obviously CONFIG_THING does not
get set correctly.

ifneq ($(KERNELRELEASE),)
include Kbuild
else
# Normal Makefile
KERNELDIR := /lib/modules/`uname -r`/build
CONFIG_THING = m
all:
$(MAKE) -C $(KERNELDIR) M=`pwd` $@

# Module clean up
clean:
$(MAKE) -C $(KERNELDIR) M=`pwd` clean

endif

Is there any way I can force CONFIG_THING to be 'm' in order to reuse the Kbuild file?

Looking for Linux Hosting? Click Here

SteveL

Solved!

In my Makefile I added 'CONFIG_THING=m' to the make call, thus:

all:
$(MAKE) -C $(KERNELDIR) M=`pwd` $@ CONFIG_THING=m

I'm pretty sure that does what I want.