Unlike in C/ C++ world where packaging creates an exe, Smalltalk has no packaged content for its program.
Similar to Smalltalk is Java that packages its code / compiled bytecode as a jar . This jar can be "executable" but per se what it does is to start a JVM with loading of all the necessary dependent jars and runs the code of the "Program/ Application" jar.
Smalltalk is a little different that we package the code for an application with all of its dependencies etc in the "image" file that contains the compiled bytecode of the code written.
You just invoke the image with the pharo.exe vm engine viz:
************************************��
From a coder/ programmer perspective, it is quite a shift to understand that you do not have a standalone 5 line code that creates a "Helloworld"
You write inside the IDE, the required class and method with its statement. The application packaging and delivery is a little more involved. So once you cross a barrier of understanding how to write code inside the IDE and see it running within the IDE with no visible "Compile - Run" cycle.