Debian package builds fail on ARMv7

[6XGate]

• Version: 22.7.0
• Electron Version: 8.4.0
• Electron Type (current, beta, nightly): current
• Target: armv7l/arm/arm32

Unable to build Debian package (.deb) for --armv7l due to using the wrong build of FPM, which was x86.

  • downloading     url=https://github.com/electron-userland/electron-builder-binaries/releases/download/fpm-1.9.3-2.3.1-linux-x86/fpm-1.9.3-2.3.1-linux-x86.7z size=4.6 MB parts=1
  • downloaded      url=https://github.com/electron-userland/electron-builder-binaries/releases/download/fpm-1.9.3-2.3.1-linux-x86/fpm-1.9.3-2.3.1-linux-x86.7z duration=3.13s
  ⨯ cannot execute  cause=exit status 127
                    errorOut=/home/node/.cache/electron-builder/fpm/fpm-1.9.3-2.3.1-linux-x86/lib/ruby/bin/ruby: line 6: /home/node/.cache/electron-builder/fpm/fpm-1.9.3-2.3.1-linux-x86/lib/ruby/bin.real/ruby: No such file or directory
    
                    command=/home/node/.cache/electron-builder/fpm/fpm-1.9.3-2.3.1-linux-x86/fpm -s dir --force -t deb -d libgtk-3-0 -d libnotify4 -d libnss3 -d libxss1 -d libxtst6 -d xdg-utils -d libatspi2.0-0 -d libuuid1 -d libappindicator3-1 -d libsecret-1-0 --deb-compression xz --architecture armhf --name bridgecmdr --after-install /tmp/t-ufb98R/0-after-install --after-remove /tmp/t-ufb98R/1-after-remove --description '
     Professional switch and monitor controller for retro gaming' --version 2.0.0-beta --package /workdir/dist/bridgecmdr_2.0.0-beta_armv7l.deb --maintainer 'Matthew Holder <sixxgate@hotmail.com>' --url 'https://github.com/6XGate/bridgecmdr#readme' --vendor 'Matthew Holder <sixxgate@hotmail.com>' --license GPL-3.0-or-later /workdir/dist/linux-armv7l-unpacked/=/opt/BridgeCmdr /workdir/node_modules/app-builder-lib/templates/icons/electron-linux/16x16.png=/usr/share/icons/hicolor/16x16/apps/bridgecmdr.png /workdir/node_modules/app-builder-lib/templates/icons/electron-linux/32x32.png=/usr/share/icons/hicolor/32x32/apps/bridgecmdr.png /workdir/node_modules/app-builder-lib/templates/icons/electron-linux/48x48.png=/usr/share/icons/hicolor/48x48/apps/bridgecmdr.png /workdir/node_modules/app-builder-lib/templates/icons/electron-linux/64x64.png=/usr/share/icons/hicolor/64x64/apps/bridgecmdr.png /workdir/node_modules/app-builder-lib/templates/icons/electron-linux/128x128.png=/usr/share/icons/hicolor/128x128/apps/bridgecmdr.png /workdir/node_modules/app-builder-lib/templates/icons/electron-linux/256x256.png=/usr/share/icons/hicolor/256x256/apps/bridgecmdr.png /tmp/t-ufb98R/2-BridgeCmdr.desktop=/usr/share/applications/bridgecmdr.desktop

[alienzhangyw]

You should write the deb key in package.json like this:
"deb": { "fpm": [ "--architecture=armhf" ] }
And arm versions can only be built on Linux x64 or WSL. By the way don't forget to add 'sudo' before your commands.

[6XGate]

Oh, that's going to make multi-arc builds even more fun.

[jyangchisyan]

You should write the deb key in package.json like this:
"deb": { "fpm": [ "--architecture=armhf" ] }
And arm versions can only be built on Linux x64 or WSL. By the way don't forget to add 'sudo' before your commands.

I think the "fpm" property doesn't support

