You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested with a relatively small one of my shell script, which is only ~ 1.3k in size (1323).
The generated file is nearly 70k (68384). In comparison, the shc generated file is about 20k (21120).
This somewhat surprises me, as the shc generated file is a standalone one that can be executed by itself, yet the ssc generated one still needs an interpreter.
I know people would say that disk space is nothing, but I'm just wondering why there's such huge differences between the two. thanks.
UPDATE:
Tried a normal-sized of my script, close to 30k (29906), and the size different is less than doubled (58704 vs 97064), just FTA.
The text was updated successfully, but these errors were encountered:
As far as I know, shc needs an interpreter at runtime too, whileas ssc can generate actually standalone binary with -e/-E flags.
The output binary size = main program size + script payload size. The size of main program is always the same. ssc is written in C++ and links against STL, it's generated main program size is expected to be larger.
Hi,
I tested with a relatively small one of my shell script, which is only ~ 1.3k in size (1323).
The generated file is nearly 70k (68384). In comparison, the
shc
generated file is about 20k (21120).This somewhat surprises me, as the
shc
generated file is a standalone one that can be executed by itself, yet the ssc generated one still needs an interpreter.I know people would say that disk space is nothing, but I'm just wondering why there's such huge differences between the two. thanks.
UPDATE:
Tried a normal-sized of my script, close to 30k (29906), and the size different is less than doubled (58704 vs 97064), just FTA.
The text was updated successfully, but these errors were encountered: