Hi! > > Hmm, I think that it may be more clear to put the linux kernel Makefile > > part to the Makefile that is in the test directory, so that it will > > became: > > > > ifneq ($(KERNELRELEASE),) > > > > obj-m := $(addsuffix .o, $(MODULE_NAMES)) > > > > else > > > > top_srcdir ?= ../../../.. > > > > include $(top_srcdir)/include/mk/testcases.mk > > > > REQ_VERSION_MAJOR := 2 > > REQ_VERSION_PATCH := 6 > > MAKE_TARGETS := test01 test02 ... > > > > include $(top_srcdir)/include/mk/module.mk > > include $(top_srcdir)/include/mk/generic_leaf_target.mk > > > > endif > And "MODULE_NAMES := Module01 Module02" on the top of it, right?
Or directly written in the $(addsuffix ...) expression, or just write the obj-m := foo.o there, since it's in one file it does not matter. > > Or to use Kbuild file which should be preffered over Makefile, > > unfortunately the documentation does not say which kernel version gets > > the support for Kbuild for extrenal modules, so if it's a recent feature > > we must go with the Makefile. > > > It can be made backward compatible with just the include of that file in > the ifneq ($(KERNELRELEASE,)). But we have only one line, I don't think > it necessary to do so. Right. I've looked into the kernel git log and the Kbuild documentation was updated to mention the posibility to use Kbuild files around 2.6.33 which is still to late for us. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
