emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0c013f5fc7
busybox/sysklogd/Makefile

23 lines
464 B
Makefile
Raw Normal View History

Major rework of the directory structure and the entire build system. -Erik
2001-10-24 10:30:29 +05:30
# Makefile for busybox
#
fix typoe (buildddir -> builddir)
2005-04-21 07:19:05 +05:30
# Copyright (C) 1999-2005 by Erik Andersen <andersen@codepoet.org>
Major rework of the directory structure and the entire build system. -Erik
2001-10-24 10:30:29 +05:30
#
use the shorter license header
2005-09-24 12:46:29 +05:30
# Licensed under the GPL v2, see the file LICENSE in this tarball.
Major rework of the directory structure and the entire build system. -Erik
2001-10-24 10:30:29 +05:30
- 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 23:03:25 +05:30
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 13:16:08 +05:30
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 23:03:25 +05:30
endif
ifndef top_builddir
fix typoe (buildddir -> builddir)
2005-04-21 07:19:05 +05:30
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 23:03:25 +05:30
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 13:16:08 +05:30
srcdir=$(top_srcdir)/sysklogd
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 17:35:57 +05:30
SYSKLOGD_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 13:16:08 +05:30
include $(top_builddir)/Rules.mak
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 17:35:57 +05:30
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 13:16:08 +05:30
-include $(top_builddir)/.depend
Major rework of the directory structure and the entire build system. -Erik
2001-10-24 10:30:29 +05:30
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 17:35:57 +05:30
rm -f *.o *.a $(AR_TARGET)
Reference in New Issue Copy Permalink