cargo-cabal VS upx

just saw this : https://github.com/yvan-sraka/cabal-pack

This will optimise the release binary to be as small as possible. Additionally with upx we can create really small docker image !

Then I compressed it with upx, cp small.exe smallUpx.exe && upx --brute smallUpx.exe, got a 10752 bytes executable, half the size, but still pretty large

You can try to a compress an output binary using https://itnext.io/shrinking-go-executable-9e9c17b47a41

By default, it produced a binary that is 24MB. I ran UPX on that and it generated a binary that is 6MB.

It depends on the platform, I think. E.g. DLL compression is supported on Windows. On Linux it seems like .so compression may be supported with some limitations - I see various tickets about it like https://github.com/upx/upx/issues/116 and https://github.com/upx/upx/issues/303 which are describing problems but also showing that it's possible.

I looked at the latest version of UPX, they began to use LZMA, if this is considered an LZMA decoder:

https://github.com/upx/upx/blob/devel/src/stub/src/arch/amd6...

Then it takes ~2500 bytes, mine is ~500 (static version). But the decompression speed for larger code should be higher, as I noticed.

UPX doesn't play nice with antivirus software if it's important for you to run on Windows (at least).

https://github.com/upx/upx/issues/337

sudo rm -rf Picocrypt-Builder && mkdir Picocrypt-Builder && cd Picocrypt-Builder && sudo apt-get install -y gcc make curl git tar wget xz-utils libx11-dev libxcursor-dev libxrandr-dev libxinerama-dev libxi-dev libgl1-mesa-dev libxxf86vm-dev libgtk-3-dev xdg-utils && sudo apt-get install -y libglx-dev || echo "Skipping libglx..." && sudo apt-get install -y xclip || sudo apt-get install xsel && wget https://golang.org/dl/go1.16.4.linux-amd64.tar.gz && sudo tar -C /usr/local -xzf go1.16.4.linux-amd64.tar.gz && export PATH=$PATH:/usr/local/go/bin && go get -u -v github.com/pkg/browser && go get -u -v github.com/zeebo/blake3 && go get -u -v golang.org/x/crypto/sha3 && go get -u -v golang.org/x/crypto/argon2 && go get -u -v github.com/AllenDang/giu && go get -u -v github.com/sqweek/dialog && go get -u -v golang.org/x/crypto/blake2b && go get -u -v golang.org/x/crypto/blake2s && go get -u -v github.com/atotto/clipboard && go get -u -v github.com/klauspost/reedsolomon && go get -u -v golang.org/x/crypto/chacha20poly1305 && go get -u -v github.com/HACKERALERT/Picocypher/monocypher && go mod init Picocrypt && wget https://raw.githubusercontent.com/HACKERALERT/Picocrypt/main/src/unstable/Picocrypt.go && go mod tidy && go build --ldflags="-s -w" Picocrypt.go && wget https://github.com/upx/upx/releases/download/v3.96/upx-3.96-amd64_linux.tar.xz && tar xf upx-3.96-amd64_linux.tar.xz && mv Picocrypt upx-3.96-amd64_linux && cd upx-3.96-amd64_linux && ./upx --best --lzma -9 -o Picocrypt-UPX Picocrypt && mv Picocrypt-UPX ../ && cd ../ && mv -v Picocrypt-UPX Picocrypt && mv Picocrypt ../ && cd ../ && sudo rm -rf Picocrypt-Builder && echo "Build complete! You can now run the file 'Picocrypt' in this directory with './Picocrypt' or by double clicking it in your file manager. Enjoy!"

I have been working on a game using Rust, SDL2 and Legion. I statically link SDL2, which mean that only the parts that I actually use gets included. Also i have been using the include_bytes to include my assets. This creates a single executable that is around 3mb (this is without compiler optimizing for size, it could go lower at the cost of runtime speed). Running (upx)https://github.com/upx/upx on it, it comes out to about 900kb.