diff options
| author | Ron Yorston <rmy@pobox.com> | 2015-10-15 10:01:39 +0100 |
|---|---|---|
| committer | Ron Yorston <rmy@pobox.com> | 2015-10-15 10:01:39 +0100 |
| commit | de1349a877b46b890325273cb0f84e7be4476bfe (patch) | |
| tree | ac7d7f0e79f0215a11c30fee78b3d2d33dad5192 | |
| parent | 0b2423b192c3fc48e7f739eb9ce26587ebbe5fcd (diff) | |
| download | busybox-w32-de1349a877b46b890325273cb0f84e7be4476bfe.tar.gz busybox-w32-de1349a877b46b890325273cb0f84e7be4476bfe.tar.bz2 busybox-w32-de1349a877b46b890325273cb0f84e7be4476bfe.zip | |
Update README.md
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
| @@ -4,9 +4,9 @@ Things may work for you, or may not. Things may never work because of huge diff | |||
| 4 | 4 | ||
| 5 | ### Building | 5 | ### Building |
| 6 | 6 | ||
| 7 | 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. | 7 | 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. |
| 8 | 8 | ||
| 9 | To start, run `make mingw32_defconfig`. You can then customize your build with `make menuconfig`. | 9 | To start, run `make mingw32_defconfig` or `make mingw64_defconfig`. You can then customize your build with `make menuconfig`. |
| 10 | 10 | ||
| 11 | In particular you may need to adjust the compiler by going to Busybox Settings -> Build Options -> Cross Compiler Prefix | 11 | In particular you may need to adjust the compiler by going to Busybox Settings -> Build Options -> Cross Compiler Prefix |
| 12 | 12 | ||
| @@ -19,4 +19,4 @@ Then just `make`. | |||
| 19 | - 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. | 19 | - 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. |
| 20 | - 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. | 20 | - 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. |
| 21 | - 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. | 21 | - 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. |
| 22 | - 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. | 22 | - 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. |