https://www.solosoft.dev/tags/packaging/Recent content in Packaging on SoloSoftHugoen-usFri, 01 May 2026 00:00:00 +0000https://www.solosoft.dev/post/electron-builder-2026/Fri, 01 May 2026 00:00:00 +0000https://www.solosoft.dev/post/electron-builder-2026/<p>Shipping a desktop application to users is only half the battle &ndash; getting that application packaged, signed, and distributed across three operating systems is where the real work begins. <strong>Electron Builder</strong> (electron-userland/electron-builder) is the most widely adopted tool for solving exactly this problem, providing an all-in-one solution for packaging Electron apps for macOS, Windows, and Linux.</p> <p>Created by the Electron ecosystem maintainers, Electron Builder has become the de facto standard for Electron application distribution. It is used by thousands of production applications ranging from small utilities to enterprise SaaS tools, handling everything from installer creation to code signing to automatic updates.</p>https://www.solosoft.dev/post/pyinstaller-packaging-2026/Fri, 01 May 2026 00:00:00 +0000https://www.solosoft.dev/post/pyinstaller-packaging-2026/<p>One of Python&rsquo;s biggest challenges is distribution. Users need to install Python, manage virtual environments, and resolve dependencies before they can run your application. PyInstaller solves this by freezing Python applications into standalone executables that work on systems without Python installed.</p> <p>PyInstaller analyzes your Python script, discovers all imported modules and data files, and bundles them together with a minimal Python interpreter into a single executable file or directory. The result is a distributable package that users can run by double-clicking, just like any native application.</p> <h2 id="key-features">Key Features</h2> <table> <thead> <tr> <th>Feature</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>Cross-platform</td> <td>Creates executables for Windows, macOS, and Linux</td> </tr> <tr> <td>One-file mode</td> <td>Bundle everything into a single executable</td> </tr> <tr> <td>Automatic dependency detection</td> <td>Finds and includes all imported modules</td> </tr> <tr> <td>Hidden imports support</td> <td>Manual specification for dynamic imports</td> </tr> <tr> <td>Data file bundling</td> <td>Include images, configs, and assets</td> </tr> </tbody> </table> <h2 id="build-process">Build Process</h2> <figure class="mermaid-wrapper not-prose" role="img" aria-label="Mermaid diagram"> <div class="mermaid-container"> <pre class="mermaid">flowchart LR A[Python Script] --&gt; B[PyInstaller Analysis] B --&gt; C[Dependency Discovery] C --&gt; D{Import Found} D --&gt;|Standard Lib| E[Bundled] D --&gt;|Third Party| E D --&gt;|Data Files| E E --&gt; F[Build Artifacts] F --&gt; G{Output Mode} G --&gt;|One File| H[single EXE/APP] G --&gt;|One Directory| I[Directory with all files] G --&gt;|Custom| J[Spec file controls]</pre> <script type="application/mermaid">flowchart LR A[Python Script] --> B[PyInstaller Analysis] B --> C[Dependency Discovery] C --> D{Import Found} D -->|Standard Lib| E[Bundled] D -->|Third Party| E D -->|Data Files| E E --> F[Build Artifacts] F --> G{Output Mode} G -->|One File| H[single EXE/APP] G -->|One Directory| I[Directory with all files] G -->|Custom| J[Spec file controls]</script> </div> </figure><p>PyInstaller first analyzes the script to understand its dependency tree, then bundles everything together. The spec file gives advanced users fine-grained control over every aspect of the build.</p>