Nice job, but UPX is not good.

[DeafMan1983]

Hello everyone,

Nice idea for Aot version. But I don't need upx. But I find funny because single executable requires 2 libraries as *.a for Linux/macOS and *.lib for Windows via directinvoke.

If you use musl-libc Linux like Void-Linux or Alpine then you just add then clang error message and copy whole output of error message and replace "clang" with musl-g++ -static and find -lrt and add -lSkiaSharp -lHarfBuzzSh then strip -S AvaloniaAOT then it looks small executable ca 10 mb under Linux.

[Sewer56]

Every once in a while I come back to this repo to mess around.

Anyway, I would recommend against using UPX too. Unless you're making a tool that's very, very rarely used so you'd rather save disk space.

The reason being that it hurts startup times. Aside from the obvious decompression, there's also another contributor.
It's actually in fact I/O.

For UPX to work, it must read and decompress the whole binary at once in memory.
Meanwhile a regular, uncompressed binary can use Demand Paging to dynamically load the code on page faults only as it's needed.

In practice the difference in boot times is not likely to be very high, but it exists.

[lixinyang123]

Every once in a while I come back to this repo to mess around.

Anyway, I would recommend against using UPX too. Unless you're making a tool that's very, very rarely used so you'd rather save disk space.

The reason being that it hurts startup times. Aside from the obvious decompression, there's also another contributor. It's actually in fact I/O.

For UPX to work, it must read and decompress the whole binary at once in memory. Meanwhile a regular, uncompressed binary can use to dynamically load the code on page faults only as it's needed.Demand Paging

In practice the difference in boot times is not likely to be very high, but it exists.

By default, upx will be disabled 8b4cc5c