Directives        Previous pageReturn to chapter overviewNext page

Process-order Directives. Use these to alter the "mainline" install/assembly sequence. The following are listed in the order of the default post-assembly sequence:

Ξ Some Notes:

    1. These are for the <Assembly> section ONLY.
    2. For ssApp's it is NOT recommended to place post-install #directives# *before* its installer or setup program since the install-to path (or <AppPath>) is often not created nor determined until after it has been run. So if need be, make use instead of .cmd/.bat and/or .reg files and of any of the Component %variables%.


CLI Directives:

Ξ Some Notes:

    1. These are for the <Assembly> section ONLY.
    2. These can be at the beginning or at the end of each line.


Gate Directives: Use these filter a line by its OS and/or Architecture.

#Is_OS<|=|>|<>|<=|>=V[.v[.bbbb]]#

with:

< : "less than"

= : "equal to"

> : "greater than"

<> : "not equal to"

>< : "not equal to"

<= : "less than or equal to"

>= : "greater than or equal to"

=< : "equal to or less than"

=> : "equal to or greater than"

where:

V.v.bbbb : The Windows NT version. This can be just the Major, the Major.minor, or Major.minor.build.

Ξ Some Notes:

    1. These can be at the beginning or at the end of each line.
    2. Gate directives may also be used in the following: Script-files (.cmd/.bat), Registry-files(.reg), and in the .app/.ppg-file under the keys "FileTypes", "RegisterDLLs", "InstallFonts", and the ShortcutS definitions. With ShortcutS definitions, placement of the gate(s) is via the "Flags" key (with or without "#" delimiters).
    3. Two or more gates used together will have a logical "AND" effect. This will allow one to specify OS ranges and OSArch combinations.


Some examples:

Copyright © 2020, Vergitek Solutions

ssTek Forum: Tools for custom Operating Systems!