Before binarycreator can do its magic, you need three critical ingredients:
: On macOS and Linux, ensure the binarycreator tool itself has execution permissions ( chmod +x ). binarycreator
| Tool | Strengths | Weaknesses | |------|-----------|-------------| | | Tiny output, very fast | Windows-only, no native online repos | | NSIS | Highly scriptable | Steep learning curve, no built-in delta updates | | CPack (CMake) | Native integration with CMake | Less control over UI/UX | | binarycreator (Qt IFW) | Cross-platform, component-based updates, professional UI | Requires Qt runtime, larger stub size (~3 MB) | Before binarycreator can do its magic, you need
: Points to the directory containing your package definitions. Before binarycreator can do its magic
Here is how you invoke binarycreator to glue it all together: