Inno Setup 32bit and 64bit dll installation

https://stackoverflow.com/questions/17944516/inno-setup-32bit-and-64bit-dll-installation

I have had success with the following:

[Files]
Source: D:..32bit filesmylibrary.dll; DestDir: {app}; 
    Flags: restartreplace ignoreversion regserver 32bit; **Check: "not IsWin64"**

Source: D:..64bit filesmylibrary.dll; DestDir: {app}; 
    Flags: restartreplace ignoreversion regserver 64bit; Check: IsWin64

edited Feb 28 '16 at 15:18

Martin Prikryl

139k3535 gold badges311311 silver badges651651 bronze badges

answered Jul 30 '13 at 14:34

GAR8

28311 gold badge55 silver badges1414 bronze badges

the destdir is {app} for both. Wouldn't it copy both the 64 and 32bit to the same location then? I'd like the 64bit copied to the 64bit program files location and 32bit to the x86 program files. – Ali Jul 30 '13 at 16:26
No, it will only copy the version that matches the bit of the system. Per Inno Help: "Causes the {sys} constant to map to the 64-bit System directory when used in the Filename and WorkingDir parameters. This is the default behavior in a 64-bit mode install. This flag can only be used when Setup is running on 64-bit Windows, otherwise an error will occur. On an installation supporting both 32- and 64-bit architectures, it is possible to avoid the error by adding a Check: IsWin64 parameter, which will cause the entry to be silently skipped when running on 32-bit Windows." – GAR8 Jul 30 '13 at 20:15
This does not answer the question, as it indeed installs both files to the same location (the {app} resolves to installation folder selected by user, it won't magically map to 64-bit equivalent when 64bit flag is used). On the other hands, this is the correct solution for most cases. For example if your application is 32-bit, but also has 64-bit version shell extension, you still install the shell extension along with the rest of the binaries to the 32-bit "Program Files". But you use the 64bit flag to make it register for 64-bit. – Martin Prikryl Feb 28 '16 at 7:04