<feed xmlns='http://www.w3.org/2005/Atom'>
<title>busybox-w32/scripts/mk_mingw64u_defconfig, branch cron_changes</title>
<subtitle>A mirror of https://github.com/rmyorston/busybox-w32.git
</subtitle>
<id>https://git.lua4.win/busybox-w32/atom?h=cron_changes</id>
<link rel='self' href='https://git.lua4.win/busybox-w32/atom?h=cron_changes'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/'/>
<updated>2025-06-09T12:23:49+00:00</updated>
<entry>
<title>Use Windows library for cryptographic checksums</title>
<updated>2025-06-09T12:23:49+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2025-06-09T12:23:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=596c443112d09506c3bf13ac98046a84b912e56c'/>
<id>urn:sha1:596c443112d09506c3bf13ac98046a84b912e56c</id>
<content type='text'>
Add a new feature to libbb, FEATURE_USE_CNG_API, which enables the
use of the Cryptography API: Next Generation library to calculate
checksums.  It is disabled by default except in the mingw64u default
config, as the API requires Windows 10+ to function.  Usage of this
API provides a size benefit and delegates hardware optimizations to
the operating system cryptography library.

Based on GitHub PR #498 by rfl890.

Saves 4064 bytes in the mingw64u case.
</content>
</entry>
<entry>
<title>win32: include our manifests in default configurations</title>
<updated>2023-09-15T08:44:12+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2023-09-15T08:41:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=54e6e2a16f2091d5dd1251bb3b4436555b1b0a03'/>
<id>urn:sha1:54e6e2a16f2091d5dd1251bb3b4436555b1b0a03</id>
<content type='text'>
The default configurations now include the provided standard or
UTF-8 manifest.

This works best if the build toolchain doesn't provide a default
manifest (which Fedora and w64devkit don't, by default).

If the toolchain does have a default manifest some bloat will
result.

(GitHub issue #366)
</content>
</entry>
<entry>
<title>win32: add FEATURE_UTF8_OUTPUT (enabled with unicode)</title>
<updated>2023-08-03T17:57:53+00:00</updated>
<author>
<name>Avi Halachmi (:avih)</name>
<email>avihpit@yahoo.com</email>
</author>
<published>2023-08-03T15:23:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=bf70275f786716546ec474caade0f16ec28da541'/>
<id>urn:sha1:bf70275f786716546ec474caade0f16ec28da541</id>
<content type='text'>
Previously, the unicode build required console (out) codepage of UTF8
in order for unicode output to be printed correctly - e.g. at the
shell command prompt or the output of `ls` for unicode file names.

This is inconvenient, because by default it's not UTF8, and so unless
the user invoked 'chcp 65001' - by default unicode output didn't work.

This feature (which is now enabled for the unicode build) makes it
print unicode output correctly regardless of the console CP, by
using a new stream-conversion funcion from UTF8 chars to wchar_t,
and writing those using WriteConsoleW.

If the console CP happens to be UTF8 - this conversion is disabled.

We could have instead changed the console CP to UTF8, but that's
a slippery slope, and some old program which expect the default CP
might get broken, so achieving the same result without touching
the console CP is hopefully better.
</content>
</entry>
<entry>
<title>win32: add script to create mingw unicode config</title>
<updated>2023-07-22T06:40:36+00:00</updated>
<author>
<name>Avi Halachmi (:avih)</name>
<email>avihpit@yahoo.com</email>
</author>
<published>2023-07-16T18:29:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=7aa64d90542cfc8f01f52ece38bf751c7b843875'/>
<id>urn:sha1:7aa64d90542cfc8f01f52ece38bf751c7b843875</id>
<content type='text'>
Run ./scripts/mk_mingw64u_defconfig to create (or update)
configs/mingw64u_defconfig from configs/mingw64_defconfig while
enabling UTF8 manifest, UTF8 input, and unicode editing.
</content>
</entry>
</feed>
