From de1349a877b46b890325273cb0f84e7be4476bfe Mon Sep 17 00:00:00 2001 From: Ron Yorston Date: Thu, 15 Oct 2015 10:01:39 +0100 Subject: Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d9988c45e..bd5f3f628 100644 --- a/README.md +++ b/README.md @@ -4,9 +4,9 @@ Things may work for you, or may not. Things may never work because of huge diff ### Building -You need a MinGW compiler and a POSIX environment (so that `make menuconfig` works). I cross compile from Linux. On Fedora or RHEL/CentOS+EPEL installing the mingw32-gcc package will pull in everything needed. +You need a MinGW compiler and a POSIX environment (so that `make menuconfig` works). I cross-compile on Linux. On Fedora or RHEL/CentOS+EPEL installing mingw32-gcc (32-bit build) or mingw64-gcc (64-bit build) will pull in everything needed. -To start, run `make mingw32_defconfig`. You can then customize your build with `make menuconfig`. +To start, run `make mingw32_defconfig` or `make mingw64_defconfig`. You can then customize your build with `make menuconfig`. In particular you may need to adjust the compiler by going to Busybox Settings -> Build Options -> Cross Compiler Prefix @@ -19,4 +19,4 @@ Then just `make`. - Wildcard expansion is disabled by default, though it can be turned on at compile time. This only affects command line arguments to the binary: the BusyBox shell has full support for wildcards. - Handling of users, groups and permissions is totally bogus. The system only admits to knowing about the current user and always returns the same hardcoded uid, gid and permission values. - Some crufty old Windows code (Windows XP, cmd.exe) doesn't like forward slashes in environment variables. The -X shell option (which must be the first argument) prevents busybox-w32 from changing backslashes to forward slashes. If Windows programs don't run from the shell it's worth trying it. - - Currently only 32-bit builds of BusyBox work. If you want to install 32-bit BusyBox in a system directory on a 64-bit version of Windows you should put it in `C:\Windows\SysWOW64`, not `C:\Windows\System32`. On 64-bit systems the latter is for 64-bit binaries. + - If you want to install 32-bit BusyBox in a system directory on a 64-bit version of Windows you should put it in `C:\Windows\SysWOW64`, not `C:\Windows\System32` as you might expect. On 64-bit systems the latter is for 64-bit binaries. -- cgit v1.2.3-55-g6feb