starred/Electron.NET
1
0
Fork 0
mirror of https://github.com/ElectronNET/Electron.NET.git synced 2026-02-04 05:34:51 +00:00
Code Issues 668 Packages Projects Releases 20 Wiki Activity

Build fails for win-x64 under linux #480

New Issue
Open
opened 2026-01-29 16:40:50 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 16:40:50 +00:00
Owner
Copy Link

Originally created by @ThuCommix on GitHub (May 9, 2020).

Originally assigned to: @GregorBiswanger on GitHub.

  • Version:
    • API: 8.31.1
    • CLI: 8.31.1
  • dotnet core sdk 3.1
  • nodejs 12.x
  • Target:
    • win-x64

I'm trying to setup a build for my electron app for multiple platforms: win-64x, linux-x64 and osx. After having giant trouble even with the linux build I rolled my own image and got it working. For example I needed to install the electron-builder globally because when just running electronize build I had got an error claiming that the post install of ejs failed.

However: Building for win-x64 in a docker container is currently not possible:

Optimizing assemblies for performance is not supported for the selected target platform or architecture. Please verify you are using a supported runtime identifier, or set the PublishReadyToRun property to false

I think the flag was introduced a couple of commits ago. Is this expected behaviour or should the build work for win-x64 under linux?

Steps to Reproduce:

  1. Pull thucommix/dotnetsdk-electron:3.1_12 (for example or setup node in a dotnet sdk image yourself)
  2. Try to build any blazor starter project using: electronize /target win
Originally created by @ThuCommix on GitHub (May 9, 2020). Originally assigned to: @GregorBiswanger on GitHub. <!-- Please search existing issues to avoid creating duplicates. --> <!-- Which version of Electron.NET CLI and API are you using? --> <!-- Please always try to use latest version before report. --> * **Version**: * API: 8.31.1 * CLI: 8.31.1 <!-- Which version of .NET Core and Node.js are you using (if applicable)? --> - dotnet core sdk 3.1 - nodejs 12.x <!-- What target are you building for? --> * **Target**: * win-x64 <!-- Enter your issue details below this comment. --> I'm trying to setup a build for my electron app for multiple platforms: win-64x, linux-x64 and osx. After having giant trouble even with the linux build I rolled my own image and got it working. For example I needed to install the electron-builder globally because when just running electronize build I had got an error claiming that the post install of ejs failed. However: Building for win-x64 in a docker container is currently not possible: ``` Optimizing assemblies for performance is not supported for the selected target platform or architecture. Please verify you are using a supported runtime identifier, or set the PublishReadyToRun property to false ``` I think the flag was introduced a couple of commits ago. Is this expected behaviour or should the build work for win-x64 under linux? <!-- If you want, you can donate to increase issue priority (https://donorbox.org/electron-net) --> Steps to Reproduce: 1. Pull thucommix/dotnetsdk-electron:3.1_12 (for example or setup node in a dotnet sdk image yourself) 2. Try to build any blazor starter project using: electronize /target win
claunia added the bug label 2026-01-29 16:40:50 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
api
applications
bug
bug
dev-experience
discussion
documentation
duplicate
enhancement
examples
Feature
Feature
good first issue
help wanted
In progress
information
infrastructure
invalid
javascript
macos
more-information-needed
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#480
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?