<feed xmlns='http://www.w3.org/2005/Atom'>
<title>busybox-w32/scripts, branch su_cmd</title>
<subtitle>A mirror of https://github.com/rmyorston/busybox-w32.git
</subtitle>
<id>https://git.lua4.win/busybox-w32/atom?h=su_cmd</id>
<link rel='self' href='https://git.lua4.win/busybox-w32/atom?h=su_cmd'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/'/>
<updated>2023-04-09T10:24:09+00:00</updated>
<entry>
<title>Merge branch 'busybox' into merge</title>
<updated>2023-04-09T10:24:09+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2023-04-09T10:24:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=d9f2ea8628452f787e02dd0e496af612a2e94578'/>
<id>urn:sha1:d9f2ea8628452f787e02dd0e496af612a2e94578</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fixdep: avoid underflow when end of entry doesn't coincide with EOF</title>
<updated>2023-02-27T12:09:44+00:00</updated>
<author>
<name>Arsen Arsenović</name>
<email>arsen@gentoo.org</email>
</author>
<published>2023-02-21T19:20:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=2d4a3d9e6c1493a9520b907e07a41aca90cdfd94'/>
<id>urn:sha1:2d4a3d9e6c1493a9520b907e07a41aca90cdfd94</id>
<content type='text'>
Bug: https://bugs.gentoo.org/893776
Closes: https://bugs.busybox.net/show_bug.cgi?id=15326
Signed-off-by: Arsen Arsenović &lt;arsen@gentoo.org&gt;
Signed-off-by: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
</content>
</entry>
<entry>
<title>build system: allow monochrome 'make menuconfig'</title>
<updated>2022-11-16T14:43:33+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2022-11-16T14:43:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=13b71ecafba53ebe8e4f88f9af70170b032ba408'/>
<id>urn:sha1:13b71ecafba53ebe8e4f88f9af70170b032ba408</id>
<content type='text'>
'make menuconfig' uses a hardcoded colour palette which may be
difficult to read.  Add support for the 'COLORS' environment
variable.  Setting this to '0' will cause 'make menuconfig' to
be displayed in black and white.

(GitHub issue #273)
</content>
</entry>
<entry>
<title>win32: native make menuconfig: support search</title>
<updated>2022-11-13T15:27:03+00:00</updated>
<author>
<name>Avi Halachmi (:avih)</name>
<email>avihpit@yahoo.com</email>
</author>
<published>2022-11-13T08:43:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=5dd110f70b3a960a1be7fc6070584d764ec7ca60'/>
<id>urn:sha1:5dd110f70b3a960a1be7fc6070584d764ec7ca60</id>
<content type='text'>
Previously, pressing slash to search at the menu aborted the menu
program ('mconf'), because regexp is not available with native mingw.

Now it works, but the search is of plain string rather than regexp.
</content>
</entry>
<entry>
<title>build system: try harder to detect w64devkit</title>
<updated>2022-11-12T08:56:52+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2022-11-12T08:56:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=80732e16e0a73965287a4d31c95831035743c484'/>
<id>urn:sha1:80732e16e0a73965287a4d31c95831035743c484</id>
<content type='text'>
We need to build the supplied PDCurses code when using w64devkit.
This was being detected by checking for the W64DEVKIT environment
variable, but this is only defined if w64devkit is started via
w64devkit.exe.

Set W64DEVKIT ourselves if HOSTCC targets the mingw32 platform.
This won't be the case when cross-compiling on Linux but will
for w64devkit and MSYS2 MINGW32/64.

The build won't work properly for MSYS2 MINGW32/64, but it doesn't
work when using the supplied curses library either.  'make menuconfig'
requires the use of MSYS2 MSYS, and HOSTCC there targets msys.
</content>
</entry>
<entry>
<title>build system: silence compiler warning</title>
<updated>2022-11-08T08:47:44+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2022-11-08T08:36:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=5507c8744566a7100d2da3cfa0decc005783a58e'/>
<id>urn:sha1:5507c8744566a7100d2da3cfa0decc005783a58e</id>
<content type='text'>
The compiler in MSYS2 warns that strcasecmp(3) isn't declared in
scripts/kconfig/lxdialog/checklist.c.  Add the appropriate include
to silence this warning.
</content>
</entry>
<entry>
<title>win32: fix ESC/CR handling in 'make menuconfig'</title>
<updated>2022-11-07T20:48:07+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2022-11-07T20:38:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=14e51376ea1d4c3888ea820b17f774a474e42504'/>
<id>urn:sha1:14e51376ea1d4c3888ea820b17f774a474e42504</id>
<content type='text'>
The WIN32 code in the 'mconf' build program should truncate the
exit status from dialogs as if it were passed through WEXITSTATUS.
The text dialog, for example, returns a status of -1 when ESC or
CR is pressed.  'mconf' expects to see this as 255.
</content>
</entry>
<entry>
<title>Provide PDCurses source for w64devkit build</title>
<updated>2022-11-07T13:49:52+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2022-11-07T11:29:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=863342aef089f064afb65d7c344a0d254c30d155'/>
<id>urn:sha1:863342aef089f064afb65d7c344a0d254c30d155</id>
<content type='text'>
w64devkit doesn't ship a curses library.  Provide a cut-down copy
of PDCurses which is sufficient to allow 'make menuconfig' to work
in w64devkit.
</content>
</entry>
<entry>
<title>win32: allow 'make menuconfig' in native builds</title>
<updated>2022-11-07T13:49:46+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2022-11-07T11:15:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=f8aeca9d9e387be17c8ee96da47e2aea146dc8ee'/>
<id>urn:sha1:f8aeca9d9e387be17c8ee96da47e2aea146dc8ee</id>
<content type='text'>
'make menuconfig' is a build option to allow changes to be made
to the BusyBox configuration.  It's a bit friendlier than using
a text editor on the .config file.

Previously 'menuconfig' was only available when cross-compiling
on a Linux/Unix platform.  The 'mconf' build program has been
ported to WIN32 so it's now able to run the 'lxdialog' program
which displays the configuration dialogs.

Building 'lxdialog' is somewhat awkward in MSYS2.  The MINGW32/64
build environments generate WIN32 executables for 'lxdialog'.
These doesn't work properly in the MSYS2 console.

For 'menuconfig' to work it's necessary to run it in an MSYS
build environment.  This generates an MSYS binary which works
in the MSYS2 console.  busybox-w32 should then be built in a
MINGW32/64 build environment.  Doing so will generate additional
copies of the build programs without a '.exe' suffix:  the MSYS
build environment adds '.exe' to binaries it builds.  This breaks
'menuconfig'.

To configure an MSYS build environment use:

   pacman -S gcc ncurses-devel
</content>
</entry>
<entry>
<title>build system: fix breakage affecting MSYS2 build</title>
<updated>2022-10-30T08:35:01+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2022-10-30T08:35:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=663319cec41bbff8b6e0e47fee7fedc84acfeafc'/>
<id>urn:sha1:663319cec41bbff8b6e0e47fee7fedc84acfeafc</id>
<content type='text'>
Upstream changes to the embedded_scripts and mkconfigs scripts
resulted in busybox-w32 failing to build with MSYS2.

bzip2 in MSYS2 detects stdout redirected to /dev/null as a terminal
and returns a non-zero exit status.  Since the test is only for
the existence of bzip2, not its functionality, even an exit status
of 1 is OK.  Only fail if the exit status is 127.
</content>
</entry>
</feed>
