busybox-w32/scripts/basic, branch su_cmd2

Merge branch 'busybox' into merge

2023-04-09T10:24:09+00:00

fixdep: avoid underflow when end of entry doesn't coincide with EOF

2023-02-27T12:09:44+00:00

Bug: https://bugs.gentoo.org/893776 Closes: https://bugs.busybox.net/show_bug.cgi?id=15326 Signed-off-by: Arsen Arsenović Signed-off-by: Denys Vlasenko

build system: allow building with w64devkit

2022-10-30T08:25:45+00:00

Make some adjustments to the build system to allow busybox-w32 to be built with w64devkit: - Strip drive prefix from CURDIR in Makefile to avoid confusing make with colons. - Limit file redirection to a subshell in the usage_compressed and embedded_scripts scripts. Otherwise it isn't possible to move the open generated file on Windows. - Change the option tests in Kbuild.include to allow for /dev/null not existing on Windows. - Create host binaries without a '.exe' extension. Otherwise they're rebuilt more often than necessary. - Modify split-include.c to allow for Windows' popen() not expanding wildcards. (GitHub issue #239)

Merge branch 'busybox' into merge

2021-05-14T07:17:12+00:00

fix "warning array subscript has type 'char'"

2021-04-14T17:12:43+00:00

Signed-off-by: Denys Vlasenko

build system: avoid build failure during bisection

2021-04-13T16:26:46+00:00

Commit 4bdc914ff (build system: fix compiler warnings) added a test on the return value of fgets() in split-include.c. During bisection it's possible to go back to a state where a configuration value didn't exist. This results in an empty include file corresponding to the missing feature. If a subsequent bisection returns to a state where the feature exists split-include treats the empty file as an error and the build fails. Add a call to ferror() to distinguish between fgets() failing due to an error and due to there being no data to read. Signed-off-by: Ron Yorston Signed-off-by: Denys Vlasenko

.gitignore: support building on Windows

2021-02-21T10:35:21+00:00

These items are already listed, albeit without `.exe` suffix. Presumably, this is because BusyBox-w32 is traditionally cross-compiled on Linux. However, we are about to introduce a CI build definition that builds BusyBox-w32 in MSYS2 (using mingw-w64-gcc), meaning that those executables might very well exist _with_ `.exe` suffix. Let's ignore those, too. Signed-off-by: Johannes Schindelin

Merge branch 'busybox' into merge

2019-01-10T08:38:15+00:00

build system: fix compiler warnings

2019-01-06T19:12:16+00:00

Signed-off-by: Denys Vlasenko

kbuild: support at least non-interactive mode on Windows

2017-07-14T14:14:30+00:00

without POSIX, kbuild has some trouble compiling its support executables. Luckily, the parts that really lean on POSIX functionality are pretty much all only needed when configuring the build interactively. When compiling BusyBox for Win32, we do not actually need interactive configuration at all: we simply choose the default. Therefore, a lot of the stuff that is typically built for the Kconfig system is totally unnecessary (such as: compiling documentation via fork()&exec(), changing the window size, etc). Liberally put all of the problematic code behind #ifndef __MINGW32__ guards, just to get `make mingw64_defconfig` going in Git for Windows' SDK (which is a special-purpose version of MSYS2). Signed-off-by: Johannes Schindelin