From: Sam Ravnborg <sam@ravnborg.org>
To: Kyle Hubert <khubert@cray.com>
Cc: linux-kernel@vger.kernel.org, Igor Gorodetsky <igorodet@cray.com>
Subject: Re: 2.6 Makefile replacement for VPATH
Date: Thu, 25 Jun 2009 19:47:48 +0200 [thread overview]
Message-ID: <20090625174748.GA15168@uranus.ravnborg.org> (raw)
In-Reply-To: <20090625163916.GN6248@cray.com>
> 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
next prev parent reply other threads:[~2009-06-25 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 16:39 2.6 Makefile replacement for VPATH Kyle Hubert
2009-06-25 17:47 ` Sam Ravnborg [this message]
2009-06-25 20:35 ` Kyle Hubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090625174748.GA15168@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=igorodet@cray.com \
--cc=khubert@cray.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox