This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Hybrid installer for 32 bit & 64 bit windows System
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 14, 2011
05:57 AM
Hybrid installer for 32 bit & 64 bit windows System
Hi,
I am using 2010 Enterpise edition.
I have developed one application and I want a single installer for both 32 bit & 64 bit windows system.
32 bit system should use 32 bit JVM & 64 bit system should use 64 bit JVM.
Please guide me how should I proceed ...
Thanks,
Jayvardhan
I am using 2010 Enterpise edition.
I have developed one application and I want a single installer for both 32 bit & 64 bit windows system.
32 bit system should use 32 bit JVM & 64 bit system should use 64 bit JVM.
Please guide me how should I proceed ...
Thanks,
Jayvardhan
1 Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 15, 2011
10:51 AM
We just have the installer use the 32 bit jvm in all cases. Then we bundle a separate 64 bit jvm which we install only if the platform is a 64 bit platform. This causes an extra jvm to be in the installer in all cases, and an extra one on disk when it is a 64 bit platform, because the installer still needs its 32 bit jvm for uninstallation (well, maybe it doesn't but I leave it there) and our product uses the 64. (In fact I'm profligate with jvms and install a separate 32 bit jvm on the 32 bit platform just so it will be in the same place for our app and our lib/ext additions will be there and not get in the way.)
I wrote a custom code rule to check bit size, on windows it looks at System.getenv("PROCESSOR_ARCHITECTURE") and on linux it runs some command (getconf LONG_BIT) and on solaris it runs another command (isainfo -b).
I wrote a custom code rule to check bit size, on windows it looks at System.getenv("PROCESSOR_ARCHITECTURE") and on linux it runs some command (getconf LONG_BIT) and on solaris it runs another command (isainfo -b).
