Age | Commit message (Collapse) | Author |
|
|
|
Not buying it, eh?
I know I said new features before 1.1, but, well... (I was weak!)
The config file and hotplug modes aren't implemented yet. Might take a stab at
those tomorrow. (I _should_ go back to focusing on the bug triage list.)
|
|
util-linux/Makefile.in for switch_root applet
|
|
|
|
find it (and tweak defconfig to catch up).
|
|
|
|
|
|
|
|
some more work to shrink them down.
|
|
|
|
stuff in it
|
|
|
|
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
|
|
transparently remap 32-bit interfaces to actually use 64 bit interfaces.
-Erik
|
|
|
|
|
|
|
|
but I then completely reworked the fdformat utility to comply
with the current busybox way of doing things.
|
|
|
|
|
|
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
|