Paquet Builder has powerful automation features that let you integrate it into your own build process, automatic distribution cycles, cron tasks... It also comes with a dedicated console compiler for build machines that don't require Windows user login.

Command-Line Options

Command-line options are both supported by Paquet Builder GUI and console compiler. You can create Self-Extracting archives silently, change the bitness of your package to x64, refresh all file lists (wildcard support), choose an existing 7z archive to convert and much more! For instance:

PBUILDER.EXE "C:\My Documents\pbtests\testdirect1.pbpx" /exetype:1 /c /q /s /filelistupt

Automation Directives

Use the powerful directive feature to create customized Self-Extracting packages with updated source files, modify version information and much more.

Paquet Builder introduces a specific file type called “directive file” which is text-based and contains instructions for Paquet Builder in order to create a package. They let you modify an existing project (transform) or create new projects from scratch.

Directives files are easy-to-use and work like the old Windows configuration (.ini extension) files. Below you can see an example:

Directive Explanation

 You can see all available parameters and learn more about directives here

Directives can be passed to Paquet Builder through command-line or the App menu. The console compiler also accepts directives.

Control operations with exit codes

Paquet Builder GUI and console compilers return proper exit codes when run through command-line and in automation process.

As you can see, Paquet Builder has a lot of tools designed for automation and batch build. That's why Paquet Builder is used for making hundreds of Self-Extracting packages automatically each day around the world.