| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
It seems windres in llvm doesn't understand MANIFEST resources.
Use the numeric value 24 instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Hey, look! It's 2021 already.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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'.
|
|
Since more than just icon resources are now provided give various
files more appropriate names.
|