Rust source code for WinRAR keygen

[WhoCares]

hello,

In order to keep the exe file small(no more than 500KB), my package uses "native-windows-gui" crate which supports Windows only, but with Windows built-in editing hotkeys and context menus.
I have another keygen template which produces a 10MB exe with Rust GPUI framework.
Your keygen produces a 4.x MB exe and looks beautiful.

And I put it in my private repo

Thanks for your work!

Originally Posted by blue_devil

@WhoCares, I have added egui to your project. Now anyone can compile it for any platform.

What a world:

I have added egui with AI but I have manually fix alignment of widgets.

@WhoCares maybe you should add this to a repo?

Source Updated for cross compilation
https://pixeldrain.com/u/JuHHfMTy

Windows x86_64
https://pixeldrain.com/u/Nv7odq85

Windows arm64
https://pixeldrain.com/u/z4dbpmET

Linux x86_64
https://pixeldrain.com/u/itn3k2be

Linux arm64
https://pixeldrain.com/u/TBXWPGQD

[blue_devil]

I am fully aware of that ph*t **s binaries. With vibe coding, we can make separate native guis. But who has that time.

I prefer GTK on Linux, but I want to give a try on egui. Even though code looks simpler, end result is huge.

At least they are working!

[WhoCares]

If we want a small binary size and only need a UI with basic controls, libui-rs is also a viable option for cross-platform. It binds to the UI frameworks provided by the operating system, so the resulting size is relatively small.

wxWidgets is another cross-platform option, it also binds to native UI framework, but the compilation process is somewhat more complicated.

Originally Posted by blue_devil

I am fully aware of that ph*t **s binaries. With vibe coding, we can make separate native guis. But who has that time.

I prefer GTK on Linux, but I want to give a try on egui. Even though code looks simpler, end result is huge.

At least they are working!

[Jupiter]

Originally Posted by WhoCares

Your keygen produces a 4.x MB exe …

Don't forget to create a release build.
By default a debug build is created.

cargo build --release

Release build is approx. 3-4 times smaller than debug one.

[WhoCares]

Thanks Jupiter for the reminder.

The sizes are for release builds. They are relatively large because the rendering engine is bundled into the binaries.

With native UI frameworks, the rendering engine is provided by the OS (system DLLs / drivers), so the app only contains a thin abstraction layer over the native APIs.