From: [EMAIL PROTECTED]
quote
noinst_LIBRARIES = normal.a normal-feature.a
normal_a_SOURCES = [bunch of files]
normal_feature_a_SOURCES = $(normal_a_SOURCES)
normal_feature_a_CFLAGS = -DFEATURE
/quote
...
Where have I gone wrong?
Of course, when my source files are C++ files the _CFLAGS
Drummonds, Scott B [EMAIL PROTECTED] writes:
From: [EMAIL PROTECTED]
quote
noinst_LIBRARIES = normal.a normal-feature.a
normal_a_SOURCES = [bunch of files]
normal_feature_a_SOURCES = $(normal_a_SOURCES)
normal_feature_a_CFLAGS = -DFEATURE
/quote
...
Where have I gone wrong?
Of
I didn't. But I do now.
Thanks,
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Ben Pfaff
Sent: Tuesday, February 24, 2004 1:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Target-specific CFLAGS
Drummonds, Scott B [EMAIL PROTECTED] writes
On Tue, 24 Feb 2004, Ben Pfaff wrote:
Of course, when my source files are C++ files the _CFLAGS extension does
nothing. Changing this to _CPPFLAGS fixed the problem. Duh.
You know that CPPFLAGS is for the C preprocessor and CXXFLAGS is
for the C++ compiler, right?
This distinction is
Bob Friesenhahn [EMAIL PROTECTED] writes:
On Tue, 24 Feb 2004, Ben Pfaff wrote:
Of course, when my source files are C++ files the _CFLAGS extension does
nothing. Changing this to _CPPFLAGS fixed the problem. Duh.
You know that CPPFLAGS is for the C preprocessor and CXXFLAGS is
for the
On Tue, 24 Feb 2004, Ben Pfaff wrote:
Bob Friesenhahn [EMAIL PROTECTED] writes:
On Tue, 24 Feb 2004, Ben Pfaff wrote:
Of course, when my source files are C++ files the _CFLAGS extension does
nothing. Changing this to _CPPFLAGS fixed the problem. Duh.
You know that CPPFLAGS is
