busybox-w32/win32/resources/Kbuild.src, branch long_pathsA mirror of https://github.com/rmyorston/busybox-w32.git
https://git.lua4.win/busybox-w32/atom?h=long_paths2025-11-06T13:00:49+00:00win32: 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.
build system: more clang/llvm tweaks2024-01-18T08:01:49+00:00Ron Yorstonrmy@pobox.com2024-01-18T08:01:49+00:00urn:sha1:992387539f26de1aeb2cdca62d85fddbde27b798
Linkers associated with clang/llvm may not support the -r option.
This is used to create built-in.o object files. It turns out that
all such files in busybox-w32 are either empty or only contain one
object file. The first case is already supported and the second
can be handled by simply copying the object file to built-in.o.
The linker is therefore never invoked with the -r option.
One adjustment is required: the workaround adopted for GitHub
issue #200 linked the dummy C file with the resource object file.
This is no longer done so only one object file is used. Since it
was the linking that broke the resource file, copying it is an
equally effective fix for the issue.
Some old linkers don't support the --warn-common option. The lack
of this option was being detected but it was still sometimes used.
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)
win32: workaround for '0-bit reloc' on MSYS22021-02-21T09:51:13+00:00Ron Yorstonrmy@pobox.com2021-02-21T07:46:21+00:00urn:sha1:ddc4704db62865b5e2c0621f17cc2dc6909c1208
There seems to be a bug in the Windows/MSYS2/mingw-w64 toolchain
which results in the generated win32/resources/built-in.o lacking
relocation data.
Forcing an actual C program to be linked along with the resources
appears to be an effective workaround.
When the toolchain bug is resolved this commit can be reverted.
See GitHub issue #200.
win32: use manifest provided by MinGW-w642019-02-21T11:53:55+00:00Ron Yorstonrmy@pobox.com2019-02-21T11:29:12+00:00urn:sha1:20dfd84edd1b45b78a284bf75ef711726a4e8415
The manifest included here wasn't effective in telling Windows
about version compatibility. Use the default manifest provided
by MinGW-w64 instead.
On Fedora this requires installing the mingw32-windows-default-manifest
and/or mingw64-windows-default-manifest packages.
Allow build objects to go to a separate directory2018-11-21T13:26:03+00:00Ron Yorstonrmy@pobox.com2018-11-21T13:26:03+00:00urn:sha1:1ae73ffecfa074e345c75dc761931a767c9c9318
Fix the build system so the KBUILD_OUTPUT environment variable can be
used as intended: to specify that object files are placed in a separate
directory from the source.
Also ensure that busybox-w32.manifest is deleted by 'make mrproper'.
win32: rename resource files2018-07-24T15:43:10+00:00Ron Yorstonrmy@pobox.com2018-07-24T15:43:10+00:00urn:sha1:958ba292aab941d81b4d89dedc92ba78ace6b1ad
Since more than just icon resources are now provided give various
files more appropriate names.