Apple-2gs-SW/hush
1
0
Fork 0
mirror of https://github.com/sheumann/hush.git synced 2024-11-04 14:05:24 +00:00
Code Issues Projects Releases Wiki Activity
081e38483e
hush/libbb/Makefile

30 lines
602 B
Makefile
Raw Normal View History

Major rework of the directory structure and the entire build system. -Erik
2001-10-24 05:00:29 +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>
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
#
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.
Split error messages into separate files. Update libbb.h, per suggestion from Vladimir, to include __attribute__((format (printf ...))) stuff -Erik
2001-03-19 19:24:06 +00:00
- use absolute path for top_builddir and top_srcdir. Fixes make trying to include the very same file in an endless loop.
2006-03-02 17:33:25 +00:00
ifndef top_srcdir
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=..
- use absolute path for top_builddir and top_srcdir. Fixes make trying to include the very same file in an endless loop.
2006-03-02 17:33:25 +00:00
endif
ifndef top_builddir
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_builddir=..
- use absolute path for top_builddir and top_srcdir. Fixes make trying to include the very same file in an endless loop.
2006-03-02 17:33:25 +00:00
endif
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
srcdir=$(top_srcdir)/libbb
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
LIBBB_DIR:=./
Attempt to address Shaun Jackman's problem adding "busybox: busybox.bflt" to .config.mak.
2006-07-06 20:02:47 +00:00
# Ensure "all" is still the default target when make is run by itself in
# libbb, even if the files we include define rules for targets.
all:
pull Rules.mak from top_srcdir as pointed out by Robert P. J. Day on the mailing list
2006-05-13 02:33:09 +00:00
include $(top_srcdir)/Rules.mak
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)/.config
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
include Makefile.in
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
Split error messages into separate files. Update libbb.h, per suggestion from Vladimir, to include __attribute__((format (printf ...))) stuff -Erik
2001-03-19 19:24:06 +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)
Reference in New Issue Copy Permalink