Inno Setup:x64 vs x86
2012-08-26 09:44
323 查看
By default Inno Setup always installs your application in 32-bit mode. But if your application is compiled to 64-bit binaries (at least, partly) you will, probably, want to use 64-bit mode. First thing you need to do is to specify ArchitecturesInstallIn64BitMode
in [Setup] section:
[Setup]
ArchitecturesInstallIn64BitMode=x64
This means that under 64-bit processor architecture 64-bit mode will be used. You can specify Itanium architecture (ArchitecturesInstallIn64BitMode=ia64) if necessary.
Now imagine you need to use one file for 32-bit mode and another file for 64-bit mode. You can do it in the following way:
[Files]
Source: "OurProgram\Release\shellextension.dll"; DestDir: "{app}"; Flags: regserver ignoreversion; Check: not Is64BitInstallMode;
Source: " OurProgram \x64\Release\shellextension.dll"; DestDir: "{app}"; Flags: regserver ignoreversion; Check: Is64BitInstallMode;
In the script above we specified to use 32-bit version of shell extension dll in 32-bit mode and 64-bit version of shell extension in 64-bit mode. Other files can be the same for 32-bit and 64-bit modes or different.
Also you can create completely different installers for different architectures. For example, to create installer specially for 64-bit architecture you need to specify:
[Setup]
ArchitecturesAllowed = x64
Other possible values are x86 or ia64. You can specify several values separated by spaces
in [Setup] section:
[Setup]
ArchitecturesInstallIn64BitMode=x64
This means that under 64-bit processor architecture 64-bit mode will be used. You can specify Itanium architecture (ArchitecturesInstallIn64BitMode=ia64) if necessary.
Now imagine you need to use one file for 32-bit mode and another file for 64-bit mode. You can do it in the following way:
[Files]
Source: "OurProgram\Release\shellextension.dll"; DestDir: "{app}"; Flags: regserver ignoreversion; Check: not Is64BitInstallMode;
Source: " OurProgram \x64\Release\shellextension.dll"; DestDir: "{app}"; Flags: regserver ignoreversion; Check: Is64BitInstallMode;
In the script above we specified to use 32-bit version of shell extension dll in 32-bit mode and 64-bit version of shell extension in 64-bit mode. Other files can be the same for 32-bit and 64-bit modes or different.
Also you can create completely different installers for different architectures. For example, to create installer specially for 64-bit architecture you need to specify:
[Setup]
ArchitecturesAllowed = x64
Other possible values are x86 or ia64. You can specify several values separated by spaces
相关文章推荐
- 关于使用VS2015编译项目时出现LNK1112 module machine type 'x64' conflicts with target machine type 'X86'
- Windows下google/protobuf v3.5.1--VS2017 x86 x64编译、使用
- vs2012 opencv 模块计算机类新x86与目标计算机类x64冲突
- vs2013中将OpenCV程序由x64转化为x86
- 关于VS项目平台的x86,x64,Any CPU以及Debug和Release
- 关于VS项目平台的x86,x64,Any CPU以及Debug和Release
- vs项目属性中目标平台x86,x64,any cpu的区别
- Any CPU vs x86 vs x64 Solution Platforms
- x86 vs x64
- vs平台选项:Any CPU,x86,x64
- x86,x64,Debug,release在VS中的编译如何选择
- QT5.3.2与VS2013 fatal error LNK1112: 模块计算机类型“X86”与目标计算机类型“x64”冲突_(解决方案)
- VS x86 x64 anycpu 编译运行对照表
- 关于VS项目平台的x86,x64,Any CPU以及Debug和Release的区别
- 在VS2015下配置OpenCV3.2时遇到 fatal error LNK1112: 模块计算机类型“x64”与目标计算机类型“X86”冲突
- QT5.3.1和VS2013开发,安装插件后在VS2013建新工程报错模块计算机类型“x64”与目标计算机类型“X86”冲突
- 关于MYSQL编程使用VS2015编译报“LNK4272库计算机类型“X86”与目标计算机类型“x64”冲突”的解决办法
- VS2013环境里安装QT插件-“X86”与目标计算机类型“x64”冲突
- VS中自动选择x86或x64的dll
- error LNK1112: 模块计算机类型“x64”与目标计算机类型“X86”冲突 (VS2013配置opencv2.4.10的BUG)