Add MinGW (Windows 10+) Target

[7d4d9e33]

I have implemented 64-bit Windows 10+ target support for Redlib via MinGW (x86_64-pc-windows-gnu).

To do this:

1. Add the target to Rust:

rustup target add x86_64-pc-windows-gnu

2. Install the cross-compilation dependencies (example is for Debian/Ubuntu):

sudo apt-get install --no-install-suggests --no-install-recommends -y \
  gcc-mingw-w64-x86-64 g++-mingw-w64-x86-64 nasm cmake

3. Run the following command inside the redlib repository root:

CARGO_TARGET_X86_64_PC_WINDOWS_GNU_LINKER=x86_64-w64-mingw32-gcc \
CC_x86_64_pc_windows_gnu=x86_64-w64-mingw32-gcc \
CXX_x86_64_pc_windows_gnu=x86_64-w64-mingw32-g++ \
BINDGEN_EXTRA_CLANG_ARGS="-I$(x86_64-w64-mingw32-gcc -print-file-name=include)" \
cargo build --release --target x86_64-pc-windows-gnu

Ubuntu Note: If you encounter header conflicts between Clang and MinGW headers, append -nobuiltininc to the BINDGEN_EXTRA_CLANG_ARGS environment variable:
BINDGEN_EXTRA_CLANG_ARGS="-I$(x86_64-w64-mingw32-gcc -print-file-name=include) -nobuiltininc"

Once the build finishes, the output executable redlib.exe will be located in target/x86_64-pc-windows-gnu/release/.

Testing & Downloads

• Status: Environment variables and core operations were tested on Windows and work smoothly.
• Prebuilt Binary: For testing without building locally, download redlib-release-x86_64-pc-windows-gnu.zip.

Suggestion: CI setup could be updated to publish compiled binaries in each push instead of putting it to release. For reference, ReSukiSU has an effective CI pipeline for publishing build artifacts directly on push without requiring a formal release tag.