winlamb
min-sized-rust
Our great sponsors
| winlamb | min-sized-rust | |
|---|---|---|
| 14 | 101 | |
| 318 | 7,410 | |
| - | - | |
| 4.6 | 6.2 | |
| 9 months ago | about 1 month ago | |
| C++ | Rust | |
| 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.
winlamb
- Cross-platform file mapping
- What middleware would you like
-
dear imgui as a Qt Widgets Alternative?
The first thing that came into my mind was: why not simply go fully native, with the aid of something like WinLamb? Often you can roll your own custom controls quicker than a cross-platform library.
-
win32 api GUI share data
With WinLamb it's trivial: just create a field in the class.
-
I am currently working on win32 gui project on codeblocks , to give my already built s/w a form of frame based gui application software but I either keep on makings mistakes or my code is less effecient. Can anyone redirect me to some resource that can help me .
However, if you still want to go Win32, this library is a thin wrapper which may save you a lot of time (and sanity). However, it's C++, not C.
-
Rust takes a major step forward as Linux's second official language
I write C++ and raw Win32 for more than 20 years. I'm the author of this, and I'm rewriting my personal stuff in Rust just for fun.
-
Is WinUI the most modern GUI library for C++ desktop applications on Windows?
I wrote a very thin C++11 wrapper for Win32 a few years ago, in case you're interested: WinLamb. It won't do everything, it just covers window creation and messaging, and leaves room to plug any other Win32 stuff on top of it.
-
Windows System Programming
Take a look at WinLamb source if you want to see how to build a native GUI.
-
Your first Rust project: How bad was the first working version in the context of what you know about the language today? If given the ability to change those early days of learning Rust, what changes would you make?
Given my C++ Win32 background, the very first thing I tried was to write a native Win32 GUI app in Rust. It later became the WinSafe crate, which is strikingly similar to WinLamb C++ lib. The Rust experience was awesome. The correctness of the type system was something I really appreciated, things C++ cannot give you.
-
Which GUI platform and why?
I write native Windows stuff sometimes, and I use Windigo, which I wrote based on my WinLamb C++ lib. It's a GUI system over raw Win32, so this has the disadvantage that you'll have to learn some Win32... but it has the advantage that you have the unleashed power of Win32 at your fingertips.
min-sized-rust
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
This is a good guide on building small Rust binaries: https://github.com/johnthagen/min-sized-rust
This talks about going to extreme lengths on making the smallest Rust binary possible, 400 bytes when it was written, https://darkcoding.net/software/a-very-small-rust-binary-ind...
The thing is, you lose a lot of nice features when you do this, like panic unwinding, debug symbols, stdlib… for kernel and some embedded development it’s definitely important, but for most use cases, does it matter?
-
Rust wont save us, but its ideas will
Oh it was 137, haha. I will link you to this older comment of mine: https://news.ycombinator.com/item?id=29408906
-
Making Rust binaries smaller by default
Are you sure? If so then this is awesome news, but I'm a bit confused; the commit in that min-sized-rust repo adding `build-std` to the README was merged in August 2021: https://github.com/johnthagen/min-sized-rust/pull/30
Are you saying that at that point the feature still hadn't "landed in Rust nightly" until recently? If so then what's the difference between a feature just being available in Rust nightly, vs having "landed"?
-
Was Rust Worth It?
Rust binaries are by default nowhere close to 500MB. If they are not small enough for you, you can try https://github.com/johnthagen/min-sized-rust. By avoiding the formatting machinery and using `panic_immediate_abort` you can get about the size of C binaries.
-
Compiling Rust binaries for Windows 98 SE and more: a journey
A useful reference: https://github.com/johnthagen/min-sized-rust
- How to minimize Rust binary size
- Error on flashing embedded code to stm32f103
-
Tiny Binaries (2021)
That must be without stripping. Also there are ways to reduce binary size. See e.g. [min-sized-rust](https://github.com/johnthagen/min-sized-rust). I've gotten stripped binaries of small cli utils less than 400KiB without doing anything special, less than 150 KiB by customizing profile settings and compressing with upx, and less than 30 KiB by replacing the std with the libc as the link shows. Haven't tried with fltk though...
-
Shared libraries
This is not quite what you're asking, but it does also address the underlying concern: https://github.com/johnthagen/min-sized-rust
What are some alternatives?
winsafe - Windows API and GUI in safe, idiomatic Rust.
smartstring - Compact inlined strings for Rust.
giu - Cross platform rapid GUI framework for golang based on Dear ImGui.
Cargo - The Rust package manager
winsafe-examples - Examples of native Windows applications written in Rust with WinSafe.
rustc_codegen_gcc - libgccjit AOT codegen for rustc
mrustc - Alternative rust compiler (re-implementation)
c2rust - Migrate C code to Rust
screen-melter - Creates melting like effect on users screen.
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
kvcrutch - Easily and Safely work with TLS Certs in Azure Key Vault
embedded-graphics - A no_std graphics library for embedded applications