Messages in this thread | | | Date | Thu, 25 Jun 2009 19:47:48 +0200 | From | Sam Ravnborg <> | Subject | Re: 2.6 Makefile replacement for VPATH |
| |
> I refer to VPATH with regards to the situation where you can have > multiple Makefiles target the same source file to build different > objects. In particular, we are using the same source file recompiled > with different options to be able to support different devices.
Several obvious solutions.
a) Let the same driver handle multiple devices - we do this in very often.
b) Keep all shared functionality in a dedicated lib* module, and have thin wrappers for the actual drivers. See libata for example.
c) The ugly where you have a thin dedicated .C file for each driver that includes the source they share.
> How do others handle this? Do they just move their driver outside of > the kernel Makefiles so they can iterate through the two builds via > traditional Make routines? That will most likely not work.
Sam
| |