Execute Directive Files

To execute a directive file without using the command line, click the and select the “Open Directive File” menu option.

Alternatively, you can execute directive files via the command line. When launching Paquet Builder manually (e.g., using the “Run” command in the Windows Start menu), you can pass parameters to specify the directive file.

Use the following command line to execute a directive file:

PBUILDER.EXE "c:\mywork\myproject\file.pbd"

This command opens Paquet Builder, reads the settings from the directive file, and prepares the project. You only need to press the Compile button to create the package.

Paquet Builder also supports the same command-line switches as for project files.

Open a directive file, compile the project without interaction, save the log to an HTML file, and exit:

PBUILDER.EXE "C:\My Documents\pbtests\directive1.pbd" /c /s /q /log:"C:\My Documents\pblog.html"

Open a directive file and set the bitness to x64 via the command line:

PBUILDER.EXE "C:\My Documents\pbtests\instructions package 2.pbd" /exetype:1

You can also override settings defined in the directive file by adding command-line switches. For example, if the directive specifies a 32-bit build but you need 64-bit, simply add /exetype:1.

In addition to the command line and the GUI menu, you can execute directive files using AI-powered tools:

• MCP Server — The execute_directive tool lets AI assistants like Claude Code, Cursor, or Windsurf run .pbd files programmatically. For example, you can ask: “Execute the directive file at C:\builds\release.pbd” and the AI will call the tool, compile the project, and report the result.

• AI Assistant — While the built-in AI Assistant does not execute directive files directly, it can accomplish the same results by modifying project settings and compiling — all through natural language conversation. For batch or scripted workflows, use directives; for interactive, conversational changes, use the AI Assistant.