• electron-builder version=22.7.0 os=5.4.51-v8+
• loaded configuration file=/home/pi/workspace/hyper/electron-builder.json
⨯ Invalid configuration object. electron-builder 22.7.0 has been initialized using a configurat$on object that does not match the API schema.
• configuration.linux.target[0] has an unknown property 'fpm'. These properties are valid:
object { target, arch? }
How to fix:
1. Open https://www.electron.build/configuration/linux
2. Search the option name on the page (or type in into Search to find across the docs).
* Not found? The option was deprecated or not exists (check spelling).
* Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", no
t in the root.

this thread provide the good workaround way

[alienzhangyw]

You should write the deb key in package.json like this:
"deb": { "fpm": [ "--architecture=armhf" ] }
And arm versions can only be built on Linux x64 or WSL. By the way don't forget to add 'sudo' before your commands.

I think the "fpm" property doesn't support

• electron-builder version=22.7.0 os=5.4.51-v8+
• loaded configuration file=/home/pi/workspace/hyper/electron-builder.json
⨯ Invalid configuration object. electron-builder 22.7.0 has been initialized using a configurat$on object that does not match the API schema.
• configuration.linux.target[0] has an unknown property 'fpm'. These properties are valid:
object { target, arch? }
How to fix:

1. Open https://www.electron.build/configuration/linux
2. Search the option name on the page (or type in into Search to find across the docs).

• Not found? The option was deprecated or not exists (check spelling).
• Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", no
  t in the root.

this thread provide the good workaround way

There is a fpm option here, maybe you missed it. My repo works fine with it.

[jyangchisyan]

• electron-builder version=22.7.0 os=5.4.51-v8+
• loaded configuration file=/home/pi/workspace/hyper/electron-builder.json
⨯ Invalid configuration object. electron-builder 22.7.0 has been initialized using a configurat$on object that does not match the API schema.
• configuration.linux.target[0] has an unknown property 'fpm'. These properties are valid:
object { target, arch? }

I found I add the fpm object into the Linux object level. I move it in deb object and the above error message not happen.

There is a fpm option here, maybe you missed it. My repo works fine with it.

However, the fpm package still use x86 version.
Let's check document again. the fpm option only support APK, FreeBSD, Pacman, P5P and RPM target option
I will trace the source code confirm that whether the deb support the fpm option.

[alienzhangyw]

However, the fpm package still use x86 version.
Let's check document again. the fpm option only support APK, FreeBSD, Pacman, P5P and RPM target option
I will trace the source code confirm that whether the deb support the fpm option.

Yes the fpm still use x86 version because it don't have arm versions, but it works with arm options.
You missed this line in the doc:

All LinuxTargetSpecificOptions can be also specified in the deb to customize Debian package.

And "deb" key should be top-level under the "build" key. You can take a look at my repo BlockPi if you still have problems.

[jyangchisyan]

You missed this line in the doc:

All LinuxTargetSpecificOptions can be also specified in the deb to customize Debian package.

Thanks for your figure out ! I miss this line.

Yes the fpm still use x86 version because it don't have arm versions, but it works with arm options.

That's clarify. I perhaps misunderstand @6XGate the question.
If we will compile and build it at the armv7 platform. We need follow [this thread] because the compiler does not at x86 platform.
(#3901 (comment))
If just need build for armv7 deb package, could direct apply it
"deb": { "fpm": [ "--architecture=armhf" ] }

@6XGate Hope the above disscussion could solve your problem. If we don't have any other confuse or question. Could close this issue.

Thanks @alienzhangyw patiently explain and participate.

[6XGate]

Base on the discussion, I'm not sure since this has to target both x86-64 and ARM 32-bit and 64-bit. To do that, it seem node-gyp has to run from those platforms directly to build native dependencies such as node-serialport.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[6XGate]

To the bot... Yes, still relevant. Not sure what is blocking. Not sure what else.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[6XGate]

To the bot... Yes, still relevant. Not sure what is blocking. Not sure what else.

The reason running anything on x86 or x64 will not work for ARM builds it related to Node packages that have native components. node-gyp does not support cross-compiling and therefore must run on the same platform as the application which is being built. In my project node-serialport is the problem dependency.