-
Notifications
You must be signed in to change notification settings - Fork 60
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
Support cross-platform builds #89
Comments
Is there any workaround for this issue? |
No, Windows API is needed
пт, 2 июл. 2021 г. в 19:36, deelef ***@***.***>:
… Is there any workaround for this issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#89 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEMMNJXMDQDCZLSXU64AJDTVXTIJANCNFSM4XM75U2Q>
.
|
Even though the Windows API is needed, it would be very helpful if the package could still be installed independently of the current OS, for example to support monorepo builds where a single package.json is used and not all dependencies are needed all the time. FWIW, we have created a custom build to remove the OS restriction and do a check during runtime instead. |
Same here. Any progress? We want to build Electron only for Windows but have to build the app on Linux :( |
Background
Our developers and CI/CD pipeline use different platforms (Windows, Linux, Mac) for working in a monorepo based on nx. Due to this, we have a single
package.json
with all dependencies.Problem
After adding winax as a dependency,
npm ci
fails on platforms other than Windows, because it cannot build the native binaries usingnode-gyp
:Proposal
It would be great if the winax package could include prebuilt binaries for Windows.
For example, the ffi-napi project includes those binaries and we can at least install the packages on other platforms and even do a build that can be used on Windows. FWIW, they are using prebuildify to build the Windows binaries in an Appveyor build.
The text was updated successfully, but these errors were encountered: