aboutsummaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorandersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277>2004-10-08 07:46:08 +0000
committerandersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277>2004-10-08 07:46:08 +0000
commitf6d0a8e7cb47688ed3786894219b373e87ac8a49 (patch)
treee81ce57a92acc0653374e1d262039562855d16ec /TODO
parent5ba0134aa31b2cd9a11772fcd9e39d722347467e (diff)
downloadbusybox-w32-f6d0a8e7cb47688ed3786894219b373e87ac8a49.tar.gz
busybox-w32-f6d0a8e7cb47688ed3786894219b373e87ac8a49.tar.bz2
busybox-w32-f6d0a8e7cb47688ed3786894219b373e87ac8a49.zip
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 git-svn-id: svn://busybox.net/trunk/busybox@9320 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'TODO')
0 files changed, 0 insertions, 0 deletions