skeeto /w64devkit

Portable C and C++ Development Kit for x64 (and x86) Windows

★ 5,010⑂ 411👁 61⑃ 88● 287▤ 42
CUnlicenseCreated 2020-05-10
下载:2.11.02.11.0 ↓2.11.02026-10-29
+3
日增长
5,010
stars
411
forks
61
watchers
88
prs
287
issues
42
releases

README

Portable C, C++, and Fortran Development Kit for x64 and x86 Windows

[w64devkit][] is a Dockerfile that builds from source a small, portable
development suite for creating C and C++ applications on and for x86 and
x64 Windows. See "Releases" for pre-built, ready-to-use kits.

Included tools:

 [Mingw-w64 GCC][w64] : compilers, linker, assembler
 [GDB][gdb] : debugger
 [GNU Make][make] : standard build tool
 [CMake][cmake] with [Ninja][ninja] and [a debugger][dcmake] : build system
 [unabashed][ub] : a bash for Windows, as sh and bash
 [busybox-w32][bb] : standard unix utilities
 [Vim][vim] : powerful text editor
 [quicktags][ctags] : source navigation (ctags)
 [Ccache][ccache] : compiler cache
 [NSIS][nsis] : Windows installer compiler (makensis)
 [aas-sign][aas-sign] : Authenticode signing via Azure Trusted Signing

It is an MSVCRT toolchain with pthreads, C11 and C++11 threads, and
OpenMP. The 64-bit release is multilib, targeting both x64 and x86. All
runtime components are all static.

Docker is not required to use the development kit. It's merely a
reliable, clean environment for building the kit itself.

 Build

Build the image, then run it to produce a self-extracting 7z archive:

    docker build -t w64devkit .
    docker run --rm w64devkit w64devkit-x64.exe

The default x64 variant is a combined x64/x86 multilib toolchain. Select a
standalone x86 toolchain with a build argument:

    docker build --build-arg VARIANT=x86 -t w64devkit .

multibuild.sh -a builds both variants.

On Windows, wslc from WSL containers works as a drop-in replacement for
docker in these commands. For multibuild.sh, set DOCKER=wslc.

This takes about 15 minutes on modern systems. You will need an internet
connection during the first few minutes of the build. Note: Do not use
PowerShell because it lacks file redirection.

 Build via GitHub Actions

GitHub can build w64devkit for you. Fork the repository, enable GitHub
Actions, push your commits, then download the freshly-built artifacts.

 Usage

The self-extracting 7z archive contains tools in a typical unix-like
configuration. Extract wherever is convenient. Inside is w64devkit.exe,
which launches a console window with the environment configured and ready
to go. It is the easiest way to enter the development environment, and
requires no system changes. It also sets two extra environment variables:
W64DEVKIT_HOME to the installation root and W64DEVKIT to the version.

Alternatively, add the w64devkit/bin directory to your path. For
example, inside a cmd.exe console or batch script:

    set PATH=c:\path\to\w64devkit\bin;%PATH%

Then to start an interactive unix shell:

    sh -l

 Main features

 No installation required. Run it anywhere as any user. Simply delete
  when no longer needed.

 Fully offline. No internet access is ever required or attempted.

 A focus on static linking all runtime components.

 Trivial to build from source, meaning it's easy to tweak and adjust any
  part of the kit for your own requ

Top issues

Discussions

Latest release

2.11.0 v2.11.0 2026-10-29
Manual pages for every program in the kit
   BusyBox man enabled, with a new nroff formatter in place of groff
   less -R passes colors and text attributes through
 x86 code defaults to 64-bit time_t and SSE2 floating point math
   C11 threads support both time_t ABIs
   libstdc++ system_clock no longer overflows in 2038, on x64 too
 New command: zipinfo (tugz)
 Large address aware x86 binutils, GCC, GDB, zstd, and tugz
 zstd decompresses windows up to 2GiB by default on x64
 Smaller NSIS installers, and NSISdl downloads work [423]
 Changes to busybox-w32 behaviors
   A bare drive such as C: m

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON