busybox-w32/win32/resources/resources.rc, branch long_pathsA mirror of https://github.com/rmyorston/busybox-w32.git
https://git.lua4.win/busybox-w32/atom?h=long_paths2026-02-27T14:27:40+00:00win32: add (some) long path support2026-02-27T14:27:40+00:00Ron Yorstonrmy@pobox.com2026-02-27T13:57:40+00:00urn:sha1:ed525e2db10081f095d2fccc1b02830654470401
Use the longPathAware manifest entry to handle path lengths above
260. This requires the LongPathsEnabled registry key to be set
at run-time.
Modify (some) WIN32 API calls to use the wide-character variant.
These features are controlled by the build-time configuration
option FEATURE_LONG_PATHS, which is not enabled by default.
win32: update UTF-8 manifest2025-12-01T15:45:18+00:00Ron Yorstonrmy@pobox.com2025-12-01T15:45:18+00:00urn:sha1:52917c47e21478c2507d1ff7b0d83a699650b310
It seems that the UTF-8 manifest can be adjusted to avoid binaries
failing to run on Windows XP.
Make the necessary adjustment. This doesn't affect the legacy
builds, only those with Unicode enabled. Nor does it change the
code which prevents Unicode builds from running on platforms
that don't support the manifest.
See this GitHub issue for details:
https://github.com/skeeto/w64devkit/issues/315
win32: allow the use of PNG format icons2025-11-06T13:00:49+00:00Ron Yorstonrmy@pobox.com2025-11-06T13:00:49+00:00urn:sha1:3227f3bdeb7c33cfcb0d3d8ceed19a0ca9560e13
Convert the icons to PNG format (by simply exporting them from
GIMP and selecting the 'Compressed (PNG)' chackbox). Allow these
to be selected instead of ICO format at build time.
Use the PNG icons by default in the Unicode and aarch64 builds.
Saves 26KB in those cases.
(GitHub PR #540)
manifest: integrate into resources.rc, reduce binary size2025-11-06T10:50:37+00:00Viktor Szakatscommit@vsz.me2025-11-04T19:48:00+00:00urn:sha1:e7f23eb454b1ad6f013b69f93276a39c3da3bb4d
It also makes the version number within the manifest use the version
macros, replacing the hard-coded "6.0.0.0".
Unicode: 32668 -> 32188 (-480 bytes)
non-Unicode: 32412 -> 31956 (-456 bytes)
with icons included.
win32: hardcode numeric value of MANIFEST resource2024-01-23T12:55:03+00:00Ron Yorstonrmy@pobox.com2024-01-23T12:55:03+00:00urn:sha1:25e7fad9b5d6c4101760f9162fe1664c7f6ec363
It seems windres in llvm doesn't understand MANIFEST resources.
Use the numeric value 24 instead.
win32: improved support for manifests2023-09-14T15:07:50+00:00Ron Yorstonrmy@pobox.com2023-09-14T15:07:50+00:00urn:sha1:b822f427d894f46a85d3ce5ff785d3ea2cef972f
The UTF-8 manifest has been updated to include features from the
standard application manifest.
Include a copy of the standard application manifest for toolchains
that don't provide one.
(GitHub issue #366)
win32: include UTF-8 manifest2023-06-20T14:33:10+00:00Ron Yorstonrmy@pobox.com2023-06-20T14:33:10+00:00urn:sha1:830e2cfae63a20beddd81d9db00dc906265a0e34
Include a manifest in the binary to set the process code page to
UTF-8. This only has an effect from Windows 10 version 1903.
Controlled by the FEATURE_UTF8_MANIFEST config setting, disabled
by default.
win32: revise creation of resources2022-10-25T07:28:42+00:00Ron Yorstonrmy@pobox.com2022-10-25T07:28:42+00:00urn:sha1:62654c448c4f0dfc0fdb72220adc33af0be7cb65
As reported in https://github.com/skeeto/w64devkit/issues/35
there's a problem creating Windows resources using the native
version of `windres`.
Avoid passing arguments to `windres` that it can't handle by
stringizing the version string locally in resource.rc.
(GitHub issue #239)
Increment date in resources2022-02-14T08:09:50+00:00Ron Yorstonrmy@pobox.com2022-02-14T08:09:50+00:00urn:sha1:5ce146536f50341efd2496370af804bb348fa66eUpdate copyright message2021-01-13T11:56:20+00:00Ron Yorstonrmy@pobox.com2021-01-13T11:56:20+00:00urn:sha1:9aa5a829070392c2ac6494d0c4e674c0c2bc7dab
Hey, look! It's 2021 already.