busybox-w32
w64devkit
busybox-w32 | w64devkit | |
---|---|---|
16 | 72 | |
640 | 2,375 | |
- | - | |
9.2 | 7.6 | |
6 days ago | 12 days ago | |
C | C | |
GNU General Public License v3.0 or later | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
busybox-w32
- The Awk Programming Language, Second Edition
-
POSIX sh is a better interpreter than python
Even in environments such as win32, we have https://frippery.org/busybox/ that is just fucking awesome. Staying the size below an 1mb while being extremely fast. Unlike the shitty python package which has 40mb archive size and leave breadcrumbs for me to cleanup all over my filesystem.
-
The amount of times I have accidentally done this...
Win32 port is here: https://frippery.org/busybox/
-
God's developer console
Look into busybox for windows https://frippery.org/busybox/. Pretty bad ass even with it’s downsides of missing applets and such
-
Does vim suck on windows?
Vim by itself means no supporting unix environment. It's useful to call out to powerful external tools not present by default on Windows. I fill that gap with busybox-w32. It's not a big deal once solved.
-
looking for a graphics library
Sure, it's not necessary, but a few simple, nice tools (<600kiB for an entire suite of extended unix utilities) makes thing a whole lot simpler on a platform devoid of nice tools.
-
Compress lots of files into lots of individual files?
To operate on many files you'll need better tools than what Windows gives you. One option is busybox-w32 (important caveat: doesn't support unicode paths), which will get you some basic command line tools. For example, to gzip compress every file under the current directory, including subdirectories (leaving the originals behind with -k):
-
Windows verison of cal
busybox-w32 includes a cal applet. If that's all you care about, you can just rename busybox.exe to cal.exe.
-
What's in your tool belt?
busybox-w32: standard unix utilities for Windows. It's a BusyBox port.
-
Makefile example project for Windows with source, include, libs and build folders. Also with a detailed explanation!
IHMO, even better is to just use POSIX sh in your Makefile and simply make it a build requirement. It's easy to obtain a reasonable sh even on Windows (Cygwin, MSYS2, busybox-w32), and to further support exactly this I include sh alongside make in my development kit distribution. This uniformity lets me hit all operating systems with the same Makefile. I use EXE from the environment to determine the binary file extension, if any.
w64devkit
-
Mingw VS Code
Try w64devkit https://github.com/skeeto/w64devkit
- Portable C and C++ Development Kit for x64 (and x86) Windows
-
Windows XP dedicated image viewer?
Click "View raw" to download. The executable is just ~3kB. If you'd like to try building it yourself, I distribute a Windows XP-friendly, no-installation-required C and C++ toolchain, w64devkit. The 32-bit toolchains are labeled "i686" (on the right under "Releases"). The build command (cc ...) is at the top of the source file.
-
Can you help me finish this vDSO Loader + mini-Elf64 Parser?
I bundle my preferred tools together in a standalone compiler toolkit for Windows: w64devkit. Except Git and documentation (see the links in the README), that's essentially everything I need to be productive.
- Assume I'm an idiot - oogabooga LLaMa.cpp??!
-
Build a GCC 13 compiler from source for Windows 10/11
I have a Dockerfile here that goes through all the steps bootstrapping a Mingw-w64 toolchain from source: https://github.com/skeeto/w64devkit
-
Why is Swift so slow (timeout) in compiling this code?
FWIW, both GNU objcopy and GNU ld (including e.g. the XCOPY-deployable ones from w64devkit[1]) are perfectly capable[2] of turning binary data into MSVC-acceptable COFF files with start and end symbols, while Free Pascal, for example, straight up ships with a bin2obj tool; the MSVC toolset is the outlier here.
[1] https://github.com/skeeto/w64devkit
[2] https://www.devever.net/~hl/incbin
-
Generic Binary Tree Delete Function Error
Sounds like an high priority issue to solve first. I distribute a toolchain that doesn't require installation and includes a debugger: w64devkit (see "Releases"). You can pluck out the gdb.exe since it's statically linked and doesn't depend on anything else in the kit.
-
I've just finished to upgrade my raycaster game engine, adding multiplayer and more! Written from scratch in C and SDL2. GitHub in the comments :)
This particular case is a Windows program due to Winsock, and I happen to include all the above tools, except SDL2, a small Mingw-w64 distribution, w64devkit. So it doesn't take much!
-
WinLibs: Standalone build of GCC and MinGW-w64 for Windows
Similar project providing slightly fewer tools: https://github.com/skeeto/w64devkit
What are some alternatives?
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
notty - A new kind of terminal
mingw-builds - Scripts for building the 32 and 64-bit MinGW-W64 compilers for Windows
oursh - Your comrade through the perilous world of UNIX.
cmake-init - The missing CMake project initializer
csvinfo - A small util to show max column lengths for a passed CSV file.
xschem - A schematic editor for VLSI/Asic/Analog custom designs, netlist backends for VHDL, Spice and Verilog. The tool is focused on hierarchy and parametric designs, to maximize circuit reuse.
csvquote - Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines
mingw-builds-binaries - MinGW-W64 compiler binaries
awk - Random AWK code
SCL_String - Public domain, header-only file to simplify the C programmer's life in their interaction with strings