About Directive Files¶

Introduction to Directive Files¶

Paquet Builder introduces a specific file type called "directive file", using the .pbd extension.
These text-based files contain instructions for Paquet Builder to create or modify a package/installer.

Why Use Directive Files?¶

✔ Automate Package Creation – Useful for external applications needing to generate packages dynamically.
✔ Modify Existing Projects – Enables automated transformations of existing projects.
✔ Shell Extension Support – The Paquet Builder shell extension works with directive files.

💡 Recommended Format: Save directive files in UTF-8 (with or without BOM).

📖 Learn More: 👉 How to Open and Execute Directives.

How Directive Files Work¶

Directive files follow a format similar to Windows INI configuration files.

Example of a Directive File (.pbd)¶

; Paquet Builder Directive File
; Version 1.1

[DirectiveVariables]
MYVERSION=1.0

[General]
Title=My archive {$MYVERSION$}  
ProjectTemplate=C:\MyWork\MyProject\baseproj.pbpx
OutputDir=C:\MyWork\MyProject\output
OutputName=MyArchive.exe
Company=G.D.G. Software
EXEType=0  ; 32-bit package
IsWizard=1
StorePaths=1
Folder=C:\MyWork\Source\
SubFolders=1
Icon=C:\MyWork\MyProject\media6.ico

[Source]
0=C:\MyWork\MyProject\Source\*.*  
1={$PBDIRECTPATH$}\Data Source Files\*.xml

Mandatory Sections¶

✔ [General] – Configures the package settings (always required).
✔ [Source] – Lists files to include (unless NoSourceSection=1 is set).

[General] Section Parameters¶

This section defines the package configuration.
- Parameters can be specified in any order.
- Boolean values: Use 1 (true) or 0 (false).

The [General] section defines the core settings of the package.
- All parameters are optional, unless specified otherwise.
- Boolean values: 1 = Enabled (true), 0 = Disabled (false).

[Source] Section¶

This section lists files to be included in the package.
- Supports wildcards (e.g., *.exe, *.xml).
- Allows absolute or relative paths using directive variables.

Example Source Section¶

[Source]
0=C:\MyWork\Project\Source\*.*
1=C:\MyWork\Project\Readme.txt
2=C:\Windows\System\cabinet.dll
3={$PBDIRECTPATH$}\Data\*.xml

💡 Use Directive Variables like {$PBDIRECTPATH$} to avoid hardcoded paths.

[Components] Section¶

Defines optional components that users can select during installation.

Example Component Structure¶

[Components]
0=Documentation
1=Pictures

[Documentation.Source]
0=C:\Project\Help\*.chm

[Documentation.Properties]
Description=Application Documentation
Title=Documentation
StoringPath=1

• Each component requires a [ComponentName.Source] and [ComponentName.Properties] section.
• The Main component always exists and is defined in [Main.Properties].

📖 Learn more: 👉 Component Management.

Directive Variables¶

Directive variables allow dynamic path replacement in directive files.

Built-in Variables¶

Example Usage¶

[Source]
0={$PBDIRECTPATH$}\Source Files\*.*
1={$PBDIRECTPATH$}\Docs\*.pdf

💡 Now, you can move the directive file without breaking file paths!

[SignToolCmd] Section – Custom SignTool Commands¶

This section allows multiple digital signatures to be applied sequentially. ⚠️ Only read if SignCertifLocation is set to 3.

Example:

[SignToolCmd]
0=sign /fd SHA256 /tr "http://timestamp.digicert.com" /td SHA256 "{$BOUTPUTFILES}"
1=sign /fd SHA1 /tr "http://timestamp.digicert.com" /td SHA1 "{$BOUTPUTFILES}"

• Each line represents one signing command.
• Executed in order (e.g., first SHA-256, then SHA-1).

Define Custom Directive Variables¶

Create your own variables inside [DirectiveVariables].

[DirectiveVariables]
MYVERSION=1.0
OUTPUTNAME=Installer

Use them in any section:

[General]
Title=My archive {$MYVERSION$}
OutputName={$OUTPUTNAME$} {$MYVERSION$}.exe

Example: Simple Directive File Without Source¶

; Paquet Builder Directive File
[General]
Title=My archive 1
NoSourceSection=1
OutputName=Direct2.exe
OutputDir=C:\Build\Output
ProjectTemplate=C:\Build\Template.pbpx
LiveUpdate=1

💡 Use NoSourceSection=1 if your directive modifies an existing project.

Conclusion¶

Directive files provide a powerful way to automate Paquet Builder workflows.
✔ Easily generate packages via scripts.
✔ Modify project parameters dynamically.
✔ Use variables to avoid hardcoded paths.

📖 Related Topics:
- 👉 How to Open and Execute Directives
- 👉 Working with Components