hush/applets/Makefile

# Makefile for busybox
#
# Copyright (C) 1999-2005 by Erik Andersen <andersen@codepoet.org>
#
# Licensed under the GPL v2, see the file LICENSE in this tarball.

top_srcdir=..
top_builddir=..
srcdir=$(top_srcdir)/applets
APPLETS_DIR:=./
include $(top_builddir)/Rules.mak
include $(top_builddir)/.config
include $(srcdir)/Makefile.in
all: $(libraries-y)
-include $(top_builddir).depend

clean:
	rm -f *.o *.a $(AR_TARGET)
Oops. Forgot these.... 2001-10-24 05:26:42 +00:00			`# Makefile for busybox`
			`#`
use the shorter license header 2005-09-24 07:16:29 +00:00			`# Copyright (C) 1999-2005 by Erik Andersen <andersen@codepoet.org>`
Oops. Forgot these.... 2001-10-24 05:26:42 +00:00			`#`
use the shorter license header 2005-09-24 07:16:29 +00:00			`# Licensed under the GPL v2, see the file LICENSE in this tarball.`
Oops. Forgot these.... 2001-10-24 05:26:42 +00:00
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 2004-10-08 07:46:08 +00:00			`top_srcdir=..`
			`top_builddir=..`
			`srcdir=$(top_srcdir)/applets`
Completely rework the config system so that it no longer annoys me to work on the busybox development tree. This eliminates the use of recursive make, and once again allows us to run 'make' in a subdirectory with the expected result. And things are now much faster too. Greatly improved IMHO... -Erik 2002-04-12 12:05:57 +00:00			`APPLETS_DIR:=./`
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 2004-10-08 07:46:08 +00:00			`include $(top_builddir)/Rules.mak`
			`include $(top_builddir)/.config`
			`include $(srcdir)/Makefile.in`
Completely rework the config system so that it no longer annoys me to work on the busybox development tree. This eliminates the use of recursive make, and once again allows us to run 'make' in a subdirectory with the expected result. And things are now much faster too. Greatly improved IMHO... -Erik 2002-04-12 12:05:57 +00:00			`all: $(libraries-y)`
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 2004-10-08 07:46:08 +00:00			`-include $(top_builddir).depend`
Oops. Forgot these.... 2001-10-24 05:26:42 +00:00
			`clean:`
Completely rework the config system so that it no longer annoys me to work on the busybox development tree. This eliminates the use of recursive make, and once again allows us to run 'make' in a subdirectory with the expected result. And things are now much faster too. Greatly improved IMHO... -Erik 2002-04-12 12:05:57 +00:00			`rm -f .o .a $(AR_TARGET)`
Oops. Forgot these.... 2001-10-24 05:26:42 +00:00