sokol-samples
corrosion
sokol-samples | corrosion | |
---|---|---|
8 | 5 | |
550 | 948 | |
- | 3.2% | |
9.0 | 8.2 | |
6 days ago | 8 days ago | |
C | CMake | |
MIT License | MIT License |
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.
sokol-samples
-
Zig cookbook: collection of simple Zig programs that demonstrate good practices
Zig currently doesn't allow chained designators and also doesn't allow to partially initialize arrays and fill up the rest of the array with default values.
E.g. the closest Zig equivalent to this C99 code:
https://github.com/floooh/sokol-samples/blob/b3bc55c4411fa03...
...is this:
https://github.com/floooh/sokol-zig/blob/a4b3c287fadd153a504...
...note how part of the initialization had to be moved out into "code".
There's a ticket about this here, but it's currently not high-priority:
https://github.com/ziglang/zig/issues/6068
-
Building a Web Game in C with Raylib
This is a simple Pong-like I've written in Raylib compiled to WASM - https://wasm-stuff.netlify.app/pong
Source code is here: https://github.com/rrampage/skitter/tree/master/pong-raylib
It is fairly straightforward to get Raylib running in the browser. I used @flohofwoe's HTML shell file ( https://github.com/floooh/sokol-samples/blob/master/webpage/... ).
-
Learn WebGPU
PS: also if shader functions could be directly defined "inline" in regular CPU code (and behind a special function pointer type), there would be no need for string literal shenanigans like this:
https://github.com/floooh/sokol-samples/blob/3f10c1a0620cec9...
(and shader compilation would happen during the regular build and would also generate regular compiler errors - with current toolchains that's only possible with a lot of build system magic)
-
Next C compiler is a D compiler: Introducing DMD's ImportC
I think something along those lines (rarely used...) was also given by the C++ Committee as justification why so much of the C99 designated init feature set was left out of C++20. But in reality, all C99 designated-init 'sub-features' complement each other nicely once you start using them. It's a great way for building 'data-driven' APIs.
For instance check out this call to create a 3D-API pipeline-state-object in C99:
https://github.com/floooh/sokol-samples/blob/ad9047e228a8441...
- C in Web Dev
-
Learning that you can use unions in C for grouping things into namespaces
I'm using anonymous nested structs extensively for grouping struct items, but I consider the extra field name a feature, not something that should be hidden:
https://github.com/floooh/sokol-samples/blob/bfb30ea00b5948f...
(also note the 'inplace initialization' which follows the state struct definition using C99's designated initialization)
-
Nuklear: A cross-platform GUI library in C
It's an STB-style single-file library, which means the implementation is in a separate ifdef-block from the interface declarations, this allows to compile the implemenentation in a separate source file (which can be a C file), and be used in different source files (which can be C++ files).
For example (using stb_image.h):
https://github.com/floooh/sokol-samples/blob/master/libs/stb...
-
Making Win32 APIs More Accessible to More Languages
C99 has made all that a lot easier, you can setup, initialize a struct and call the function taking a pointer to that struct all in one call:
https://github.com/floooh/sokol-samples/blob/89f5825ab5d3690...
The Win32 window system functions and D3D11 are actually very convenient to work with in C99, better than C++ actually.
corrosion
-
Learn WebGPU
With reference to the section on how difficult it is to build wpgu-native and how you basically have to use a precompiled binary, there appears to be an easier way to integrate a Cargo library into a CMake project: https://github.com/corrosion-rs/corrosion
-
Lust 🦞
Already taken as a name https://github.com/corrosion-rs/corrosion
-
Advice on build system approach choice for a Rust + Fortran project?
Corrosion can help with option 1, cmake with option 2. You are on your own with option 3, so I would stay away from that.
-
Having to work with C++ made me appreciate how good Rust is.
Or you can just use one of the many solutions others have already come up with, like this cmake project I found with a minute of googling: https://github.com/corrosion-rs/corrosion
-
[Problem] Adding rust in a CMake/Cpp project using Cxx and Corrosion linker iterator debug level issue
Tools that seems reasonable to help this integration is Corrosion and Cxx.
What are some alternatives?
sokol-zig - Zig bindings for the sokol headers (https://github.com/floooh/sokol)
cmake-d - cmake for D2
NanoGUI - Minimalistic GUI library for OpenGL
cxx - Safe interop between Rust and C++
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
rusty_cmake - Rust cmake integration template with corrosion and cxx
libev - Full-featured high-performance event loop loosely modelled after libevent
conan - Conan - The open-source C and C++ package manager
nuklear - A single-header ANSI C immediate mode cross-platform GUI library
vcpkg_template - Simple cmkr template to get you started with vcpkg right away.
ArrayFire - ArrayFire: a general purpose GPU library.
bake - Bake, A build system for building, testing and running C & C++ projects