aboutsummaryrefslogtreecommitdiff
path: root/Rules.mak
diff options
context:
space:
mode:
authorandersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277>2004-10-08 07:46:08 +0000
committerandersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277>2004-10-08 07:46:08 +0000
commitf6d0a8e7cb47688ed3786894219b373e87ac8a49 (patch)
treee81ce57a92acc0653374e1d262039562855d16ec /Rules.mak
parent5ba0134aa31b2cd9a11772fcd9e39d722347467e (diff)
downloadbusybox-w32-f6d0a8e7cb47688ed3786894219b373e87ac8a49.tar.gz
busybox-w32-f6d0a8e7cb47688ed3786894219b373e87ac8a49.tar.bz2
busybox-w32-f6d0a8e7cb47688ed3786894219b373e87ac8a49.zip
egor duda writes:
Hi! I've created a patch to busybox' build system to allow building it in separate tree in a manner similar to kbuild from kernel version 2.6. That is, one runs command like 'make O=/build/some/where/for/specific/target/and/options' and everything is built in this exact directory, provided that it exists. I understand that applyingc such invasive changes during 'release candidates' stage of development is at best unwise. So, i'm currently asking for comments about this patch, starting from whether such thing is needed at all to whether it coded properly. 'make check' should work now, and one make creates Makefile in build directory, so one can run 'make' in build directory after that. One possible caveat is that if we build in some directory other than source one, the source directory should be 'distclean'ed first. egor git-svn-id: svn://busybox.net/trunk/busybox@9320 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'Rules.mak')
-rw-r--r--Rules.mak10
1 files changed, 3 insertions, 7 deletions
diff --git a/Rules.mak b/Rules.mak
index 43cf24226..63b80f3a5 100644
--- a/Rules.mak
+++ b/Rules.mak
@@ -42,7 +42,7 @@ LD = $(CROSS)ld
42NM = $(CROSS)nm 42NM = $(CROSS)nm
43STRIP = $(CROSS)strip 43STRIP = $(CROSS)strip
44CPP = $(CC) -E 44CPP = $(CC) -E
45MAKEFILES = $(TOPDIR).config 45# MAKEFILES = $(top_builddir)/.config
46 46
47# What OS are you compiling busybox for? This allows you to include 47# What OS are you compiling busybox for? This allows you to include
48# OS specific things, syscall overrides, etc. 48# OS specific things, syscall overrides, etc.
@@ -80,7 +80,7 @@ BB_SRC_DIR=
80#GCCINCDIR:=$(shell gcc -print-search-dirs | sed -ne "s/install: \(.*\)/\1include/gp") 80#GCCINCDIR:=$(shell gcc -print-search-dirs | sed -ne "s/install: \(.*\)/\1include/gp")
81 81
82WARNINGS=-Wall -Wstrict-prototypes -Wshadow 82WARNINGS=-Wall -Wstrict-prototypes -Wshadow
83CFLAGS=-I$(TOPDIR)include 83CFLAGS=-I$(top_builddir)/include -I$(top_srcdir)/include -I$(srcdir)
84ARFLAGS=-r 84ARFLAGS=-r
85 85
86#-------------------------------------------------------- 86#--------------------------------------------------------
@@ -102,7 +102,7 @@ endif
102 102
103# Pull in the user's busybox configuration 103# Pull in the user's busybox configuration
104ifeq ($(filter $(noconfig_targets),$(MAKECMDGOALS)),) 104ifeq ($(filter $(noconfig_targets),$(MAKECMDGOALS)),)
105-include $(TOPDIR).config 105-include $(top_builddir)/.config
106endif 106endif
107 107
108# A nifty macro to make testing gcc features easier 108# A nifty macro to make testing gcc features easier
@@ -189,12 +189,8 @@ endif
189# have a chance of winning. 189# have a chance of winning.
190CFLAGS += $(CFLAGS_EXTRA) 190CFLAGS += $(CFLAGS_EXTRA)
191 191
192%.o: %.c
193 $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -c -o $@ $<
194
195.PHONY: dummy 192.PHONY: dummy
196 193
197 194
198
199.EXPORT_ALL_VARIABLES: 195.EXPORT_ALL_VARIABLES:
200 196