Things may work for you, or may not. Things may never work because of huge differences between Linux and Windows. Or things may work in future, if you report the problem on GitHub or GitLab. If you don't have an account on one of those or you'd prefer to communicate privately you can email rmy@pobox.com.
Additional information is available from the BusyBox for Windows web page. In particular:
You need a MinGW toolchain and a POSIX environment. I cross-compile on Linux. On Fedora the following should pull in everything required:
dnf install gcc make ncurses-devel perl-Pod-Html
dnf install mingw64-gcc
(for a 64-bit build)
dnf install mingw32-gcc
(for a 32-bit build)
On Microsoft Windows you can install w64devkit. Get the -i686
variant for a 32-bit build. Unzip the file and run w64devkit/w64devkit.exe
.
On either Linux or Windows the commands make mingw64_defconfig
or make mingw32_defconfig
will pick up the default configuration. You can then customize your build with make menuconfig
or by editing .config
, if you know what you're doing.
Then just make
.
See the Building busybox-w32 web page for additional information.
c:/path
or //host/share/path
c:path
/path
path
C:\Windows\SysWOW64
, not C:\Windows\System32
as you might expect. On 64-bit systems the latter is for 64-bit binaries.BB_TERMINAL_MODE=1
to force the use of literal ANSI escapes or BB_TERMINAL_MODE=0
to emulate them using the Windows console API.BB_OVERRIDE_APPLETS
to a space-separated list of applet names. Thus, to use an external make
in preference to the built-in applet set BB_OVERRIDE_APPLETS="make"
.if=/dev/urandom
as the input file to dd
. The same emulation of /dev/urandom
is used internally by the shred
utility and to support https in wget
. Serious users of random numbers may, of course, wish to make alternative arrangements.