From: malattia at linux.it
To: devel@acpica.org
Subject: [Devel] [patch 1/5] Allow overriding some of the CFLAGS
Date: Mon, 05 Jul 2010 21:03:25 +0900 [thread overview]
Message-ID: <20100705120817.527713917@linux.it> (raw)
In-Reply-To: 20100705120324.581857151@linux.it
[-- Attachment #1: Type: text/plain, Size: 3223 bytes --]
It makes it easier for package maintainers to override CFLAGS without touching
iasl specific defines and includes.
Signed-off-by: Mattia Dongili <malattia(a)linux.it>
---
compiler/Makefile | 6 +++++-
tools/acpiexec/Makefile | 6 +++++-
tools/acpisrc/Makefile | 5 ++++-
tools/acpixtract/Makefile | 5 ++++-
4 files changed, 18 insertions(+), 4 deletions(-)
Index: b/compiler/Makefile
===================================================================
--- a/compiler/Makefile 2010-07-02 21:42:26.849349488 +0900
+++ b/compiler/Makefile 2010-07-04 11:18:15.830519370 +0900
@@ -125,7 +125,8 @@
../osunixxf.c
NOMAN= YES
-CFLAGS+= -Wall -O2 -Wstrict-prototypes -D_LINUX -DACPI_ASL_COMPILER -I../include -I../compiler
+MK_CFLAGS = -DACPI_ASL_COMPILER -I../include -I../compiler
+CFLAGS= -Wall -Wstrict-prototypes -O2
#YACC= yacc
YACC= bison
@@ -141,6 +142,9 @@
LDLIBS = -lpthread -lrt
+%.o: %.c
+ $(CC) $(MK_CFLAGS) $(CFLAGS) -c -o $@ $<
+
aslmain : $(patsubst %.c,%.o, $(SRCS))
$(CC) $(LDFLAGS) $(patsubst %.c,%.o, $(SRCS)) \
$(LOADLIBES) $(LDLIBS) -o iasl
Index: b/tools/acpiexec/Makefile
===================================================================
--- a/tools/acpiexec/Makefile 2010-07-02 21:42:26.893349116 +0900
+++ b/tools/acpiexec/Makefile 2010-07-04 11:18:15.830519370 +0900
@@ -139,8 +139,12 @@
../../osunixxf.c
-CFLAGS+= -Wall -g -D_LINUX -DNDEBUG -D_CONSOLE -DACPI_EXEC_APP -D_MULTI_THREADED -Wstrict-prototypes -I../../include
+MK_CFLAGS = -DNDEBUG -D_CONSOLE -DACPI_EXEC_APP -D_MULTI_THREADED \
+ -I../../include
+CFLAGS = -Wall -Wstrict-prototypes -O2 -g
+%.o: %.c
+ $(CC) $(MK_CFLAGS) $(CFLAGS) -c -o $@ $<
acpiexec : $(patsubst %.c,%.o, $(SRCS))
$(CC) $(LDFLAGS) $(patsubst %.c,%.o, $(SRCS)) -lrt -lpthread -o $(PROG)
Index: b/tools/acpisrc/Makefile
===================================================================
--- a/tools/acpisrc/Makefile 2010-07-02 21:42:26.877349353 +0900
+++ b/tools/acpisrc/Makefile 2010-07-04 11:18:15.838518967 +0900
@@ -4,8 +4,11 @@
SRCS= ascase.c asconvrt.c asfile.c asmain.c asremove.c astable.c \
asutils.c osunixdir.c ../../common/getopt.c
-CFLAGS+= -Wall -O2 -D_LINUX -DACPI_APPLICATION -Wstrict-prototypes -I../../include
+MK_CFLAGS= -DACPI_APPLICATION -I../../include
+CFLAGS= -Wall -Wstrict-prototypes -O2
+%.o: %.c
+ $(CC) $(MK_CFLAGS) $(CFLAGS) -c -o $@ $<
aslmain : $(patsubst %.c,%.o, $(SRCS))
$(CC) $(LDFLAGS) $(patsubst %.c,%.o, $(SRCS)) -o $(PROG)
Index: b/tools/acpixtract/Makefile
===================================================================
--- a/tools/acpixtract/Makefile 2010-07-02 21:42:26.861349031 +0900
+++ b/tools/acpixtract/Makefile 2010-07-04 11:18:15.838518967 +0900
@@ -3,8 +3,11 @@
PROG= acpixtract
SRCS= acpixtract.c
-CFLAGS+= -Wall -O2 -D_LINUX -DACPI_APPLICATION -Wstrict-prototypes -I../../include
+MK_CFLAGS= -DACPI_APPLICATION -I../../include
+CFLAGS= -Wall -Wstrict-prototypes -O2
+%.o: %.c
+ $(CC) $(MK_CFLAGS) $(CFLAGS) -c -o $@ $<
acpixtract : $(patsubst %.c,%.o, $(SRCS))
$(CC) $(LDFLAGS) $(patsubst %.c,%.o, $(SRCS)) -o $(PROG)
reply other threads:[~2010-07-05 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100705120817.527713917@linux.it \
--to=devel@acpica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.