Build installers for both x86 and x64 in Maven

[valimaties]

I'm submitting a…

• bug report
• feature request
• other

Short description of the issue/suggestion:

How do I generate different installers for x86 and x64 architectures in a Maven project?

Steps to reproduce the issue/enhancement:

1. [First Step]
2. [Second Step]
3. [Other Steps...]

What is the expected behavior?

I want to use the installer depending on the system I install my app, if it is a x86 system OS to use the x86 installer, and if it is a x64 OS system I want to use the installer for x64.

What is the current behavior?

I don't know how to do it, I tried something using different profiles, but I don't have any property to set to name the file depending on the profile I use. Or maybe is a wrong approach, I don't know.

Do you have outputs, screenshots, demos or samples which demonstrate the problem or enhancement?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

• JavaPackager version: 1.7.0
• OS version: W11 x64 22H2
• JDK version: Liberica JDK 20
• Build tool:
  • Maven
  • Gradle

Other information (e.g. related issues, suggestions how to fix, links for us to have context)

[valimaties]

Seems to make a JavaFX Maven application to run on both x86 and x64 OSes there are a lot of things that should be changed in the settings and build. So, is not only a Javapackager "feature/issue" but also a build configuration for each platform.

[fvarrui]

Hi @valimaties!
I'll do some research about this topic

[valimaties]

Thanks @fvarrui
I'll wait for your feedback 🤗

[lhDream]

At present, java officially only provides 64-bit JDK

[valimaties]

At present, java officially only provides 64-bit JDK

I'm using Liberica SDK 20, which provides both 32 bit and 64 bit sdk. Liberica is based on OpenJDK.

[lhDream]

@valimaties

Then you can only use 32-bit JDK, 64-bit system is compatible with 32-bit applications. Or specify the 32-bit jdk or 64-bit jdk path used when packaging.

<jdkPath>${java.home}/java_jdk_x86</jdkPath>
 <jdkPath>${java.home}/java_jdk_x86_64</jdkPath>

[valimaties]

@valimaties

Then you can only use 32-bit JDK, 64-bit system is compatible with 32-bit applications. Or specify the 32-bit jdk or 64-bit jdk path used when packaging.

<jdkPath>${java.home}/java_jdk_x86</jdkPath>
 <jdkPath>${java.home}/java_jdk_x86_64</jdkPath>

🙂definitelly, I don't want to build the apps using only the 32bit jdk on both 32 and 64 bit OSes.
So, yes, specifying the jdk when packaging is the goal, but I don't want to do it somehow manually. I tried using profiles (as I said already) but somehow the 32 bit exe file does not starts. Only 64 bit starts. Using profiles I packaged them in different location, one for 32bit and one for 64 bit. That for the 64 bit starts, but the one for the 32bit doesn't. That's why I created this issue, and Fancisco already added the "Working on" state for this issue. Maybe he find a way to build the exe file using the jdk from 32bit path. I thiink that's the issue right now.

[fvarrui]

Not only is a 32 bit JRE required, but the EXE file and the installer are also required to be 32 bit. I guess that's where the problem lies

[valimaties]

any news?

[fvarrui]

any news?

I'm sorry, I haven't been able to make much progress, I'll try to do something over the weekend 😞

[fvarrui]

Just installed Win7 32bits in a VM (https://app.vagrantup.com/mrh1997/boxes/vanilla-win7-32bit) ... ready to do some tests

[fvarrui]

After doing some research about this issue, I found out that Launch4J generated EXE and Inno Setup installer EXE files are both 32bits, so both run on 32-bit and 64-bit Windows systems without problems:

C:\Users\fvarrui\GitHub\HelloWorldMaven>sigcheck target\HelloWorldMaven\HelloWorldMaven.exe

Sigcheck v2.90 - File version and signature viewer
Copyright (C) 2004-2022 Mark Russinovich
Sysinternals - www.sysinternals.com

C:\Users\fvarrui\GitHub\HelloWorldMaven\target\helloworldmaven\HelloWorldMaven.exe:
        Verified:       Unsigned
        Link date:      15:01 20/07/2023
        Publisher:      n/a
        Company:        ACME
        Description:    HelloWorldMaven
        Product:        HelloWorldMaven
        Prod version:   1.0.0
        File version:   1.0.0
        MachineType:    32-bit

C:\Users\fvarrui\GitHub\HelloWorldMaven>sigcheck target\HelloWorldMaven_1.0.0.exe

Sigcheck v2.90 - File version and signature viewer
Copyright (C) 2004-2022 Mark Russinovich
Sysinternals - www.sysinternals.com

C:\Users\fvarrui\GitHub\HelloWorldMaven\target\HelloWorldMaven_1.0.0.exe:
        Verified:       Unsigned
        Link date:      15:54 15/02/2023
        Publisher:      n/a
        Company:        ACME
        Description:    HelloWorldMaven Setup
        Product:        HelloWorldMaven
        Prod version:   1.0.0
        File version:
        MachineType:    32-bit

HelloWorldMaven is just a project for testing JP.

** sigcheck is a Sysinternals tool

[fvarrui]

@valimaties I understand therefore that it's only necessary to consider using a 32-bit JDK when bundling a JRE