Binarycreator — __top__

binarycreator -c config/config.xml -p packages -e myapp.core,myapp.docs MyAppOnlineInstaller.exe And for an (single big file with everything):

<!-- In config.xml --> <Installer> <RepositorySettings> <Repository url="https://updates.myapp.com/repo" /> </RepositorySettings> </Installer> When things go wrong (missing dependencies, broken scripts), run: binarycreator

Download the Qt IFW from the official Qt site (open source under GPL/LGPL) and run binarycreator --help . Your first installer is only three files away. Have you used binarycreator in production? Or struggled with a peculiar bug? Let me know in the comments below. binarycreator -c config/config

binarycreator --verbose -c config.xml -p packages output.exe It will dump every file it packs and every XML node it reads. | Problem | Likely Cause | |---------|---------------| | "Could not find package 'A'" | You forgot -p or the folder name doesn't match <Name> in package.xml | | Installer crashes on launch | The stub architecture mismatches the target (e.g., using Windows stub on macOS) | | Files missing after install | Forgot to put them in data/ or used symlinks (not followed) | | Script errors are silent | Enable --verbose during build and run installer with --verbose too | Alternatives to binarycreator If you are evaluating packaging tools, here is how binarycreator compares: Or struggled with a peculiar bug

binarycreator