cling
w64devkit
Our great sponsors
cling | w64devkit | |
---|---|---|
19 | 72 | |
3,342 | 2,375 | |
2.1% | - | |
8.4 | 7.6 | |
18 days ago | 11 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.
cling
- Cling 1.0 Released
- Cling: Interactive C++ Interpreter
-
Interactive GCC (igcc) is a read-eval-print loop (REPL) for C/C++
More recent activity, but based on clang: https://github.com/jupyter-xeus/xeus-cling https://github.com/root-project/cling
-
It's 2023, so of course I'm learning Common Lisp
> The repl driven workflow is amazing and the lisp images are rock solid and highly performant.
do people not realize that basically everything vm/interpreted language has a repl these days?
https://www.digitalocean.com/community/tutorials/java-repl-j...
https://github.com/waf/CSharpRepl
https://pub.dev/packages/interactive
not to mention ruby, python, php, lua
hell even c++ has a janky repl https://github.com/root-project/cling
-
Compiled and Interpreted Languages: Two Ways of Saying Tomato
Interactive C++ with Cling, https://blog.llvm.org/posts/2020-11-30-interactive-cpp-with-cling/, https://github.com/root-project/cling/, Relaxing the One Definition Rule in Interpreted C++, https://dl.acm.org/doi/10.1145/3377555.3377901 (PDF: https://www.researchgate.net/publication/339463915_Relaxing_the_one_definition_rule_in_interpreted_C)
-
dont want online ones
Want to see your mind blown? Check out cling, a (sort of) C and C++ interpreter (it's a REPL). Or the work in progress, live-developed clauf, a real C interpreter.
-
How to cling for execute code plugin?
Cling: https://github.com/root-project/cling
-
Do you use Wokwi to test/simulate/debug your ESP32/Arduino code, or are there other dev tools a better fit for the ESP32?
Wanting to just test pure c or c++ functions that are hardware independent -> (solution that I'm using): cling just in time compiler, gives a shell that you can just experiment with C++ expressions
-
gcc is pre installed but g++ not?
C++ source cannot contain a shebang, but you can make them executable with binfmt-misc, and have the kernel pass them to a C++ interpreter such as Cling upon execution. Pretty much the same as running Python or Bash scripts.
- Fête à bord d’un avion de Sunwing | L’organisateur s’explique sur l’origine de sa fortune
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?
termux-ndk - android-ndk for termux
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
xeus-cling - Jupyter kernel for the C++ programming language
mingw-builds - Scripts for building the 32 and 64-bit MinGW-W64 compilers for Windows
femtolisp - a lightweight, robust, scheme-like lisp implementation
cmake-init - The missing CMake project initializer
cppreference-doc - C++ standard library reference
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.
sectorlisp - Bootstrapping LISP in a Boot Sector
mingw-builds-binaries - MinGW-W64 compiler binaries
foth - Tutorial-style FORTH implementation written in golang
SCL_String - Public domain, header-only file to simplify the C programmer's life in their interaction with strings