-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux x64 build fails when arm build is performed before #6534
Comments
For further details, this is the output log and config from before when it only built x64 targets and was still working. |
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. |
Still relevant to my knowledge |
If someone wants to make fpm in |
Were you able to overcome this @lukasbach? I'm trying to build app for Linux arm64 using the electron.builder Docker image in a GitHub runner and I'm stuck in the same place: |
@rmartins90 no sorry, after it was not working I didn't investigate this any further. |
I'm trying to build for both arm architectures and x64 under Linux. Before, I just had x64 as target which worked fine, however now I've added arm64 and armv7l as targets, and now the x64 target is failing which I don't really understand since that worked fine before.
The build is executed on an Github action runner. The complete output log is here: https://github.com/lukasbach/yana/runs/4722014157?check_suite_focus=true#step:6:351
(marked line is where the error happens)
This is how the config file looks like: https://github.com/lukasbach/yana/blob/6955233158610ea75564fd38fe52bc4436cf4d59/electron-builder.json
Relevant snippet from the config:
Relevant outout log part:
Is there an issue with electron builder, since the previously working x64 build now fails if a arm build is performed previously, or has it something to do with my config? Thanks in advance!
The text was updated successfully, but these errors were encountered: