32-bit unicode support

[ale5000-git]

Could you please create by default also the 32-bit unicode version?
The 32-bit version would work on both 32/64-bit systems and it is the best choice for a portable exe.

[jack6th]

I also want it.
Is it possible?

[avih]

Is it possible?

Yes.

I also want it.

You will have to compile it yourself. There are instructions which you should be able to follow - https://frippery.org/busybox/build.html .

Unicode busybox-w32 (in either 32 or 64 bit build) only works on Windows 10 and later, which, except old Windows 10 installations, is always 64 bit.

So to reduce confusion and management of binaries, only 64 bit Unicode busybox-w32 pre-built binary is provided.

[avih]

@rmyorston Can you please add the 64u variant to the build instructions page? EDIT: move it up with the examples of the normal 32/64 builds ;) Also, "only works in recent versions of windows", if you consider decade-old recent. Maybe just say win10?

@jack6th you will need to use make mingw64u_defconfig instead of the non-unicode 32/64 variants.

[ale5000-git]

32-bit isn't uncommon (if you exclude newbies that usually use only preinstalled OS), still with the changes discussed in the past the same exe could work without unicode also in Win 7 / 8 / old 10.

Ref: #423 (comment)

[rmyorston]

The build page on the website has been adjusted.

[avih]

The build page on the website has been adjusted.

Thanks, but I'm now realizing building 32 bit (or aarch) unicode is still non obvious.

Didn't we have a script which can take the 32/64(/a?) non-unicode config and output a unicode config?

If it still works, then maybe it's worth adding a note about it?

[ale5000-git]

In fact this is the most confusing thing.
Most people, when they see 64a/64u will understand it as ANSI/UNICODE when currently it is ARM64/AMD64.

[ale5000-git]

This is my suggestion for a clearer understanding:

busybox-32.exe
busybox-64.exe
busybox-64u.exe
busybox-arm64u.exe