|
|
@@ -5239,7 +5239,51 @@ DiskSliceSize=1457664
|
|
|
<topic name="archidentifiers" title="Architecture Identifiers">
|
|
|
<keyword value="Architecture Identifiers" />
|
|
|
<body>
|
|
|
-<p>.</p>
|
|
|
+<dl>
|
|
|
+
|
|
|
+<dt><b>arm32compatible</b></dt>
|
|
|
+<dd>
|
|
|
+<p>Matches systems capable of running 32-bit Arm binaries. Only Arm64 Windows includes such support.</p>
|
|
|
+</dd>
|
|
|
+
|
|
|
+<dt><b>arm64</b></dt>
|
|
|
+<dd>
|
|
|
+<p>Matches systems running Arm64 Windows.</p>
|
|
|
+</dd>
|
|
|
+
|
|
|
+<dt><b>win64</b></dt>
|
|
|
+<dd>
|
|
|
+<p>Matches systems running 64-bit Windows, regardless of OS architecture.</p>
|
|
|
+<p>This may be useful in an installer that doesn't ship any architecture-specific binaries, but requires access to something 64-bit, like <tt>HKLM64</tt> in the [Registry] section, or the native 64-bit Program Files directory.</p>
|
|
|
+</dd>
|
|
|
+
|
|
|
+<dt><b>x64compatible</b></dt>
|
|
|
+<dd>
|
|
|
+<p>Matches systems capable of running x64 binaries. This includes systems running x64 Windows, and also Arm64-based Windows 11 systems, which have the ability to run x64 binaries via emulation.</p>
|
|
|
+</dd>
|
|
|
+
|
|
|
+<dt><b>x64os</b></dt>
|
|
|
+<dd>
|
|
|
+<p>Matches systems running x64 Windows only — not any other systems that have the ability to run x64 binaries via emulation.</p>
|
|
|
+<p>In most cases, <tt>x64compatible</tt> should be used instead of <tt>x64os</tt>, because <tt>x64compatible</tt> allows x64 apps to be installed on Arm64-based Windows 11 systems as well.</p>
|
|
|
+<p>However, <tt>x64os</tt> is appropriate in unusual cases where an x64 app/binary is known to require true x64 Windows and cannot function under emulation. x64 device drivers are one example; x64 emulation isn't supported in kernel mode.</p>
|
|
|
+<p>Before Inno Setup 6.3, <tt>x64os</tt> was named <tt>x64</tt>. The compiler still accepts <tt>x64</tt> as an alias for <tt>x64os</tt>, but will emit a deprecation warning when used.</p>
|
|
|
+</dd>
|
|
|
+
|
|
|
+<dt><b>x86compatible</b></dt>
|
|
|
+<dd>
|
|
|
+<p>Matches systems capable of running 32-bit x86 binaries. This includes systems running x86 Windows, x64 Windows, and also Arm64-based Windows 10 and 11 systems, which have the ability to run x86 binaries via emulation.</p>
|
|
|
+<p>Given that Setup itself is currently always built as a 32-bit x86 binary, this always matches.</p>
|
|
|
+</dd>
|
|
|
+
|
|
|
+<dt><b>x86os</b></dt>
|
|
|
+<dd>
|
|
|
+<p>Matches systems running 32-bit x86 Windows only.</p>
|
|
|
+<p><tt>x86os</tt> usually only makes sense when installing 32-bit x86 device drivers. When installing a regular 32-bit app, <tt>x86compatible</tt> should be used instead (or just leave <tt>ArchitecturesAllowed</tt> unset).</p>
|
|
|
+<p>Before Inno Setup 6.3, <tt>x86os</tt> was named <tt>x86</tt>. The compiler still accepts <tt>x86</tt> as an alias for <tt>x86os</tt>.</p>
|
|
|
+</dd>
|
|
|
+
|
|
|
+</dl>
|
|
|
</body>
|
|
|
</topic>
|
|
|
|
Jordan Russell