emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
ebd1355828
busybox/networking/libiproute/Makefile

37 lines
1.1 KiB
Makefile
Raw Normal View History

IP applet by Bastian Blank <waldi@debian.org>
2002-11-10 07:03:55 +05:30
# Makefile for busybox
#
Remove trailing whitespace. Update copyright to include 2004.
2004-03-15 13:59:22 +05:30
# Copyright (C) 1999-2004 by Erik Andersen <andersen@codepoet.org>
IP applet by Bastian Blank <waldi@debian.org>
2002-11-10 07:03:55 +05:30
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
#
- 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
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_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)/networking/libiproute
IP applet by Bastian Blank <waldi@debian.org>
2002-11-10 07:03:55 +05:30
LIBIPROUTE_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
IP applet by Bastian Blank <waldi@debian.org>
2002-11-10 07:03:55 +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
IP applet by Bastian Blank <waldi@debian.org>
2002-11-10 07:03:55 +05:30
clean:
rm -f *.o *.a $(AR_TARGET)
Reference in New Issue Copy Permalink