Apple-2gs-SW/hush
1
0
Fork 0
mirror of https://github.com/sheumann/hush.git synced 2024-11-05 06:07:00 +00:00
Code Issues Projects Releases Wiki Activity
84cb76733f
hush/coreutils/Makefile

20 lines
428 B
Makefile
Raw Normal View History

Merge fileutils, textutils and shellutils into coreuils
2003-02-15 10:53:40 +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>
Merge fileutils, textutils and shellutils into coreuils
2003-02-15 10:53:40 +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.
Merge fileutils, textutils and shellutils into coreuils
2003-02-15 10:53:40 +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)/coreutils
Merge fileutils, textutils and shellutils into coreuils
2003-02-15 10:53:40 +00:00
SHELLUTILS_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
Merge fileutils, textutils and shellutils into coreuils
2003-02-15 10:53:40 +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
Merge fileutils, textutils and shellutils into coreuils
2003-02-15 10:53:40 +00:00
clean:
rm -f *.o *.a $(AR_TARGET)
Reference in New Issue Copy Permalink