[PATCH 00/39] Windows port, base and archival/

Rob Landley rob at landley.net
Sun Apr 18 06:26:38 UTC 2010


On Thursday 15 April 2010 14:58:20 Nguyễn Thái Ngọc Duy wrote:
> Hi,
>
> This is something I think good enough to go upstream. The rest of my
> work is on:
>
> git://github.com/pclouds/busybox-w32.git wip
>
> Caveat: crappy, constantly rebased stuff as it's work in progress.
> However it may tell where this port leads to. If we don't count
> regex.c there are about 3k more lines to go.
>
>
> Nguyá»
n Thái Ngọc Duy (39):
>   ar: do not filter listing if there is no extra argument
>
> This is a regression, not related to Windows port at all.
>
>   Config.in: add target platform selection
>   Config.in: add target platform WIN32

No.  You don't have to config busybox for arm or mips or powerpc, you just 
build it.  The compiler defines macros that tell you what target you're 
building on.  For example, on Linux  there's:

#define __linux__ 1

Do this:

  gcc -dM -E - < /dev/null


>   Config.in: disable all commmands when TARGET_WIN32 is selected

So you're forcing the rest of us to carry annotations on every single command 
ever about what you do and don't support.

Why is this our problem?

>   win32: Refuse to build on Windows/MinGW unless TARGET_WIN32 is
>     selected

Wrong.

> Very basic stuff just enough to make a succesful build. You
> will have a nice 52K busybox.exe, with no applets.

On Linux, or allnoconfig is 10k.  (I'm not sure _why_ it's 10k, I thought it 
used to be more like 5k, but oh well...)

Rob
-- 
Latency is more important than throughput. It's that simple. - Linus Torvalds


More information about the busybox mailing list