Message-ID: <46EB198D.2040208@gmail.com>
Date: Sat, 15 Sep 2007 01:30:21 +0200
From: Rene Herman <rene.herman@gmail.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: "H. Peter Anvin" <hpa@zytor.com>
CC: Kai Germaschewski <kai@germaschewski.name>,
       Sam Ravnborg <sam@ravnborg.org>,
       Linux Kernel <linux-kernel@vger.kernel.org>,
       ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: Per option CFLAGS?
References: <46EB141A.7090200@gmail.com> <46EB1599.4020806@zytor.com>
In-Reply-To: <46EB1599.4020806@zytor.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1233
Lines: 42

On 09/15/2007 01:13 AM, H. Peter Anvin wrote:

> Rene Herman wrote:

>> I have a single file foo.c that I want to generate two (ALSA) modules
>> from, snd-foo2000.ko and snd-foo2001.ko, by compiling with either
>> FOO2000 or FOO2001 defined.
>>
>> I can do this, and ALSA does this a few times, by providing dummy
>> foo2000.c and foo2001.c files, like:
>>
>> === foo2000.c
>> #define FOO2000
>> #include "foo.c"
>> ===
>>
>> and a regular Makefile
>>
>> ===
>> foo2000-objs := foo2000.o
>> foo2001-objs := foo2001.o
>>
>> obj-$(CONFIG_SND_FOO2000) += snd-foo2000.o
>> obj-$(CONFIG_SND_F002001) += snd-foo2001.o
>> ===
>>
>> That #include is a little lame though. Is there a nicer way? I noticed
>> the per-file CFLAGS, but given that it's one source file for both, that
>> doesn't fit.
>>
> 
> The stub source file is usually considered a good way to do this.

Mmm. If I'll have to live with it, I can, but thought I'd ask if there was 
some nice build trickery available instead.

Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/